John Morris wrote:Thank you for the effort you put into this. It does make it easier for us Ubuntu based users.

Doug Marsh wrote:Is there a way I can gift you something to show my appreciation?! You rock!

--Doug

Thank you guys! I'm really glad you find my work useful. I will keep updating my converter for as long as it's possible. It really does make it a lot easier to manage Resolve installations in the Debian world.

Just wondering where we're at regarding adding sound to DaVinci Resolve running on Linux. Like many, the only thing restricting me from moving to Linux full-time is the inability to deal with audio.

Hope this feature will gain priority in the near future!

Thanks

As far as I know, unless they announced it somewhere I'm not aware, there are no current efforts to make Resolve compatible with standard Linux audio systems like Pulseaudio, Jack or Alsa. The only known way to have audio in Resolve Linux is by having one of their Decklink cards installed and it's driver handling audio, so it outputs audio via SDI, HDMI or analog outs via breakout cable, depending on the Decklink model you have. I'm most likely rolling with the Studio 4k because it has some video capture features I'd like to have too, but if you just want audio, a Mini Monitor 4k should be more than enough and way cheaper. Anyway, I might be wrong about no plans for normal Linux audio or anything else for that matter, if so, anyone is more than welcome to correct me!

Hello everybody! Need some help with figuring out Resolve install issue here. I'm a seasoned Linux user but a Resolve noob.

I'm on Ubuntu 16.04 LTS. I'm using it as the primary desktop, so it's got a ton of things installed. I wanted to use Resolve to edit some old 8mm film footage to do color correction and grain noise removal. It's a hobby project, and I thought that using a pro tool would give me the best result, so here I am.

I've downloaded DaVinci_Resolve_14.2.1_Linux.zip (md5sum 84b7f8db651c1d000289f8840565f909) and followed steps 1 through 11.1-2, plus 16 and 17 of the Linux Mint install instructions posted earilier. I didn't update GRUB options as that just to speed up booting and it disables normal disk checking at boot, and I don't have a NVidia card, so naturally I didn't install NVidia drivers.

Based on previous post here, Resolve can be used with Intel GPU, and the "Quick start" of Resolve seems to be indicating it as well. Unfortunately, once I finish the "Quick start" flow, the attempt to start Resolve results in a crash. I've pasted the details below. I've also ran ldd to list that all dependencies are satisfied, and vainfo and glxinfo to show the video config and capabilities. Any help would be appreciated.

sserdyuk wrote:Based on previous post here, Resolve can be used with Intel GPU

Well,

If you followed the Mint Guide, your libraries should be fine for Resolve. The GPU is another story.

On the upper left corner is the 'Search this topic' box. If you search for Intel, you'll see a lot of people have issues with the integrated graphics. 12.5 apparently worked with them better than 14.x.

Kuntal Majumder wrote:I ran Resolve on my integrated GPU but have to install beignet , the OpenCL implementation for Intel GPUs in Linux , though I wont suggest someone to do that. (Got a lot of warnings and popups after opening Resolve).

You could also try downloading Resolve 12.5 for Linux at the BMD website/Support section. See if it starts up proper. In that case, you'd already have a reasonable solution for your needs.

edit. After looking into it, Resolve 14 (on Win/Mac) can be ran on Intel HD Graphics, but it's more demanding than 12.5. An older Intel GPU w/ less memory, like HD4000 (1,5Gb), is expected to be slow and unstable.

I found something interesting which may help to solve the problem. Last night i tried every Version of DaVinci from 14.0 to 14.3 and it seems that this problem does not exist with the Versions 14.0 and 14.0.1. All Versions from 14.1 and higher do have this problem in my case! With 14.0 and 14.01 the software starts without any problem!

Moreover, the messages about the log4cxx are no errors, they are appearing too with my working 14.0 and 14.0.1. Also, the quoted message above (...AppConfig.cpp:159...) appears with the 14.0 and 14.01 but it does not crash because of that!

To solve this problem it would be interesting what's changed from 14.0.1 to 14.1 that DaVinci won't start anymore!I found several differences in the /configs directory (from 14.1 it contains much more) and the installer outputs different messages before Version 14.1. Maybe comparing the relase notes of 14.0.1 and 14.1 would help! I did not found the right thing until now... Maybe user rights on the configs folder? Some new feature in 14.1 which does not have access to a folder? Maybe some missing file or folder which the installer can not create?? Maybe the new user preferences feature introduced in 14.1 ?

I had the problem with several other systems and versions of them too, Ubuntu, elementaryOS, Xubuntu. And i even tried CentOS! The error was the same on all systems and the above described behaviour was repeatable with all of them!

Kuntal Majumder wrote:I ran Resolve on my integrated GPU but have to install beignet , the OpenCL implementation for Intel GPUs in Linux , though I wont suggest someone to do that. (Got a lot of warnings and popups after opening Resolve).

beignet is one choice. it works for very simple applications of OpenCL utilization, but it's often not sufficient to run more demanding code. but there are a few other options around, which may also worth trying -- especially pocl, which often works more reliable, although in many cases not as fast as beignet.

I might actually say you should try an Ubuntu-based OS with Resolve/ATI.

I know Centos is the 'official' OS, but it has more GPU driver compatibility issues than the Ubuntu family. That's why I prefer to opt out of it.

edit. R14 is confirmed by BMD to work on Nvidia (CUDA 3.0) and AMD / Intel (OpenCL 1.2).

Splitting hairs, Linux support is never explicitly mentioned with Intel. BMD have likely never tested it properly, so they lack an answer. But an educated guess would be that the Linux version, like the others, supports all three.

===

edit. the CUDA issue has been seen before, with Debian and integrated graphics. Also, libcudart.so.7.5 is a Resolve dependency, so you may need to have CUDA installed, if only for Resolve.

Sulo Kokki wrote:I know Centos is the 'official' OS, but it has more GPU driver compatibility issues than the Ubuntu family. That's why I prefer to opt out of it.

CentOS is a solid Linux distro, but Ubuntu has it beat, particularly with audio. Let's face it, Ubuntu is one very slick operating system.

But for Fairlight work, we're still stuck with the paid OS's to get the same functionality. I have a Behringer XR-18 connected to a Win7 laptop via USB2. No Decklink needed. And a Behringer X-Touch connected via MIDI for control. Neither are possible at present with any flavor of Linux.

So for now, I need both a XEON machine with a Decklink for video, and a stout Win laptop for audio, but no video out.

Sulo Kokki wrote:But for Fairlight work, we're still stuck with the paid OS's to get the same functionality.

This is true for some aspects. However, there are many different reasons as to why I migrated to Linux. Which meant throwing away 5 Windows licenses & quite some software that came along with the package.The speed, the stability, the customization & the privacy/security of the Linux platform I simply adore. Plus the fact that it brings out the best in people, since all converge for a single goal.

On the Fairlight, I haven't tried it much. I've been trying to get Resolve to bypass the initial loading screen of an Arch installation. Everything seems to be in place, no libraries missing, but it pops an empty splash screen and sits there. It's not a matter of OpenCL, since Fusion recognizes and works perfectly with it.

Sulo Kokki wrote:I know Centos is the 'official' OS, but it has more GPU driver compatibility issues than the Ubuntu family. That's why I prefer to opt out of it.

CentOS is a solid Linux distro, but Ubuntu has it beat, particularly with audio. Let's face it, Ubuntu is one very slick operating system.

I might add there are Ubuntus and then there are Ubuntus. Tried the bleeding edge of the main fork (17.10), found a myriad of issues with Decklink and whatnot. Still dislike Unity. Switched to Mint (Ubuntu 16.04LTS kernel with a Win7 outlook). All those issues went away, the user experience is more to my liking and Resolve turned out solid.

Noel Sterrett wrote:But for Fairlight work, we're still stuck with the paid OS's to get the same functionality.

Agreed. We're still stuck with OS X for the MIDI work. With dualboot, the bother can be managed, but it'd be swell to do it on Linux. The alternative would be to buy a BMD Mini panel, which would frankly be an expensive downgrade.

Vassilis Kontodimas wrote:The speed, the stability, the customization & the privacy/security of the Linux platform I simply adore.

Uh huh. Commercial OS' can't touch that.

Vassilis Kontodimas wrote:I've been trying to get Resolve to bypass the initial loading screen of an Arch installation.

I know it's counterintuitive, but it just might that the software works that way. I recall I had to install the OpenCL dev files to an NVidia system, simply to get the start-up going.

The difference is that nVidia can handle the OpenCL drivers. However, I am not certain how AMD will handle the CUDA, which - in other cases - is inadvisable to combine in an installation. Normally, when it doesn't find the necessary libraries, it used to throw out a warning of "No OpenCL capable hardware", but at least it went past the splash screen. Not this time. And produces zero errors.

With Resolve Studio 14.2.1 for Linux (the first version of Resolve I've ever used under Linux), I am unable to import CinemaDNG folders as such, but need to descend into each CinemaDNG folder and manually select and import all contained files. (Which means that each shot requires its own import individual import operation.)

Is this a known issue or limitation? - I'm running the program under Debian 9 and used makeresolvedeb to convert the install archive into a Debian archive.

Vassilis Kontodimas wrote:The difference is that nVidia can handle the OpenCL drivers. However, I am not certain how AMD will handle the CUDA, which - in other cases - is inadvisable to combine in an installation.

Fair point, didn't know the AMD side is pickier.

You're on Arch? Seen this? They got it done with OpenCL, without CUDA.

Vassilis Kontodimas wrote:The difference is that nVidia can handle the OpenCL drivers. However, I am not certain how AMD will handle the CUDA, which - in other cases - is inadvisable to combine in an installation.

Fair point, didn't know the AMD side is pickier.

You're on Arch? Seen this? They got it done with OpenCL, without CUDA.

Thank you for the recommendation, Sulo. It's the AUR I used for the quick installation, after picking up the archive from the BMD site.

I think I may have detected the problem, which is almost the same Steam had a while ago - and it was a Steam issue.

I find it interesting, personally. As I did also install Resolve 14 Beta on a Manjaro system (I posted a thread in their forum), which is an Arch derivative, and it worked. However, the non-beta (final) seems to be stuck on the AMD side at least.

EDITI'm also including the main, rolling log (that comes next to the Resolve one). It appears that OpenCL is recognized appropriately. Also, as a side note, I uninstalled the AMDGPU drivers without any difference.

Noel Sterrett wrote:You might try just moving the contained files out of the folders. I do this with Sony F5/55 files, and have had no problems.

But that destroys the CinemaDNG format (where the folder structure is part of the format definition).

So something must be wrong.

Perhaps, but I was told the same thing by "experts" for the Sony MXF files, but that has turned out not to be the case. All the metadata is embedded in the files themselves and the directories are a nuisance.

Well, it's hardly practical to have all DNG frames of one project in a single directory - that would be more than 40,000 files in a single directory for half an hour footage. Plus, the allocation of dng and wav files would be screwed up. It's a completely different situation than with MXF files.

So my question to the forum is again: Is this normal behavior? Can you import CinemaDNG folders in Resolve for Linux without having to descend into the CinemaDNG clip directories?

maybe i missed it (it is a rather large thread) but i just downloaded resolve and see it is up to 14.3. the deb converter seems not to be at that version yet, though. will there be an update to the converter for this current version? very much want to try to get resolve running on ubuntu studio 17.10.

George Lockwood wrote:maybe i missed it (it is a rather large thread) but i just downloaded resolve and see it is up to 14.3. the deb converter seems not to be at that version yet, though. will there be an update to the converter for this current version? very much want to try to get resolve running on ubuntu studio 17.10.

thanks,g

Sorry! I've been a little preoccupied lately and missed the 14.3 release. It will be up shortly as soon as I have verified it. Structure for 14.3 looks to be pretty much unchanged so it shouldn't take long.

After installing the converted .deb archive, trying to launch Resolve results in error messages on libssl.so.10 and libcrypto.so.10 missing. I solved this by symlinking libbssl.so.10 to Debian 9's libssl.so.102 and libcrypto.so.10 to Debian 9's libcrypto.so.1.0.2 in /usr/lib/x86_64-linux-gnu/ but wonder whether this is the correct procedure?!?

(Since I am still having the problem that CinemaDNG folders recorded by BM cameras do not get recognized by Resolve as reels - which they do by Resolve for Windows.)

The performance on the exact same project, same machine, same rushes and same grades are very far from the windows version (some clips that i can play realtime in windows are played half realtime in centos), so i’m wondering if i did something wrong?

As a new linux user, i wonder if drivers from elrepo are good or if it’s better (seems more complicated) from nvidias official?

My proc is a bit new but well recognized by centos 7

If you guys have any tips for a linux begginer to optimise my machine i’m all open

1st: I was not able to import any of my videos. I'm shooting with Canon 70D, SJCAM M20 and Mavic Pro drone all of those generating MP4 and MOV H264 videos. It seems for some reason DR14 free version does not like H264 and had to reencode those to DNxHD.

2nd: no sound. I see wave forms and audio meters moving, DR14 is just not producing any sound. In System Settings -> Audio -> Applications I see only "No applications are currently playing or recording audio". "Use system audio" in DR14 settings is grayed out.

Now, after I've read a gazillion pages of this thread I realize there is not sound support for the DR14 free release for Linux, unless a specific PCI card is used. That is a pretty big thing to be left out of the sign-up-here brochure in the marketing department.

It looks like DR is a big deal in the pro world, but if there is a free release I would expect to get it running on a standard Linux configuration.

So, I'm just opting in for the thread email notifications and I hope to see if a solution is posted. Ubuntu 18.04 LTS comes out soon, and I hope DR will get some improvements until then. Until then BMD is getting a big black mark for marketing something Linux-ready when it is clearly not.

If those issues were minor bugs, I would pass them over my head, but DR is not usable at all right now.

I would like to see system audio implemented as well. But with a Decklink card costing $145 you can get two channels of audio. With a $195 BMD Mini Converter SDI to Audio added you get an additional four channels and you're at 5.1 surround. Add another Mini Converter and you're up to 7.1 surround, with a Stereo channel to boot.

If I had my wish, BMD would drop every other OS and focus solely on Linux. But I'm happy that they at least released a Linux version.

Hi, i really need help.I've installed davinci resolve as its instruction, then i followed the tour and quick start as well, and no problem about that. but after i finished the quick start, nothing happen. i try to recall the program, still nothing happen.

then i open terminal and try to call the program on it.it resulted these lines, but no any other window/programme opened:

So far I was able to reel out all graphics elements - as it would seem.

I cleaned up my Antergos & placed in a pure Arch this time (it has better support for software I need, so it's a huge life saver). With that being said, the "cleanest" log I got for unsuccessfuly trying to run Resolve:

I'm also having this issue. Just recently bought a dongle to use the studio-version, but ended up with not being able to start it up at all in Linux. I'm using Antergos (Arch, basically).

My hardware is dual Xeon E5-2683v3, 32Gb of RDimm Ram, and two 980Ti's.

The free version was working just fine. Also, I'm not super-proficient in Linux, so I don't really know how to troubleshoot this at all. I tried uninstalling, making sure the /opt/resolve-studio - folder was totally gone and then reinstalling. Still, it won't start.

As a side note, it works very well in Windows 10, but I'm more comfortable working in Linux since for me It's more responsive when using Blender.

Compilerbau wrote:I found something interesting which may help to solve the problem. Last night i tried every Version of DaVinci from 14.0 to 14.3 and it seems that this problem does not exist with the Versions 14.0 and 14.0.1. All Versions from 14.1 and higher do have this problem in my case! With 14.0 and 14.01 the software starts without any problem!

Compilerbau wrote:I found something interesting which may help to solve the problem. Last night i tried every Version of DaVinci from 14.0 to 14.3 and it seems that this problem does not exist with the Versions 14.0 and 14.0.1. All Versions from 14.1 and higher do have this problem in my case! With 14.0 and 14.01 the software starts without any problem!

I hope I annoy noone if this issue has already been resolved in this thread, the thread is very long and I only skimmed the first few pages

I recently installed DaVinciResolve 14 on Kubuntu 16.04. I used this guide: www(dot)youtube(dot)com/watch?v=7bEyGhm9Gj8&I can run it and import files, but video files aren't being replayed. they show a timecode counting up, but nothing nothing else. Images work, Audiophiles show the waveform but don't play any sound.I tried multiple file formats and codecs.I tried CUDA and OpenGPL