Blackmagic Forum

Hello all,

I've just purchased a DaVinci Dongle for Linux to export in ProRes. So rare to find! $1650 on eBay...

I'm bored with Hackintosh issues so I'll probably buy the new ThreadRipper generation with 64 cores. I already know a little bit Ubuntu (but not CentOS at all). Can you please confirm DaVinci Studio 15 or 16 works perfectly with Ubuntu? I'll use it with a Decklink 4K Extreme 12G.

Are the DNx export still an issue with AMD/Linux?

Thank you.

alfabuster wrote:Hi. Where you get Davinci Resolve version 15.2.1? Official website propose only 16 and 16.1...

All the versions since the Blackmagic Design acquisition are available, going all the way back to 10.1.5. Just scroll down. https://www.blackmagicdesign.com/suppor ... and-fusion

Lucius Snow wrote:Can you please confirm DaVinci Studio 15 or 16 works perfectly with Ubuntu?

See: viewtopic.php?f=21&t=90190#11

Seth Goldin wrote:

Lucius Snow wrote:Can you please confirm DaVinci Studio 15 or 16 works perfectly with Ubuntu?

See: viewtopic.php?f=21&t=90190#11

I just now tried DaVinci Resolve 15.2.1 on Ubuntu 19.04, have got the same error like 16.0

Code: Select all

/opt/resolve/bin/resolve                                                             
ActCCMessage Already in Table: Code= c005, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c006, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c007, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= 2282, Mode=  0, Level=  0, CmdKey= 8, Option= 0
PnlMsgActionStringAdapter Already in Table: Code= 615e, Mode=  0, Level=  0, CmdKey= -1, Option= 0
15.2.1 (#005) Linux/Clang
Main thread starts: 9D91D640
[0x7fa79d91d640] | Undefined            | INFO  | 2019-09-17 13:58:29,844 | --------------------------------------------------------------------------------
[0x7fa79d91d640] | Undefined            | INFO  | 2019-09-17 13:58:29,844 | Loaded log config from /opt/resolve/configs/log-conf.xml
[0x7fa79d91d640] | Undefined            | INFO  | 2019-09-17 13:58:29,844 | --------------------------------------------------------------------------------
[1]    9462 abort (core dumped)  /opt/resolve/bin/resolve


But I have laptop ASUS TUF Gaming FX505DY, with radeon rx560x mesa driver. I think this is problem. On windows 10 DaVinci works great...

Seth Goldin wrote:

Lucius Snow wrote:Can you please confirm DaVinci Studio 15 or 16 works perfectly with Ubuntu?

See: viewtopic.php?f=21&t=90190#11

I know CentOS is recommended. Well, by the way, they say:

For this reason, we even provide our own ISO for installing the correct version of CentOS with all required dependencies.

Where's this ISO? I can't find it.

There's this direct link: http://downloads.blackmagicdesign.com/D ... OS_7.3.iso

Is is the latest version? Is there any release history logs somewhere? Does it have the Radeon VII drivers included?

Thanks.

EDIT: Ok, the ISO link is inside Linux_Installation_Instructions.pdf that comes with the installer.

Hi Lucius

Look at
viewtopic.php?f=21&t=97863&p=543862&hilit=radeon+VII#p543862

I have both CentOS/Xeon and Ubuntu Studio/Threadripper running 16.1b3 now

I avoid updating CentOS since earlier attempts totally broke CentOS, keep running it from BMD Iso as a reference
Updates of Resolve and Desktop Video have worked on both, I always uninstall, then install the new version

Updates of Ubuntu Studio have been without any problem, both with GPU 1080ti and now Radeon VII
There were more issues with codecs earlier, but it's still complicated which codecs work on which OS/CPU

DNx export on AMD/Linux were broken earlier without any helpful error messages, works now

With Linux you really need the Resolve Studio license, and you've got the exclusive one
Good luck!

Björn

Thank you Bjorn. So now you run the Radeon VII on Ubuntu Studio with full stability / performances?

Have you noticed any disadvantage to run DaVinci Studio on Ubuntu instead of the CentOS Blackmagic official distribution?

Is Ubuntu install more complicated than CentOS? At the moment, I only use it as a live OS with a bootable USB key to format in EXT3. So I'm not a Linux expert.

Why do you say that CentOS is a "boring" OS?

Yes, good performance, no problems
---
Earlier versions of Resolve Linux on Ubuntu were tricky, the installer was just a gigantic shell script without uninstall and with no checks before it started to install things
When something failed/Resolve didn't succeed in starting it was very difficult to clean up, try again

Daniel Tufvesson, creator of the thread made a fantastic script that converted Resolves 'installer' to a proper .deb package, this to keep track of dependencies and also enable a proper uninstall
Only bad thing it disabled BMD Control panel support

Later BMD got the Resolve installer much better, and Daniel's script wasn't required
This also kept Control panel support

I really like Ubuntu studio, it has a 'low latency' kernel which I believe is good for editing, install not more complicated, you can try it from USB stick/DVD without doing permanent install first

I've been working with linux for many years, sometimes boring

CentOS is Red Hat linux 'for free', ambition on both is stability, no extra risks
This means newer HW support, newer 3rd party application versions in the distribution is lacking/very delayed

One example is ImageMagick which on Red Hat/CentOS distribution can be several years old - requires separate compile from source if you need newer features, support for newer file formats, important bug fixes etc

One example from my Threadripper machine, the motherboard included a 10 Gbit enet card, CentOS from BMD didn't support it
Ubuntu just worked on first try!

Latest BMD CentOS ISO now supports the card, but this is typical for Red Hat/CentOS experience
Björn

Centos 8 will be released next week. AFAIK it is supported by BM. But the changes under the hood compared to Centos 7 might cure some problems that we currently have in particular h.264/5. I am not saying it will but it might as most of the graphics stack is different. If any one has tried it with RH8 they could tell us. In any case I will be trying it next week and will report back if it helps.

Björn, that is interesting!

Anyone got any of the Resolve hardware panels working under Debian/Ubuntu (or any other distro for that matter) and mind sharing their setup?

I rented a Micro panel a while back but was unable to get it working before I had to return it.

@ bjornzitting : Can you confirm the Mini Panel work with Ubuntu Studio?

I've read this about requirements:

Linux: CentOS 6.4, Red Hat Enterprise 6.8 and 7.3

Daniel and Lucius
Yes, the micro panel works fine, haven't seen anything not working - but of course I can't test every combination of things others will manage to invent!

As I wrote, after several kludge installs with updates on update, I started clean with a Ubuntu Studio image, 19.04, burned to a DVD

I like burned optical disks for two reasons:
1. Sweden declared a special tax on them many years ago, so I and many others bought a lot ahead of the tax
2. Nothing from the net changes/viruses can update the burned disk if I want to repeat same install later, it's a snapshot of when I collected the content

In the end big USB sticks etc replaced need of burned disks so I still have a good supply of CD/DVD blanks
I think BMD still claims their reference CentOS image has to be burned to a DVD...
---
The clean install of Ubuntu Studio 19.04 I directly updated via the net, then installed the at that time latest Resolve 16 beta
Micro panel worked!
After that I have allowed Ubuntu Studio to upgrade a lot of times, also upgraded Resolve through several 16.0 and 16.1 beta
Never seen a problem with the micro panel after that!

Thanks again Daniel for your script!
It really put pressure on BMD and gave me the courage to try Threadripper with Ubuntu
Björn

Since version 16.0, 16.1b3 I am not able to export H.264 movies.

When selecting:

Format => QuickTime
Codec => H.264
Encoder => NVIDIA


Then hitting render, after one frame I get following error:
Recording Failed.
Recording failed with Error: Failed to encode the video frame.



All other codecs work well.


Edit:
********

I figured out that the issue only appears in the project when using h264 footage together with image sequences (.png, .tga).

Edit2:
******
@Daniel Tufvesson: Tested with Nvidia 430 and Nvidia 435 Driver, Cuda V 10.1

Marc Gasser wrote:Since version 16.0, 16.1b3 I am not able to export H.264 movies.

When selecting:

Format => QuickTime
Codec => H.264
Encoder => NVIDIA


Then hitting render, after one frame I get following error:
Recording Failed.
Recording failed with Error: Failed to encode the video frame.



All other codecs work well.


Edit:
********

I figured out that the issue only appears in the project when using h264 footage together with image sequences (.png, .tga).

I'm having this exact issue, however I do not have any image sequences. It was working perfectly all day, now suddenly I'm having it stop for everything. I've tried multiple codecs and I'm getting nothing. I've exported dozens of projects on this set up, and through monitoring my hardware appears fine. Just wondering if you noticed anything else that maybe helped solve this issue.

bjornzitting wrote:Yes, the micro panel works fine, haven't seen anything not working

Thank you for the information Björn! I will have a go at this again.

Those of you having issues with NVIDIA h.264 encoding, what NVIDIA driver version are you running?

In case this is of interest for any one running Ubuntu.

"Unofficial Radeon ROCm Packages Re-Enable APU Support"
https://www.phoronix.com/scan.php?page= ... APU-Ubuntu

I tried getting DR running on Centos 8 and there is no ROCm support for it and no packages for AMDGPU pro. AMD really seems to be in lala land.

Just upgraded from RHEL7 to RHEL8 on my primary workstation (kernel 4.18.0-80.11.2.el8_0.x86_64). Deployed amdgpu-pro 19.30-855429 (RX 580 GPU). Davinci Resolve 16 works fine.

linuxfreak wrote:Just upgraded from RHEL7 to RHEL8 on my primary workstation (kernel 4.18.0-80.11.2.el8_0.x86_64). Deployed amdgpu-pro 19.30-855429 (RX 580 GPU). Davinci Resolve 16 works fine.

Did you install DKMS and Desktop Video OK as well?


Sent from my iPhone using Tapatalk

Seth Goldin wrote:

linuxfreak wrote:Just upgraded from RHEL7 to RHEL8 on my primary workstation (kernel 4.18.0-80.11.2.el8_0.x86_64). Deployed amdgpu-pro 19.30-855429 (RX 580 GPU). Davinci Resolve 16 works fine.

Did you install DKMS and Desktop Video OK as well?

Yes, the driver installer did add the module to DKMS and I'm also using the amdgpu-pro driver for the desktop.

Code: Select all

# dkms status
amdgpu, 19.30-855429.el8, 4.18.0-80.11.2.el8_0.x86_64, x86_64: installed (original_module exists)


Good to know. As I reported over in this other thread, installing the NVIDIA driver from the .run file and DKMS breaks everything.

Roadblocks for using DaVinci Resolve on CentOS 8
https://r.tapatalk.com/shareLink/topic? ... source=app

Once ELRepo has the NVIDIA driver packaged, I’m guessing CentOS 8 will be usable for those of us with NVIDIA cards.


Sent from my iPhone using Tapatalk

I have DR running on Centos8 + KDE with the amdgpupro drivers. I had to add the amd opencl packages in separately. Seems to work better than it did on RH7. I can run the scopes on the GPU which I couldn't before. Still no x264/5.

(...)

EDIT: I intended to post this in another thread, the Debian focused one that Daniel opened few days ago. Since I dont like to cross post, I'm removing my questions from here

I have a problem running 16.1b3 Studio on Debian 10

I have a dongle, but when I start Resolve it asks me for an Activation Code or Insert the Dongle.
The dongle is already in and it lights Green, but the program doesn't start.

Any help?

Have you tried plugging the dongle into a different port? If you unplug the dongle and plug it back in and do a dmesg what does it show? Try a lsusb and see what it says as well. I am pretty sure you can trade the dongle in for a code as well if that is necessary.

@WrongHP: could you figure out anything?

I tried several drivers and cuda versions.
The weird thing is that on two machines its not working and on the third it works.
All having Ubuntu 18.04.2LTS installed, two having NvidiaRTX graphics, one NvidiaGTX.

The laptop(RTX) which renders h264 without issues runs the Nvidia-driver-435 opensource (by Tuxedo) and
Cuda compilation tools, release 9.1, V9.1.85

Did you try converting movies to h264 with Winff or Handbrake and then opening them on a Win or Osx computer?
Because my h264 converted movies only play on Linux and I have a slight feeling that somewhere there lies the problem...

Could I get some one that is running RH/Centos 7/8 with an AMD GPU that has h.264 as an option on the deliver tab do a rpm -qa and post the results here please.

Thank you.

Trying to run Resolve 16 on Fedora 31. I've got all the dependencies installed, but when I run it there's a segfault pretty much immediately.

Code: Select all

$ /opt/resolve/bin/resolve
ActCCMessage Already in Table: Code= c005, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c006, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c007, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= 2282, Mode=  0, Level=  0, CmdKey= 8, Option= 0
PnlMsgActionStringAdapter Already in Table: Code= 615e, Mode=  0, Level=  0, CmdKey= -1, Option= 0
16.1 (#055) Linux/Clang
Main thread starts: D9BB1C80
[0x7f3dd9bb1c80] | Undefined            | INFO  | 2019-10-23 19:33:18,735 | --------------------------------------------------------------------------------
[0x7f3dd9bb1c80] | Undefined            | INFO  | 2019-10-23 19:33:18,735 | Loaded log config from /home/chris/.local/share/DaVinciResolve/configs/log-conf.xml
[0x7f3dd9bb1c80] | Undefined            | INFO  | 2019-10-23 19:33:18,735 | --------------------------------------------------------------------------------
Segmentation fault (core dumped)

Here's all that shows up in my log:

Code: Select all

[0x7ff13d4a9c80] | Main                 | INFO  | 2019-10-23 19:04:39,148 | Running DaVinci Resolve v16.1.0.055 (Linux/Clang)
[0x7ff13d4a9c80] | Main                 | INFO  | 2019-10-23 19:04:39,148 | Updating display GPU information...

This is on a system with a Ryzen Threadripper 1900x and a Radeon RX 550, using Mesa. I don't need AMDGPU-PRO for this, do I?

You need to get opencl and LLVM working to use Resolve on F31. To the best of my knowledge there is no way to do that on F31. I tried a month ago. There are 3 way to do it with AMD.

1 - ROCM from AMD - AMD won't release code for ROCM on Fedora only RH/Centos or certain other distros. The Centos packages won't on Fedora.
2 - ROCM packaged by Fedora. If this is ever going to work on F31 it will probably have to work this way. Fedora packages every thing needed but the "thunk" part hasn't been updated in forever because the AMD code base is a mess. I know some one was working with them for a way that they could fix it but I don't know if it will ever be completed.
3. AMDGPUPRO - I tried this when the F-31 beta came out and remember it didn't work but I don't remember why.

For me because I need resolve for work I decided to dual boot F31 for my main desktop and Centos 8 for resolve. I can update F31 as often as I want and it won't effect resolve. Is it ideal? No, but it is what works enough for me.

https://github.com/RadeonOpenCompute/ROCm

I was using CentOS 8 on that PC until just recently, I got frustrated with some software that was too out-of-date.

Looks like I'll be going back to it. Maybe I'll try CentOS Stream... whenever they decide to get a recent version of GDM, at least I won't have to wait as long for it.

It's a workstation anyway, not my gaming PC.

Has anyone tried Ubuntu 19.10? I heard Nvidia drivers are included in the package.

Have been running Davinci Resolve Studio on Manjaro for a year now and it has been smooth sailing so far. Just installed Davinci Resolve Studio from AUR and I was good to go. NVIDIA drivers were installed and configured automatically on my system.

kobayashi wrote:I'm happy to report that I've done a clean install of Ubuntu 18.04.2 to give amdgpu-pro 19.30 driver a try and everything is working perfectly now. At full speed

For those that want to give a try, it can be downloaded from AMD, while you indicate your gpu as an RX5700, otherwise the webpage will give you 19.20 download link

I have a Vega56 and is working at full throttle now, had rocm 2.5 and while working fine was crippling card performance, somewhat limiting it (the card was running at lower temps)

from amdgpu-pro you only need the openCL compute bits, so install with the --headless flag, otherwise Fusion viewer will not work.

Standard candle:
66 blur 9fps
30 blur 21fps
18 blur 34fps
9 blur 59fps

6TNR 15fps
4TNR 20fps
2TNR 30fps
1TNR 47fps

noticed in some clip with time warp slowmo went from rendering at 1-1.5fps to 3-4.5fps
This while having a 165W powercap.
Is a standard MSI airboost vega56, no OC

Hi, I have almost the same specs than you, but running Debian with amdgpu-pro 19.30 and Vega 64.
I did exactly the same amdgpu-pro installation procedure, but Resolve 16 crashes on me (Resolve 15 works):

Code: Select all

#TIME Sun Oct 27 18:56:39 2019 - Uptime 00:00:02 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v16.1.0.055 (Linux/Clang)

bin/resolve() [0x530eba9]
bin/resolve() [0x530e39a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x13510) [0x7f1c6c279510]
/opt/amdgpu-pro/lib/x86_64-linux-gnu/libOpenCL.so.1(clGetDeviceInfo+0x8) [0x7f1c7227a178]
bin/resolve() [0x5eb76af]
bin/resolve() [0x5ebc471]
bin/resolve() [0x5e1ff13]
bin/resolve() [0x5e1ffd7]
bin/resolve() [0x2161ecd]
bin/resolve() [0x21662fd]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8fb7) [0x7f1c6c26efb7]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f1c6a2042ef]
Signal Number = 11


Could you please paste the output of your "dpkg -l", so I could check what's different on my system?

Thanks.

So far, not too much luck with Ubuntu 19.10 and nvidia.

My install process: download the latest 16.1 installer and execute the .run file. Provide sudo creds as needed during the install UI prompts.

I can get some playback to start and then then Resolve 16.1 hangs.

I've tried various video configurations for both OpenCL and CUDA.

Code: Select all

trace: Process 12766 attached
restart_syscall(<... resuming interrupted read ...>

) = -1 ETIMEDOUT (Connection timed out)
futex(0x7f8a412a7fa0, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f8a412a7ff0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1572308390, tv_nsec=350183000}, FUTEX_BITSET_MATCH_ANY

is what I'm seeing when this thing hangs.

If I use the operating system's facilities to kill the process the whole box hangs (the OS sends signal 11 on hang). I can successfully get the app to die if I send signal 9 (SIGKILL).

New BMPCC 4k owner.

After a fair bit of fiddling, here's what works for me on Ubuntu 19.10:

nvidia 435 (I have a cuda m5000m on a xeon laptop (Lenovo P70). Needed to add libssl1.0 (I used xenial's deb file).
Using the make dpkg script from www dot danieltufvesson dot com/makeresolvedeb works correctly for me w/ Resolve Studio 16.1.2.

Code: Select all

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.10
DISTRIB_CODENAME=eoan
DISTRIB_DESCRIPTION="Ubuntu 19.10"

dpkg -l | grep nvidia
ii  libnvidia-cfg1-435:amd64                   435.21-0ubuntu2                             amd64        NVIDIA binary OpenGL/GLX configuration library
ii  libnvidia-common-435                       435.21-0ubuntu2                             all          Shared files used by the NVIDIA libraries
rc  libnvidia-compute-390:amd64                390.129-0ubuntu2                            amd64        NVIDIA libcompute package
rc  libnvidia-compute-390:i386                 390.129-0ubuntu2                            i386         NVIDIA libcompute package
rc  libnvidia-compute-418:amd64                418.56-0ubuntu1                             amd64        NVIDIA libcompute package
ii  libnvidia-compute-435:amd64                435.21-0ubuntu2                             amd64        NVIDIA libcompute package
ii  libnvidia-compute-435:i386                 435.21-0ubuntu2                             i386         NVIDIA libcompute package
ii  libnvidia-decode-435:amd64                 435.21-0ubuntu2                             amd64        NVIDIA Video Decoding runtime libraries
ii  libnvidia-decode-435:i386                  435.21-0ubuntu2                             i386         NVIDIA Video Decoding runtime libraries
ii  libnvidia-encode-435:amd64                 435.21-0ubuntu2                             amd64        NVENC Video Encoding runtime library
ii  libnvidia-encode-435:i386                  435.21-0ubuntu2                             i386         NVENC Video Encoding runtime library
ii  libnvidia-fbc1-435:amd64                   435.21-0ubuntu2                             amd64        NVIDIA OpenGL-based Framebuffer Capture runtime library
ii  libnvidia-fbc1-435:i386                    435.21-0ubuntu2                             i386         NVIDIA OpenGL-based Framebuffer Capture runtime library
ii  libnvidia-gl-435:amd64                     435.21-0ubuntu2                             amd64        NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii  libnvidia-gl-435:i386                      435.21-0ubuntu2                             i386         NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii  libnvidia-ifr1-435:amd64                   435.21-0ubuntu2                             amd64        NVIDIA OpenGL-based Inband Frame Readback runtime library
ii  libnvidia-ifr1-435:i386                    435.21-0ubuntu2                             i386         NVIDIA OpenGL-based Inband Frame Readback runtime library
rc  nvidia-compute-utils-390                   390.129-0ubuntu2                            amd64        NVIDIA compute utilities
rc  nvidia-compute-utils-418                   418.56-0ubuntu1                             amd64        NVIDIA compute utilities
ii  nvidia-compute-utils-435                   435.21-0ubuntu2                             amd64        NVIDIA compute utilities
ii  nvidia-cuda-dev                            10.1.168-1build1                            amd64        NVIDIA CUDA development files
rc  nvidia-dkms-390                            390.129-0ubuntu2                            amd64        NVIDIA DKMS package
rc  nvidia-dkms-418                            418.56-0ubuntu1                             amd64        NVIDIA DKMS package
ii  nvidia-dkms-435                            435.21-0ubuntu2                             amd64        NVIDIA DKMS package
ii  nvidia-driver-435                          435.21-0ubuntu2                             amd64        NVIDIA driver metapackage
rc  nvidia-kernel-common-390                   390.129-0ubuntu2                            amd64        Shared files used with the kernel module
rc  nvidia-kernel-common-418                   418.56-0ubuntu1                             amd64        Shared files used with the kernel module
ii  nvidia-kernel-common-435                   435.21-0ubuntu2                             amd64        Shared files used with the kernel module
ii  nvidia-kernel-source-435                   435.21-0ubuntu2                             amd64        NVIDIA kernel source package
ii  nvidia-prime                               0.8.13                                      all          Tools to enable NVIDIA's Prime
ii  nvidia-settings                            435.21-0ubuntu2                             amd64        Tool for configuring the NVIDIA graphics driver
ii  nvidia-utils-435                           435.21-0ubuntu2                             amd64        NVIDIA driver support binaries
ii  screen-resolution-extra                    0.18                                        all          Extension for the nvidia-settings control panel
ii  xserver-xorg-video-nvidia-435              435.21-0ubuntu2                             amd64        NVIDIA binary Xorg driver


dpkg -l | grep opencl
ii  ocl-icd-libopencl1:amd64                   2.2.11-1ubuntu1                             amd64        Generic OpenCL ICD Loader
ii  ocl-icd-opencl-dev:amd64                   2.2.11-1ubuntu1                             amd64        OpenCL development files
ii  opencl-c-headers                           2.2~2019.01.17-g49f07d3-1                   all          OpenCL (Open Computing Language) C header files


dpkg -l | grep libssl
ii  libssl1.0.0:amd64                          1.0.2g-1ubuntu4.15                          amd64        Secure Sockets Layer toolkit - shared libraries
ii  libssl1.1:amd64                            1.1.1d-1+ubuntu19.04.1+deb.sury.org+2       amd64        Secure Sockets Layer toolkit - shared libraries
rc  libssl1.1:i386                             1.1.1d-1+ubuntu19.04.1+deb.sury.org+2       i386         Secure Sockets Layer toolkit - shared libraries

clinfo
Number of platforms                               1
  Platform Name                                   NVIDIA CUDA
  Platform Vendor                                 NVIDIA Corporation
  Platform Version                                OpenCL 1.2 CUDA 10.1.0
  Platform Profile                                FULL_PROFILE
  Platform Extensions                             cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_khr_gl_event cl_nv_create_buffer
  Platform Extensions function suffix             NV

  Platform Name                                   NVIDIA CUDA
Number of devices                                 1
  Device Name                                     Quadro M5000M
  Device Vendor                                   NVIDIA Corporation
  Device Vendor ID                                0x10de
  Device Version                                  OpenCL 1.2 CUDA
  Driver Version                                  435.21
  Device OpenCL C Version                         OpenCL C 1.2
  Device Type                                     GPU
  Device Topology (NV)                            PCI-E, 01:00.0
  Device Profile                                  FULL_PROFILE
  Device Available                                Yes
  Compiler Available                              Yes
  Linker Available                                Yes
  Max compute units                               12
  Max clock frequency                             1050MHz
  Compute Capability (NV)                         5.2
  Device Partition                                (core)
    Max number of sub-devices                     1
    Supported partition types                     None
    Supported affinity domains                    (n/a)
  Max work item dimensions                        3
  Max work item sizes                             1024x1024x64
  Max work group size                             1024
  Preferred work group size multiple              32
  Warp size (NV)                                  32
  Preferred / native vector sizes                 
    char                                                 1 / 1       
    short                                                1 / 1       
    int                                                  1 / 1       
    long                                                 1 / 1       
    half                                                 0 / 0        (n/a)
    float                                                1 / 1       
    double                                               1 / 1        (cl_khr_fp64)
  Half-precision Floating-point support           (n/a)
  Single-precision Floating-point support         (core)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
    Correctly-rounded divide and sqrt operations  Yes
  Double-precision Floating-point support         (cl_khr_fp64)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
  Address bits                                    64, Little-Endian
  Global memory size                              8521711616 (7.936GiB)
  Error Correction support                        No
  Max memory allocation                           2130427904 (1.984GiB)
  Unified memory for Host and Device              No
  Integrated memory (NV)                          No
  Minimum alignment for any data type             128 bytes
  Alignment of base address                       4096 bits (512 bytes)
  Global Memory cache type                        Read/Write
  Global Memory cache size                        589824 (576KiB)
  Global Memory cache line size                   128 bytes
  Image support                                   Yes
    Max number of samplers per kernel             32
    Max size for 1D images from buffer            134217728 pixels
    Max 1D or 2D image array size                 2048 images
    Max 2D image size                             16384x16384 pixels
    Max 3D image size                             4096x4096x4096 pixels
    Max number of read image args                 256
    Max number of write image args                16
  Local memory type                               Local
  Local memory size                               49152 (48KiB)
  Registers per block (NV)                        65536
  Max number of constant args                     9
  Max constant buffer size                        65536 (64KiB)
  Max size of kernel argument                     4352 (4.25KiB)
  Queue properties                               
    Out-of-order execution                        Yes
    Profiling                                     Yes
  Prefer user sync for interop                    No
  Profiling timer resolution                      1000ns
  Execution capabilities                         
    Run OpenCL kernels                            Yes
    Run native kernels                            No
    Kernel execution timeout (NV)                 Yes
  Concurrent copy and kernel execution (NV)       Yes
    Number of async copy engines                  2
  printf() buffer size                            1048576 (1024KiB)
  Built-in kernels                                (n/a)
  Device Extensions                               cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_khr_gl_event cl_nv_create_buffer

NULL platform behavior
  clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...)  NVIDIA CUDA
  clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...)   Success [NV]
  clCreateContext(NULL, ...) [default]            Success [NV]
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT)  No platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU)  No platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM)  Invalid device type for platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL)  No platform

ICD loader properties
  ICD loader Name                                 OpenCL ICD Loader
  ICD loader Vendor                               OCL Icd free software
  ICD loader Version                              2.2.11
  ICD loader Profile                              OpenCL 2.1

dpkg -l | grep cuda
ii  libcudart10.1:amd64                        10.1.168-1build1                            amd64        NVIDIA CUDA Runtime Library
ii  nvidia-cuda-dev                            10.1.168-1build1                            amd64        NVIDIA CUDA development files


I just tested a DCI 4k braw and successfully exported that using the deliver capability which seemed to be able to dump a .mov file just fine.

Since I'm new to Davinci and the whole blackmagic design ecosystem ... this did take a few hours of fiddling with things. I also added the symlinks as indicated here:

Code: Select all

sudo ln -s /usr/lib /usr/lib64

sudo ln -s /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 /usr/lib/libgstreamer-0.10.so.0

sudo ln -s /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0 /usr/lib/libgstbase-0.10.so.0

sudo ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 /usr/lib/libssl.so.10

sudo ln -s /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /usr/lib/libcrypto.so.10


However I'm not sure that's actually necessary as this was prior to running Daniel's deb maker script as resolve remained broken after those changes. Ymmv!

I now have Resolve 16,1,1 working (so far) on a laptop using Ubuntu 19.10 with Nvidia 435 drivers. I first tried installing using the .run file as I had before, and which worked fine with all the 16 beta's. Resolve hung at the splash screen, and then preceded to freeze the system. I then tried installing using Daniel's make deb, and that worked well.

I really can't fathom why BMD chooses to make a .deb install so difficult.

Thanks Daniel.

Noel Sterrett wrote:I now have Resolve 16,1,1 working (so far) on a laptop using Ubuntu 19.10 with Nvidia 435 drivers. I first tried installing using the .run file as I had before, and which worked fine with all the 16 beta's. Resolve hung at the splash screen, and then preceded to freeze the system. I then tried installing using Daniel's make deb, and that worked well.

I really can't fathom why BMD chooses to make a .deb install so difficult.

Thanks Daniel.

You are welcome Noel. I'm glad you got it running. I fully agree. BMD are really close now to making Resolve run on Debian out of the box. They really only need to change two string constants in the code for their dynamic lib loading. When that's done packaging it all in a .deb is very straight forward. They are already doing a great job with Desktop Video and the BMRAW player so they clearly know how to do it.

Until then we can use things like makeresolvedeb. Resolve paired with the Nvidia 435 driver has been very stable for me so far.

Daniel Tufvesson wrote:You are welcome Noel. I'm glad you got it running.

Well, almost. I tried 16.1.1 with makeresolvedeb on a second Ubuntu system (19.04). Resolve is fine, but the Mini Panel is no longer recognized.

Panel.log:

Code: Select all

opened log file
Opening communication to resolve..
Failed to create listener
Unsupported DaVinci Panel API Version (0.0), please update
Resolve discovery

ResolveDebug_1.txt:

Code: Select all

[0x7f872a081700] | SyManager            | ERROR | 2019-11-06 14:12:01,633 | Failed to connect to panel socket

SY panel handler thread starts: 2A081700
Exit SY panel handler


The Mini Panel works fine with 16.1b1, which installs from just the .run file. But when installed with the .run file, 16.1b3, 16.1 and 16.1.1, all crash in the same manner:

Code: Select all

#TIME Wed Nov  6 13:43:31 2019 - Uptime 00:00:02 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v16.1.1.005 (Linux/Clang)

/opt/resolve/bin/resolve() [0x5382759]
/opt/resolve/bin/resolve() [0x5381f4a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x13f40) [0x7f551360df40]
Signal Number = 11


I have confirmed that 'DaVinci Resolve Panels Setup' works with 16.1.1, and is able to change the Mini Panel network settings. It just won't control Resolve.

It seems now I'm stuck with the 16.1b1 in order to use the Mini Panel.

Any suggestions would be most welcome.

I almost managed to install Resolve 16.1 on Ubuntu 18.04.3 with this graphic-card: Intel® UHD Graphics (Whiskey Lake 3x8 GT2)
The first launch was very promising, i saw the Tour which is shown the first time started and also got the system check, which promted that with my graphic-card i may have limited possibilities but in total everything would be all right.

Now when launching the program.. nothing happens!

There is a promt showing

resolve crashed with SIGABRTin_GI_raise()

In the shell i tried out "ldd /opt/resolve/bin/resolve" and no libraries seem to be missing.
"/opt/resolve/bin/resolve" gives the following result:

Code: Select all

ActCCMessage Already in Table: Code= c005, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c006, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c007, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= 2282, Mode=  0, Level=  0, CmdKey= 8, Option= 0
PnlMsgActionStringAdapter Already in Table: Code= 615e, Mode=  0, Level=  0, CmdKey= -1, Option= 0
16.1 (#055) Linux/Clang
Main thread starts: 18F29000
log4cxx: setFile(./logs/rollinglog.txt,true) call failed.
log4cxx: IO Exception : status code = 2
[0x7fec18f29000] | Undefined            | INFO  | 2019-11-06 21:07:25,567 | --------------------------------------------------------------------------------
log4cxx: No output stream or file set for the appender named [RollLogAppender].
[0x7fec18f29000] | Undefined            | INFO  | 2019-11-06 21:07:25,568 | Loaded log config from /home/chr/.local/share/DaVinciResolve/configs/log-conf.xml
[0x7fec18f29000] | Undefined            | INFO  | 2019-11-06 21:07:25,568 | --------------------------------------------------------------------------------
Abandon (core dumped)


I want to thank Daniel Tufvesson: Thank you for your great work with the installation-script!! Please, can anyone give advice what is wrong with my installation? Thx Chris

Anyone got Resolve 16.1.1 working on Fedora 31?
When trying to start I get is this log:

Code: Select all

[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:29,878 | Running DaVinci Resolve v16.1.1.005 (Linux/Clang)
[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:29,880 | Updating display GPU information...


==========[CRASH DUMP]==========
Please send this to support:

#TIME Wed Nov  6 20:51:30 2019 - Uptime 00:00:00 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v16.1.1.005 (Linux/Clang)

./resolve() [0x530ff19]
./resolve() [0x530f70a]
/lib64/libpthread.so.0(+0x14b20) [0x7f8ce4a5bb20]
[0x7f8cce95a4e0]
Signal Number = 11

================================
[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:30,072 | Updating display GPU information...
[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:30,072 | Detecting Main Display properties
[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:30,075 | Process to detect main display has finished
[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:30,079 | Fallback process to detect main display has finished
[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:30,079 | GPU Name = 'NVIDIA GeForce GTX 980', Main display = 0
[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:30,089 | 1 NVIDIA GPUs (excluding display GPU) found. Using CUDA for processing.
[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:30,089 | Not GLmap capable. GPUs: 1 discrete, 0 integrated, 0 external. Auto mapping, CUDA processing, main display not on external GPU.
[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:30,089 | Setting LsManager.3.NumGPUs = 1
[0x7f8ce1655c80] | IO                   | INFO  | 2019-11-06 20:51:30,089 | RED InitializeSdk with library path at /opt/resolve/libs
[0x7f8ce1655c80] | IO                   | INFO  | 2019-11-06 20:51:30,136 | R3DAPI 7.1.0-3YM06 (20180720 L64S) R3DSDK 7.1.0-3YM06 (20180720 L64D) RED CUDA 7.1.0-45494 (20180721) RED OPENCL 7.1.0-45494 (20180721) [/opt/resolve/libs/] init is successful
[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:30,136 | 0 RED rocket cards available
There are 1 GPUs in the system.
libDeckLinkAPI.so: cannot open shared object file: No such file or directory
[0x7f8ce1655c80] | Main                 | INFO  | 2019-11-06 20:51:30,137 | Decklink model name: '', version: ''
[0x7f8ce1655c80] | CrashReport          | ERROR | 2019-11-06 20:51:30,821 | Compress() : Failed to add file:/home/lmueller/.local/share/DaVinciResolve/configs/UI.preset to archive.
[0x7f8ce1655c80] | CrashReport          | ERROR | 2019-11-06 20:51:30,821 | Compress() : Failed to add file:/home/lmueller/.local/share/DaVinciResolve/configs/config.user.xml to archive.
[0x7f8ce1655c80] | CrashReport          | ERROR | 2019-11-06 20:51:30,821 | Compress() : Failed to add file:/home/lmueller/.local/share/DaVinciResolve/Fusion/Profiles/Default/Fusion.prefs to archive.
QCoreApplication::arguments: Please instantiate the QApplication object first
ASSERT failure in QList<T>::operator[]: "index out of range", file /usr/local/Components/qt-5.4.1+dav_3/dev/linux/include/QtCore/qlist.h, line 486


==========[CRASH DUMP]==========
Please send this to support:

#TIME Wed Nov  6 20:51:30 2019 - Uptime 00:00:00 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v16.1.1.005 (Linux/Clang)

./resolve() [0x530ff19]
./resolve() [0x530f70a]
/lib64/libpthread.so.0(+0x14b20) [0x7f8ce4a5bb20]
/lib64/libc.so.6(gsignal+0x145) [0x7f8ce2a78625]
/lib64/libc.so.6(abort+0x12b) [0x7f8ce2a618d9]
/opt/resolve/bin/../libs/libQt5Core.so.5(+0x8baa6) [0x7f8d0eaa8aa6]
/opt/resolve/bin/../libs/libQt5Core.so.5(_ZNK14QMessageLogger5fatalEPKcz+0x121) [0x7f8d0eaaa5c1]
/opt/resolve/bin/../libs/libQt5Core.so.5(+0x88a97) [0x7f8d0eaa5a97]
./resolve() [0x1f28daa]
./resolve() [0x1f285e3]
./resolve() [0x530fac5]
/lib64/libpthread.so.0(+0x14b20) [0x7f8ce4a5bb20]
[0x7f8cce95a4e0]
Signal Number = 6

================================


Noel Sterrett wrote:I have confirmed that 'DaVinci Resolve Panels Setup' works with 16.1.1, and is able to change the Mini Panel network settings. It just won't control Resolve.

It seems now I'm stuck with the 16.1b1 in order to use the Mini Panel.

Any suggestions would be most welcome.

I just discovered that sometime during the beta phase for some reason DaVinciPanelDaemon supplied in the installer archive lost the executable flag. What if you manually set the x flag? Does that make the panel work?

Code: Select all

sudo chmod +x /opt/resolve/bin/DaVinciPanelDaemon

I don't have a panel so it's difficult for me to verify this unfortunately.

Christoph05 wrote:I almost managed to install Resolve 16.1 on Ubuntu 18.04.3 with this graphic-card: Intel® UHD Graphics (Whiskey Lake 3x8 GT2)
The first launch was very promising, i saw the Tour which is shown the first time started and also got the system check, which promted that with my graphic-card i may have limited possibilities but in total everything would be all right.

Now when launching the program.. nothing happens!

I'm afraid that currently Intel GPU's are not compatible with Resolve for Linux. Most stable option right now is NVIDIA.

Daniel Tufvesson wrote:I'm afraid that currently Intel GPU's are not compatible with Resolve for Linux.

yes -- an equal support for intel integrated GPU capabilities like on the other operating systems is one very unpleasant and in fact unnecessary [because intel provides the required support for linux as well!] peculiarity of the linux edition, but the fact, that BMD doesn't even report the cause of the consequent actual execution abort [like in most other cases] in a more user friendly and human comprehensible way is IMHO an even more unsatisfying aspect, which is hardly excusable in professional software for serious practical use.

Cobinja wrote:I just discovered that sometime during the beta phase for some reason DaVinciPanelDaemon supplied in the installer archive lost the executable flag. What if you manually set the x flag? Does that make the panel work?

I won't be able to try that for a few days, but I noticed that the DaVinciPanelDaemon is not set as executable on another machine, so that may well be the problem.

Thanks for the tip.

Daniel Tufvesson wrote:I just discovered that sometime during the beta phase for some reason DaVinciPanelDaemon supplied in the installer archive lost the executable flag. What if you manually set the x flag? Does that make the panel work?

Code: Select all

sudo chmod +x /opt/resolve/bin/DaVinciPanelDaemon

I don't have a panel so it's difficult for me to verify this unfortunately.

No need to verify, the Mini Panel now works!

Can't thank you enough!

Noel Sterrett wrote:

Daniel Tufvesson wrote:I just discovered that sometime during the beta phase for some reason DaVinciPanelDaemon supplied in the installer archive lost the executable flag. What if you manually set the x flag? Does that make the panel work?

Code: Select all

sudo chmod +x /opt/resolve/bin/DaVinciPanelDaemon

I don't have a panel so it's difficult for me to verify this unfortunately.

No need to verify, the Mini Panel now works!

Can't thank you enough!

That's great! I'm glad we found it. Do you have the panel connected using USB or Ethernet? (Both working?)

Daniel Tufvesson wrote:That's great! I'm glad we found it. Do you have the panel connected using USB or Ethernet? (Both working?)

I've tried both and both seem to be working. I haven't had time to see if they are solid, as there have been disconnect issues especially with Ethernet. But at least the Mini Panel is recognized.

Cheers.

WrongHP wrote:

Marc Gasser wrote:Since version 16.0, 16.1b3 I am not able to export H.264 movies.

When selecting:

Format => QuickTime
Codec => H.264
Encoder => NVIDIA


Then hitting render, after one frame I get following error:
Recording Failed.
Recording failed with Error: Failed to encode the video frame.



All other codecs work well.


Edit:
********

I figured out that the issue only appears in the project when using h264 footage together with image sequences (.png, .tga).

I'm having this exact issue, however I do not have any image sequences. It was working perfectly all day, now suddenly I'm having it stop for everything. I've tried multiple codecs and I'm getting nothing. I've exported dozens of projects on this set up, and through monitoring my hardware appears fine. Just wondering if you noticed anything else that maybe helped solve this issue.

I'm noticing this happen when using NVDEC on some MOV-wrapped H.264 footage from a Canon 5D Mk III and trying to use NVENC to encode MOV-wrapped H.264. Curiously, encoding to HEVC ["H.265"] in MOV works fine.

This is on:

• DaVinci Resolve Studio 16.1.1.005
• CentOS Linux release 8.0.1905 (Core)
• Kernel 4.18.0-80.11.2.el8_0.x86_64
• Intel Xeon Gold 6136
• NVIDIA 440.31
• GeForce GTX 1080 Ti

Seth Goldin wrote:

WrongHP wrote:

Marc Gasser wrote:Since version 16.0, 16.1b3 I am not able to export H.264 movies.

When selecting:

Format => QuickTime
Codec => H.264
Encoder => NVIDIA


Then hitting render, after one frame I get following error:
Recording Failed.
Recording failed with Error: Failed to encode the video frame.



All other codecs work well.


Edit:
********

I figured out that the issue only appears in the project when using h264 footage together with image sequences (.png, .tga).

I'm having this exact issue, however I do not have any image sequences. It was working perfectly all day, now suddenly I'm having it stop for everything. I've tried multiple codecs and I'm getting nothing. I've exported dozens of projects on this set up, and through monitoring my hardware appears fine. Just wondering if you noticed anything else that maybe helped solve this issue.

I'm noticing this happen when using NVDEC on some MOV-wrapped H.264 footage from a Canon 5D Mk III and trying to use NVENC to encode MOV-wrapped H.264. Curiously, encoding to HEVC ["H.265"] in MOV works fine.

This is on:

• DaVinci Resolve Studio 16.1.1.005
• CentOS Linux release 8.0.1905 (Core)
• Kernel 4.18.0-80.11.2.el8_0.x86_64
• Intel Xeon Gold 6136
• NVIDIA 440.31
• GeForce GTX 1080 Ti

I should now add that I have some XAVC-I footage that would not render on Linux with the above specs to either H.264 or HEVC, but worked totally fine on with a different, Windows boot drive on the same machine:

• DaVinci Resolve Studio 16.1.1
• Windows 10 1909 18363.476
• NVIDIA driver 441.12

I guess something's gummed up with with the 440.31 NVIDIA driver.

Seth Goldin wrote:

Seth Goldin wrote:

WrongHP wrote:
I'm having this exact issue, however I do not have any image sequences. It was working perfectly all day, now suddenly I'm having it stop for everything. I've tried multiple codecs and I'm getting nothing. I've exported dozens of projects on this set up, and through monitoring my hardware appears fine. Just wondering if you noticed anything else that maybe helped solve this issue.

I'm noticing this happen when using NVDEC on some MOV-wrapped H.264 footage from a Canon 5D Mk III and trying to use NVENC to encode MOV-wrapped H.264. Curiously, encoding to HEVC ["H.265"] in MOV works fine.

This is on:

• DaVinci Resolve Studio 16.1.1.005
• CentOS Linux release 8.0.1905 (Core)
• Kernel 4.18.0-80.11.2.el8_0.x86_64
• Intel Xeon Gold 6136
• NVIDIA 440.31
• GeForce GTX 1080 Ti

I should now add that I have some XAVC-I footage that would not render on Linux with the above specs to either H.264 or HEVC, but worked totally fine on with a different, Windows boot drive on the same machine:

• DaVinci Resolve Studio 16.1.1
• Windows 10 1909 18363.476
• NVIDIA driver 441.12

I guess something's gummed up with with the 440.31 NVIDIA driver.

Just uninstalled 440.31 on the CentOS 8 disk and installed 430.64 instead, and tried to render again. Same error when trying to render to H.264, but curiously, HEVC worked perfectly.

Can confirm, can't render NVIDIA accelerated H264.

Manjaro Gnome
Linux 5.3.11
NVIDIA 440.31

A new long-lived branch NVIDIA driver dropped on Friday, 440.36. Going to install and test for H.264 and HEVC encoding.