alt Hacker NewsI recently used Resolve (just the free version) for a project. It was my first time seriously using the software but I ended up spending a lot of time with it - lots of timeline editing, keyframe animation, some simple Fusion compositions, and a fair bit of work in the Fairlight page, rendering out daily . I did all this on my beloved Arch Linux workstation, and frankly it was rock solid, apart from exactly one crash when using the timeline keyframe editor - something that was solved by upgrading Resolve to the latest version.
I was really impressed by how well it worked for me on Linux.
I think these things might have helped:
- I use an X11 desktop (Cinnamon), not Wayland. I've tried it out on a GNOME Wayland desktop but it seemed quite a bit more clunky and froze frequently.
- PipeWire runs the system's audio routing, so Resolve just appears as another ALSA client, and I can then use wiremix to send to my preferred speakers or headphones. (I haven't tried any audio input yet)
- I didn't try to install Resolve natively, I used davincibox [1] to install and update it within a container (it uses distrobox, which then uses podman).
I'll now be purchasing the studio version, which hopefully will work as well.
Replies
I use Resolve (paid) all the time on Arch with Gnome+Mutter+Wayland, works completely alright for me, except when it comes to anything generating 3D in Fusion, for some reason. Mostly use it for quick cutting and also audio mastering.
Got my license when I bought a second hand Blackmagic camera, must have been 5-6 major Resolve versions ago, and it still works as a charm! They're a rare star among a sea of trash in the software and (arguably bit less trash) hardware world.
You encouraged me to try again and somehow, blackmagically ;) it works this time. It may be that recent DaVinci version has made some improvement. I'm so happy!
Installation still requires workarounds and codecs support is limited, but having that aknowledged and accepted, the application is finally usable!
PS. I don't know where the h264 (and other codes?) limitation come from, since ffmpeg has full support of it. Or is it just business model? Weird.