So this is a Linux distribution and is my distribution of choice. Blackmagic Design likes sent OS, I’m not a fan. So I installed this for some benchmarking on Ubuntu and I got some questions: hey how’d, you make that work. So let’s take a look today at how we made it work here in Ubuntu Linux.
First thing I did was install the base version with the proprietary Nvidia graphics cards. Now I am at Blackmagic comm, slash support and I clicked on resolve and fusion in the menu above then, I downloaded the Linux version of studio 16. 1.1. This will work the same as it will in the free version. If you do not have a studio license, it’s now downloading the studio version and will zip ahead and the download is complete.
I’ve opened this in the archive manager so that I can read the installation instructions, which is one of two files that are handed to you. One is a shell script and one is this installation instructions. The instructions primarily tell you to run Sint OS again, not my favorite. As you can see on the left, I’ve opened my terminal window browsed to My Documents, folder, where I downloaded and extracted the tarball that they sent me and I ran the script, typing dot and slash and then the install script name.
Now you can see it’s running the normal install that you’re used to. In fact this will complete it copies the binaries and the configuration files that you would expect to your hard drive so where’s the snack. Well, I can tell you you saw, it looks like it’s positively finished the install and it has, but now I’m going to change directory to opt resolve and then here I will run the resolve there. We go program, dot, slash resolved and it will now tell me what my issue is.
I’ve tried to run it. It says, live open, CLS, o dot. One cannot open. This is because DaVinci Resolve is referencing, a library it believes should be in my operating system. We boot to, however, does not include that library from default, so I will search for it here in my browser and ask how do I install this in and boot? Do I get a very quick answer with apt and I’ll use apt to know install from a repository a beautiful thing about searching that here we go direct commands.
I can run that will download and install the software that I need if I can type my password when it asks you the. Why means? Yes, I want to download and install it’s capitalized, because it is the default you could just hit enter. Now that I have the libraries installed, I’m ready to run it again, so here an opt resolve bin. You can use the up-arrow to run it again boom there we go. I now have the welcome screen in Linux.
You will soon learn to hate the welcome screen. The welcome screen hangs here and you have to use one of a few different options to delete it or close the program. The first is in the top left corner of your screen. Davinci Resolve introduction quit. The other option is to wait for this to timeout and force quit either of those work, but you’ve got to be patient. This will take two four five eight minutes get comfortable.
This is the only time this will happen now. I will accelerate the speed here. We’re waiting on the force quit to pop up. It feels like forever. Now just wait till you get to do this in real life. Here it pops up and we’re going to choose force quit. That does not mean that it will immediately force quit. However, it does happen pretty quickly, so it kills it off and now I have DaVinci Resolve studio, launching we’re home free right in the launch dialog here in the focus window, we’ll get to a point where it searches for control surfaces scans for every USB device.
In my machine and then it tries to load the waveform monitor when that happens, it tries to instantiate CUDA. How do I know that? Well, let’s take a look. I killed off resolve and now we can see as I scroll back through the log history, that I’ve got here in my window from running resolve from the window. I can see where the logs are stored here in my config, if I’d like, but I’ve got some helpful data here in this stream.
So I see all the USB devices being referenced as we saw it was trying to find a console, and if I look through it, I can look for keywords like error info or problem. Let’s say I don’t see anything though nothing’s calling out to me, so what I’ve done is I’ve gone into opt resolve logs here, there’s one file that I’ve concatenated out to my screen using the cat command and I will scroll back up through it.
This is a line by line log that I can see info error and warn messages. So I’m looking through this Center column, where you see my mouse for error, so socket failed. Well, that’s because it’s not able to open a console or panel, I’m okay, with that. I don’t have one of those next, I’m looking initially in GPU board. This is a good spot to start and Oh unable to load, live CUDA from user live 64 or live CUDA, hmm! Well.
I have CUDA installed because I installed the proprietary Nvidia drivers. Maybe it’s a problem where they can’t talk to each other, so hey I’ll, search that library. I want to see where I might find it here on my workstation, if I have it or where I can get it. If I don’t check this out, one of the first results is live. Cuda cannot be found. Hmm that makes sense. Look through it. It looks like sure enough.
It should be there. Oh wait. This log post is from 2016 boy, that’s a while back. You know what I’m going to find something else now I’ll try and find something more specific to my situation. 2016 is a little out there, so I’m looking down, I see 2017 2018 tensorflow would also be referencing the cuda libraries and look at that. Here’s a command. I can use to fine, so I paste this into my terminal.
Sorry, the terminals below the edge of the window at the moment and it searches and file the file for me now. I know I have the file, but it’s not necessarily where DaVinci Resolve expects it to be so I’m going to create, what’s called a symlink, I’m going to link any reference to live CUDA data, so here in live 64 to the location. My operating system stores that file – I can do that with the command that creates what’s called a sim link.
The link is nothing but a traffic sign. It says when you come to user, live 64, live CUDA data, so looking for that file instead look over here. So here’s the command I ran, then I change directories to the bin directory under site, opt resolve and again run resolve from the terminal window. This time it launches us off without the welcome screen and with the CUDA libraries enabled here, you can see we get past the waveform, monitor, load and boom.
We have a fully working project manager and now resolved thanks for reading. Please give me a like if this was helpful to you subscribe for more content, and let me know in the comments, if you’re interested in more let based content have a great day.
Videos are truly an awesome way to get the point across. Any type of content from your business is important!