Of course, now R15b1 says it cannot access the existing R14 Cache/Capture folders due to lacking write permissions.

Furthermore, Media page only shows the opt/Resolve/Media mount. The preferences are replicated from R14, but R15b1 cannot access these mounts at all. If I try to add them manually, R15 insists they already exist and refuses.

But. If I add some random folder outside the pre-existing Media pool, all my mountpoints jump up. This appears to affect all the projects in the same db. Other projects still display the write permission errs, for whatever reason.

It is nevertheless a very interesting processor to make video, and the sales of this processor fly away. We are obliged to use ubuntu and the script to run your software. Almost everything works on ubuntu. Almost. We bought the cards to make the sound work. And I seriously look at your last camera. You see even after installing Davinci Resolve 10 times hoping for a proper functioning, I still love you.

But where I do not follow you is why I chose centos, who is always a little late, who is not the most used office solution. With Centos we have to cut our discs in 2, to go from one system to another. It is impractical. when I next update ubuntu 18.04 I promise that I will crush the partition CENTOS. Because your ISO is not functional on AMD. I hope someday to discover DEB that will satisfy the majority of Linux users ... and who will be functional on AMD, for the comfort of the greatest number.

Audacieuse-Galerie Sarl wrote:But where I do not follow you is why I chose centos, who is always a little late, who is not the most used office solution.

CentOS was probably chosen as it and RHEL form the backbone of most studios running Linux. I use it as my main personal workstation’s OS and have no problems with it, and Red Hat are doing a fairly good job of keeping the supported desktop environment modern in the 7.x releases. Another bonus is that in an industry where it is already hard enough as it is to mimic other users/houses environments and toolchains, a long term OS that is rock solid helps ease potential software conflicts and allows the industry to upgrade as a whole when it’s decided to. Sure, we may not have all the newest packages on the planet, but the system is really hard to break and just chews threw tasks with minimal issues.

Honestly, just don’t use BMD’s ISO. Perform a standard CentOS installation then slap Resolve on after. If you check the system requirements of every other major industry tool, they are pretty much built and tested on CentOS.

Hmm i was able to set DaVinci (beta) up on my ArchLinux computer (still having issues on my Thinkpad) - however, my MTS files are importet but offline (argh!), MOV files are audio sources and mp4 only got the audio thumbnail but no content at all, well this is frustrating, anything i can do?

I write it to this thread because i edited MTS files with Windows just fine.

Edit: okey case partially clear now even tho i thought it was working with resolve 14 where sound support was missing in the past on linux: "Cannot find the codec for decoding."

Just want to report that, after running a script to point everything in the right direction, Resolve 15 beta works flawlessly on my Dell XPS 15 running Linux Mint 18.3 on an Nvidia GTX 1050 GPU. I'm also really happy to see that audio works without a hitch. Throw in some h.264 support and you guys will make me a very happy filmmaker!

Sam Weston wrote:Throw in some h.264 support and you guys will make me a very happy filmmaker!

Thank you so much for the script, Sam!I installed Resolve on a Debian 9 distro I placed on an additional SSD, since AMD posted their latest drivers truncated on their website again (143MB, as opposed to the normal ~540MB normal file size). I was able to make it run after copying Resolve's installation folder from main Arch system, which offered its own workaround to avoid using nVidia only drivers. Resolve just stonewalls me due to the lack of MESA OpenGL profiles (most likely), hence the Debian.

Per your h.264, there is a very good workaround. In short, FFMPEG is your friend, since it's a nifty & extremely powerful application that can shift the video encoding, with almost zero (if not fully zero) loss.

If you have a number of files you need to work on, download WinFF FFMPEG GUI from the repository (since Debian 9 has it, it's certain you'll find it for Mint) and create a new preset with the following code:

I'm on Ubuntu 17.10, with a GTX680 and 390.30 but I seem to be getting this issue:

/opt/resolve/bin/resolve: /opt/resolve/bin/../libs/libCg.so: no version information available (required by /opt/resolve/bin/resolve)/opt/resolve/bin/resolve: /opt/resolve/bin/../libs/libCgGL.so: no version information available (required by /opt/resolve/bin/resolve)

I didn't see a specific solution to it. Also tried deleting /opt/resolve and then reinstalling after I updated the nvidia driver, but same issue.

Good find Steve! I was just about to suggest that and you updated while I was writing

Now that I have created a post anyway, I must add a comment to the fix suggested by Sam. It's simple although I would strongly advise against modifying Debian system library directories manually. It's not the Debian way and may cause unexpected and hard to find problems in the long run.

These four lines should cover needed library links for Resolve 14 & 15 on most Debian based distributions but I would still urge people to take care when running the Resolve installer directly. It will do unhealthy stuff to a Debian based system such as Mint and Ubuntu and does not provide a way to reverse the process. I would not run it on any production environment.That's why I wrote the DEB-package creator script

Daniel Tufvesson wrote:I must add a comment to the fix suggested by Sam. It's simple although I would strongly advise against modifying Debian system library directories manually. It's not the Debian way and may cause unexpected and hard to find problems in the long run.

Instead create library symlinks in /opt/resolve/libs/ and the resolve binary will find them.

...

...but I would still urge people to take care when running the Resolve installer directly. It will do unhealthy stuff to a Debian based system such as Mint and Ubuntu and does not provide a way to reverse the process. I would not run it on any production environment.That's why I wrote the DEB-package creator script

Thanks Daniel for this very important remark!

it's really a pleasure, to read, that at least one other user/expert shares my discontent about this kind of really questionable advises...

one other aspect worth mentioning, could be seen in the fact, that the present resolve installer doesn't make any useful checks, if all the tools, which he needs to perform the installation, are already available on the system. that's a very significant flaw, which you will hardly find in similar scripts. but in the actual case of resolve, you definitely have to install at least this list of additional packages [even on a clean CentOS installation!] in advance before the installer will work as expected:

usbutils pciutils psmisc bzip2 unzip rsync

and it's often hard to see, when one of this tools wasn't available, and only some parts of resolve were installed

MikeRochefort wrote:Honestly, just don’t use BMD’s ISO. Perform a standard CentOS installation then slap Resolve on after. If you check the system requirements of every other major industry tool, they are pretty much built and tested on CentOS. Cheers, Mike

We tested this, and resolve was not functional. The color settings were not saved. Now that CENTOS is not going to settle on our new AMD Ryzen 7 , I do not think we can say that this is such a nice and compatible system.

Keep in mind that this is script is also in it's early beta stage.Be careful and keep it far away from production environments!

Almost there!ldd gives me: libssl.so.10 => not found libcrypto.so.10 => not foundOn fresh Debian 9 64 bit setup with makeresolvedeb liteAny ideas? Original setup still has same problems as resolve 14. Thanks for the effort!

Keep in mind that this is script is also in it's early beta stage.Be careful and keep it far away from production environments!

Almost there!ldd gives me: libssl.so.10 => not found libcrypto.so.10 => not foundOn fresh Debian 9 64 bit setup with makeresolvedeb liteAny ideas? Original setup still has same problems as resolve 14. Thanks for the effort!

Audacieuse-Galerie Sarl wrote:We tested this, and resolve was not functional. The color settings were not saved. Now that CENTOS is not going to settle on our new AMD Ryzen 7 , I do not think we can say that this is such a nice and compatible system.

What issues were you running into? CentOS should support the newer chips since the added support for EPYC, but I don’t have any on hand to test or confirm. I just installed Resolve on my workstation running my own CentOS 7.4 config and with the exception of a ‘minor’ mishap with OpenCL (I temporarily bricked my system), everything just works.

I have the program installed and it works for the most part. However, when I open the Color tab there is no video playback in the program monitor, my external monitor or in the scopes. I cannot tell what my adjustments look like as far as color changes are concerned. Also as it plays in color the timeline it is about 1 frame per second.

In the Fairlight tab there are no audio clips present on the timeline. I can see the clips on the Edit tab but not in Fairlight.

Cedric Akins wrote:I have the program installed and it works for the most part. However, when I open the Color tab there is no video playback in the program monitor, my external monitor or in the scopes.

as you are writing in this linux thread, i don't think, you are reporting experiances on "Windows 10 Pro 64-bit". nevertheless it would be useful, if you could mention your actually used linux distribution as well, because the described color panel related issues could perhaps be caused by SELinux or similar peculiarities of your system, but could also have its rational cause in nvida driver version incompatibilities or only partial installation...

Anyone else ever tested the Fusion tab in Resolve15 under Linux?I can import an image sequence into Resolve, then I go to the Fusion tab, hit CTRL + SPACE, type merge to add a merge node, then hit CTRL + SPACE again and type background.

Anyone else ever tested the Fusion tab in Resolve15 under Linux?I can import an image sequence into Resolve, then I go to the Fusion tab, hit CTRL + SPACE, type merge to add a merge node, then hit CTRL + SPACE again and type background.

I can confirm & reported the background/merge issue as a bug. Though I use Shift+Space for the typing menu. It happens when I try to connect the footage to a merge node. Basically anything that changes the footage from being the primary background.

@Vassilis Kontodimas: Under Configuration I switched to "Always run Fusion on CPU" this helped to solve some stability issues.

Thanks for reporting the bug to Blackmagicdesign.I stopped reporting Linux bugs since I had the feeling no one there really cares about feedback and support. (e.g. Still not able to use network rendering in Linux, waiting since months for a response).

Marc Gasser wrote:hanks for reporting the bug to Blackmagicdesign.I stopped reporting Linux bugs since I had the feeling no one there really cares about feedback and support. (e.g. Still not able to use network rendering in Linux, waiting since months for a response).

Yes, use of a good public facing bug reporting/tracking system might help matters. There are lessons to be learned from the old 'The Cathedral and the Bazaar' regarding valuing people who report software bugs:...

Please just do us the kindness of packaging up in Snap, Flatpak or AppImage. It's 2018 and it's a little silly a huge company can't get it together to do this but every single open source competitor can.

Thanks Daniel for the deb packages you have provided for Resolve. Using it I managed to get 14.3 installed on Ubuntu 18.04 and so far it is working well.

The knowledge shared by the more experienced members of this forum is really appreciated.

I'm just a hobbyist considering buying the Linux Studio version, but i need to know if it will import mp4 files and if audio will be functional on the Linux Studio version. It seems from the spec comparison info available on BM's site that it does, but I would like to be absolutely sure. Any further info would be a big help.

Neil Preston wrote:Thanks Daniel for the deb packages you have provided for Resolve. Using it I managed to get 14.3 installed on Ubuntu 18.04 and so far it is working well.

Yes he has been a champion when it comes to .DEB (ubuntu) support/packaging. I am surprised he hasn't been hired by Blackmagic yet!?

Neil Preston wrote:I'm just a hobbyist considering buying the Linux Studio version, but i need to know if it will import mp4 files and if audio will be functional on the Linux Studio version. It seems from the spec comparison info available on BM's site that it does, but I would like to be absolutely sure. Any further info would be a big help.

I purchased the commercial version (studio) and it uses/required nVidia hardware and commercial drivers installed to import H264 (mp4). The free version (as of last I tried) doesn't support it.

Thanks for the information Doug. Looks like the Studio version is going to work for me. It's overkill for what I do, but when it's just a hobby it doesn't always have to make sense. It just needs to be enjoyed.

I'm really glad you guys find my work useful! It has taken fair bit of time and effort to create and maintain makeresolvedeb. I'm a big fan of Resolve and Debian so this was a good match for me. To me a .deb is the only proper way to install Resolve on a Debian based system. I'm actually surprised BMD hasn't released their own .deb yet but the current situation is actually quite good. The openness of the current Resolve installer is what makes makeresolvedeb possible. I was trying to do something similar with the Fusion installer but found no elegant way. Now with Resolve 15 wonderfully including Fusion this situation was automagically solved! Thank you BMD

To give my answer to Neil's question regarding Resolve Studio and mp4 files, I regularly get mp4 material from the GH5 (both 8 and 10 bit) along with files from the DJI Mavic Pro and Spark, and it's working beautifully in the Studio version! If you are a hobbyist running a standalone Ubuntu/Debian system I would actually recommend going for 15.0b2 (current beta) instead of 14.3. In my experience the UI of 15.0b2 is much more responsive compared to 14.3 and the fact that system audio monitoring is working now makes it a huge plus! On my Debian 9 system I actually find 15.0b2 to be more stable than 14.3!

Thanks Daniel for the advice to rather install 15.0b2. which I will do this morning. Before I do that I was wondering if there would be any advantage to first replacing my Ubuntu install with Debian on the desktop that I use for Resolve.

I have an empty drive to use for a Debian Installation, so there is no inconvenience for me to do it.

Daniel Tufvesson wrote:I'm really glad you guys find my work useful! It has taken fair bit of time and effort to create and maintain makeresolvedeb. I'm a big fan of Resolve and Debian so this was a good match for me.

i also like your endeavor to improve the situation for debian users. and your script looks indeed much more acceptable to me, them most of this stupid ad hock hacks, which simply advise to place silly links in the system directories, without considering their debian specific layout and its reasons, don't think about ld.so.conf requirements etc.

Daniel Tufvesson wrote:To me a .deb is the only proper way to install Resolve on a Debian based system.

yes -- that's something, i can 100% agree!

Daniel Tufvesson wrote:I'm actually surprised BMD hasn't released their own .deb yet but the current situation is actually quite good. The openness of the current Resolve installer is what makes makeresolvedeb possible. I was trying to do something similar with the Fusion installer but found no elegant way.

that's again point, which a can't agree. the usual Qt installer framework based alternatives, as for example used by nuke or sgo mistika, can be manually decomposed in a quite similar manner as the actual resolve installer (here is a practical example). but in practice this other kind of installer looks much more user friendly. and as much as i prefer native debian packages, i still have emphasize the fact, that Qt installers are at least compatible to automatic package generation via CheckInstall, which unfortunately isn't the case with resolves present installer.

although i really like your script, i'm still not satisfied by the actual situation. putting everything into a .deb-package and make it proper uninstallable is indeed a very important first step, but it's on the other hand just a part of the whole game. reproducible CI builds and tests, automatically generated dependency graphs, which declare all necessary other installation requirements, and comfortable updates from external repositories, without any need of manual workarounds, are very useful too.

and what's the main issue, all those really trivial fixes to the installer and naming of required libraries, which wouldn't lessen the compatibility in the case of CentOS and RHEL, but would make live much easier for debian/ubuntu/mint users, are still ignored by BMD. that's a really a very frustrating state of things, because you simply can not improve the situation in a significant manner, as long as the upstream source does their best to ignore/boycott any relevant attempts.

nevertheless i'm quite optimistic, that the situation will improve over time. it's very encouraging, how much interest among the linux users 15b already attracted. i think, BMD will have to react sooner or later and improve the software in regard to this little share of customers too.

Daniel Tufvesson wrote: .... I would actually recommend going for 15.0b2 (current beta) instead of 14.3. In my experience the UI of 15.0b2 is much more responsive compared to 14.3 and the fact that system audio monitoring is ....

Thanks Daniel for the advice. I have installed your deb for 15.0b2, but there are 3 problems with lib files:

LibCg.so ... no version info. Resolve requires this.LibCgGL.so ... no version info. Resolve requires this.LibOpenCL.so.1 not found

Help on how to fix this would really be appreciated.Would it be an advantage to replace the Ubuntu 18.04 I’m running, with Debian 9.

Still nothing.I have openssh from debian8 installed over Debian 9.4 as @Daniel Tufvesson mentioned.Nvidia binary from non-free set, as well as nvidia-libopencl1, nvidia-opencl-dev, nvidia-opencl-common

Could Boris' issue perhaps be related to the Nvidia driver version? BMD recommends 390.42 in Linux_Installation_Instructions.pdf. Version 390.48 is available in stretch-backports. That's the one I use to get 15b2 running. 375.82 for example will not work.

Also I would second Martins advise on using nvidia-kernel-dkms. Make sure you have the header files installed for your current kernel (usually linux-headers-amd64) to make dkms happy.

Daniel Tufvesson wrote:Could Boris' issue perhaps be related to the Nvidia driver version? BMD recommends 390.42 in Linux_Installation_Instructions.pdf. Version 390.48 is available in stretch-backports. That's the one I use to get 15b2 running. 375.82 for example will not work.

yes, that's indeed another possible source of troubles.

i personally prefer to run debian 'testing' in rolling release mode (= nvidia-driver version 390.48 right now) on most of my machines, because it's usually more consistent and utilized/debugged by a wider active user community than backport mixes, but in the case of this particular driver, this shouldn't make any difference.

Neil Preston wrote:Thanks Daniel for the deb packages you have provided for Resolve. Using it I managed to get 14.3 installed on Ubuntu 18.04 and so far it is working well.

Yes he has been a champion when it comes to .DEB (ubuntu) support/packaging. I am surprised he hasn't been hired by Blackmagic yet!?

Daniel's script answers to a social call by the Debian community and goes a long way in helping BMD out, by allowing the users a more proper way to install the software. The official alternative is, essentially, install a CentOS. Insult to injury, their official ISO is in dire need of upgrades. Suffice to say, the official support for the Linux port is still seriously lacking.

The current climate is a bit mixed. We got System Audio within a year, because BMD got smart on the matter. Would still like support for Mesa and FFMpeg - and mending that installation. I sometimes wonder whether BMD wants to keep the Linux port weird and unusual. I base this on the notion that they appear a bit casual in developing it to a comparatively acceptable point. Appointing say, Ubuntu, as an officially supported platform would only take a sought-out to Canonical.

v14 was not ready for the greater Linux community. And v15b3 is not exactly there yet, either. At least now, BMD know a lot more about the Linux install than they did the last time around. Some major caveats have been fixed. Users can focus on actually running it.

To be fair, BMD folks here must feel a bit tired with the Linux crowd at times. A very needy bunch, who feel entitled to have certain features with their port. Some more bluntly than others. An emotional thing, Linux. And we really just want the port to to utilize all the beneficial elements available on the platform.

Hi,For my part the transition between the BETA2 to the BETA 3 was perfect. no problem for all my actual projets, everythings rolls. (ubuntu 18.04 makeresolvedeb_15.0b3-1.sh Nvidia driver: 390.48)

- still the permutation screen problem (for the dual screen) maybe ubuntu gnome problem?!- still have crash for one of my complex edition, but now it crash freezing instead of quit.- I don"t have any green bar with the DJI phantom pro4 h264 4K50p H264 format video sources for all my videos projets- Still mising the H264/H265 Export for linux