DaVinci Resolve auf Linux: Die häufigsten Fehler und ihre Fixes

Today, we're going to go over Resolve in Linux. Oh, the thing that no one ever can get working quite right. And >> [laughter] >> I've been using Resolve for years in Linux, but there's some caveats you need to know because it's not as simple as just installing in Windows. It's just one of those things. Now, I'm just happy Blackmagic gives us support of some type. But as long as you understand the limitations, you can actually work around them and things are perfect. So, let's get into all the issues that you're going to run into with Resolve and how to fix them. Now, first up, what are you going to use for your operating system? Are you using Ubuntu? Are you using Arch Linux? Are you using Debian or any kind of different operating system other than that? Well, you're probably going to have problems right out of the gate. So, just to straight up, Blackmagic's Resolve is built for Red Hat Enterprise Linux or Rocky Linux or Alma Linux. Those Rel-based distros that are years old are the ones made. And they do that because those systems don't need to be updated every single day or every single month. You can leave them for years and they're still going to work. But modern Linux users will not use these operating systems. And everybody online will not use these operating systems because they're boring, but they're very reliable. So, having said that, let's see how to fix it for a common Linux desktop user. So, the first thing you're going to run into, library mismatches. The libraries from your distro that you're using are probably more up-to-date than the stuff being used in Rocky or Rel-based systems. The other thing is setting up the GPU, which has OpenCL or CUDA if you're an Nvidia user. That's also a problem. And then codec support is the next thing. If you're playing it and you don't see any video or you don't see or hear any audio, well, if it's a video problem, well, you probably don't have uh H.264 or H.265 codecs, which is not supported in the free model. If you get the studio, you can use these codecs. If you don't have the studio, you can't. There's actually a FFmpeg encoder plugin I highly recommend installing in your DaVinci Resolve. I'll leave a link for this as well, but this essentially you can install through the AUR, and then you get all these supported codecs, which is nice. So, you can encode using 264 265, which isn't there natively on Linux. But essentially, you just download this zip bundle, you extract to this directory, and then it loads pretty seamlessly. So, now that we've talked about that, how do I run my Resolve like this and I do all my edits? This video is edited with Resolve. The first problem is getting around that library mismatch. I made an entire other Git repository called resolve-linux, and in it I have something called resolve-fix. Essentially, what's happening is the people at Blackmagic aren't great with Linux, and what they've done is they preloaded some stuff or some libraries with their executable or their binary, and then other things are pulling from your system. The things they're pulling from your system, they're looking for really old libraries, and those libraries are already upper they're they're newer. So, they can't use those newer libraries with the older ones because it's just referencing older ones. So, what this does is it loads the newer libraries that are on your system, not the older ones. So, then when Resolve goes to do the check, they're like, "Oh, it's already here. Let's proceed." And then when you go to launch, and you go just Resolve, it goes ahead and launches using the newer libraries where most people when they first install Resolve, they go to launch and it just doesn't do anything. Or if they launch it from the CLI, they'll be like, "Oh, crap. It says some library mismatch. What's going on? That's how to fix that. And speaking of installation, you can use Arch or there's actually bundled packages on Ubuntu as well. You could do that depending on your setup. The other things is the GPU support. You have to have GPU support and that is having basically saying CL info and then having this pronoun. If you don't have any info in CL info or you're not able to see anything in CL info, this isn't going to work. It's not going to see your GPU and Resolve all just won't load or if it does load, it won't be working properly. So, for Nvidia, you install these libraries. For AMD, you install this library. And for Intel, you install this library. I use an Intel B70 card cuz I do some local AI inference and all that. And then also I use it for Resolve. It's very good. It's perfect for my use case. So, I actually recommend my card for people that aren't really gaming that much, more from a productivity standpoint. Still fantastic though. I can still game with probably my older games. But, this is how I installed this so you have OpenCL and you get Resolve actually seeing that that GPU. So, that's the library launch problem. That's the GPU problem. And if it still will not launch, you can always do this and find the missing libraries and then just simply update my script. Let's say sometime in the future it's updated and for whatever reason I haven't updated it, this is the process I went through to find those files and then link them. Now, finally the codec problem. Um even [clears throat] if you're doing the free model, I don't want to say, "Hey, you're borked." Uh because you still could just re-encode things. Now, I made an entire helper script for this. It's called Resolve Convert and I just made it a bash script. And or or shell script and that just says, "Hey, point it at the directory with all your footage in it, run the script and it just can convert everything. Now, by default, I made it do DNxHR with PCM. So, lossless audio with an HD thing and Resolve just loves these formats. And you'll see one I also kind of recommend this anyways. Uh so, this is a great way to do it. Personally, though, if you want to do this, I would probably set your recording device to go ahead and encode this way. Uh on OBS, I have it set up to do the DNxHR for the encoding for the video. And then for the audio, I actually don't do lossless because it's a little bit heavier. And I find that I really like uh Opus. Opus, I feel like sounds better. It's not as heavily compressed as AAC, which is what most people do by default. And it's actually better and more space-efficient. So, personally, if you set up OBS, I would probably set it to this and then also set Opus to the audio instead of PCM. Uh both uh Resolve and Linux and Windows and everywhere will read that format perfectly. And I feel like your audio will sound just a little bit better than if you use AAC. But, if you don't want to use any of these and you have your own special formats, here's a little cheat sheet. I went ahead and added little flags you can do. Sometimes I upscale to 1440 and then push it through just so it doesn't have as much compression in YouTube, but different thing. That's more of a YouTube problem, not a Resolve problem. And also, if you do want just to fix the audio, like let's say the video comes in perfect and you're like, "I don't want to re-encode all my video to uh that." No problem. You can actually just use FFmpeg, pull out that AAC track, and then replace it with just the regular raw wave file. And then you'll have an output wave file with your audio file. You can just link those up and you're good to go. So, this is a quick way of doing it if you don't want to re-encode your whole video file. The other problem is missing fonts in Resolve. I found that it only imports fonts from the USR share fonts folder. So, when you go to do custom titling and other things in Resolve, like you'll see when I pull up let's say we do an untitled project. We'll go Resolve Linux. And I pull up my effects tab and I start looking through. Now, I have some special effects which I've bought from like different sites online. Like Mr. Alex Tech, if you're a big Resolve guy, he's amazing. Love that guy. But, I also have like a focus clip. I have a zoom effect. I have all these other things that have specific fonts that are needed. Now, typically Linux users will put this in the dot local file and then it will not show up because by default Resolve is set to only grab fonts from the USR folder, which is your your system resources folder. Most people never install fonts there and you probably shouldn't. You should install them in your home folder. So, to fix this, you go into fusion tab, go to fusion settings, go to path map, and then you'll notice under fonts, this will just say system fonts. And you want to expand that to have a colon in between the system fonts and then go home. local share fonts or wherever your fonts folder resides, but it should reside there. And this will pull in your home folder fonts and your system fonts. Took me a forever to figure out why the hell aren't my titles coming in properly in here, but that fixed it for me. I also made a backup script, too. So, like I do restore these things. I have fonts everywhere and I wanted to make sure I grab everything. So, I did make a backup script that grabs all user fonts, all the settings of my Resolve, and then I made that available here, too, just as a nice thing. But, here's a little troubleshoot checklist, too. But, you shouldn't run into anything. But, just as a little cheat sheet, if you do have stuff and just go through here and I give you like my little workflow to go through on a free version of Resolve and be able to use it in Linux. This is just going to be so much better than any free editor. I for like the first four or 500 videos on my channel I did Kdenlive. It sucks and it's just not anywhere close to what Resolve can do. You have to get Resolve working if you really, really want to seriously video edit. And I absolutely love it. Thank Thank you Blackmagic for making some kind of Linux thing and hopefully this helps you. Let me know in your comments, did you have any other issues with Resolve? I'm sure you did, but it should fall into one of these buckets I went over today. With that, I'll see you in the next one.