DaVinci Resolve on Linux - Install issues

I can't tell if Resolve is 'working' or not, judging by this thread...

yes -- it's more or less working -- since version 15 even with native audio support via your usual sound card.

but it's worth mentioning, that the actual codec support in the free version for linux is much worse than for mac os or windows (i.e. you'll have to reencode most footage by ffmpeg before you can use it in resolve on linux systems).

the installer is still a horrible inferior crap and only supports CentOS. therefore most users actually utilize community supported hacks to get resolve running on their preferred distributions. repacking and more user friendly support by distribution maintainers resp. more user friendly integration into existing widely used linux distributions is prohibited by the rather restrictive EULA and software download procedures.

it's still necessary to have a powerful machine with at least a recent nvida card with lots of VRAM (maybe some AMD cards may work as well) to run resolve on linux. iGPUs are not sufficient, although they may work for resolve on other operating systems.

it's also useful to communicate to new users, that you will not get any continuous full screen preview (e.g. while editing) on a second second screen in resolve before you purchase a blackmagic video i/o card or adapter. using only the GUI preview resp. computer monitors instead is rather unsatisfying, because the software calibration LUT entries do not work reliable and consistent in all modes of the application.

but beside all this rather unpleasant irks and tons of of other bugs, it's IMHO still the most powerful affordable NLE-like solution on linux right now! it's simply the only one, which allows unlimited import/export of projects in common exchange formats -- that's IMHO the most important and unique feature, which i really miss in all other freely available linux solutions. nevertheless i still think, we shouldn't forget all the other serious linux alternatives (natron, blender, ardour, nuke non-commercial, sgo mistika, autodesk flame, baselight). in the long run it's very important that the whole ecosystem prospers and gets better and better over time and others don't wither in the shadow of only one popular product.

I can't tell if Resolve is 'working' or not, judging by this thread...

yes -- it's more or less working -- since version 15 even with native audio support via your usual sound card.

but it's worth mentioning, that the actual codec support in the free version is much worse than for mac os or windows (i.e. you'll have to reencode most footage by ffmpeg before you can use it in resolve on linux systems).

the installer is still a horrible inferior crap and only supports CentOS. therefore most users actually utilize community supported hacks to get resolve running on their preferred distributions. repacking and more user friendly support by distribution maintainers resp. more user friendly integration into existing widely used linux distributions is prohibited by the EULA and software download procedures.

it's still necessary to have a powerful machine with at least a recent nvida card with lots of VRAM (maybe some AMD cards may work as well) to run resolve on linux. iGPUs are not sufficient, although they may be enough for resolve on the other operating systems.

it's also useful to communicate to new users, that you will not get any continuous full screen preview (e.g. while editing) on a second second screen in resolve before you purchase a blackmagic video i/o card or adapter. using only the GUI preview resp. computer monitors instead is rather unsatisfying, because the software calibration LUT entries do not work reliable and consistent in all modes of the application.

but beside all this rather unpleasant irks and tons of of other bugs, it's IMHO still the most powerful affordable NLE-like solution on linux right now! it's simply the only one, which allows unlimited import/export of projects in common exchange formats -- that's IMHO the most important and unique feature, which i really miss in all other freely available linux solutions. nevertheless i still think, we shouldn't forget all the other serious linux alternatives (natron, nuke non-commercial, sgo mistika, autodesk flame, baselight). in the long run it's very important that the whole ecosystem prospers and gets better and better over time and others don't withers in the shadow of only one popular product.

Cool, thanks. Very informative and interesting. There was a 'state of video editing on linux' article that I read that seemed to place emphasis on a bunch of editors and sort of mentioned Resolve near the end. It made it sound like things weren't mature enough to be mentioned compared to the alternatives.

We can include a caveat RE the free version. We do have dongle licenses for Resolve so we shouldn't run into that issue (is that correct?).

Hardware wise, it'll be interesting to see the performance difference between platforms. We can certainly throw what we have at it and see. Maybe 4 Quadros and a 26 CPU station. It seems like using a Decklink was required prior to 15 but that's no longer an issue. Are there hardware incompatibilities we should look out for?

We ARE going to look at other 'editors' including Natron, Kdenlive, and Blender. But from what I've been reading, the scene's still kind of jank.

There was a guide to install on Ubuntu that a Google search had turned up. Do you know if that's feasible or should we stick to CentOS?

I have resolve 15.1.1 installed on a Lenovo T440s with Intel 4400 under Mint 19 after proceeding with the script, then I have still installed opencl (see code info opencl). resolve also starts, but then stops and obviously can not find a compatible opencl GPU. what could you do?

I know that the performance will not be so great, but wanted to use the system but still so learning.

thanks jojo


Number of platforms 2
Platform Name Intel Gen OCL Driver
Platform Vendor Intel
Platform Version OpenCL 2.0 beignet 1.3
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_byte_addressable_store cl_khr_3d_image_writes cl_khr_image2d_from_buffer cl_khr_depth_images cl_khr_spir cl_khr_icd cl_intel_accelerator cl_intel_subgroups cl_intel_subgroups_short cl_khr_gl_sharing
Platform Extensions function suffix Intel

Platform Name Clover
Platform Vendor Mesa
Platform Version OpenCL 1.1 Mesa 18.0.5
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA

Platform Name Intel Gen OCL Driver
Number of devices 1
Device Name Intel(R) HD Graphics Haswell Ultrabook GT2 Mobile
Device Vendor Intel
Device Vendor ID 0x8086
Device Version OpenCL 1.2 beignet 1.3
Driver Version 1.3
Device OpenCL C Version OpenCL C 1.2 beignet 1.3
Device Type GPU
Device Profile FULL_PROFILE
Device Available Yes
Compiler Available Yes
Linker Available Yes
Max compute units 20
Max clock frequency 1000MHz
Device Partition (core)
Max number of sub-devices 1
Supported partition types None, None, None
Max work item dimensions 3
Max work item sizes 512x512x512
Max work group size 512
Preferred work group size multiple 16
Preferred / native vector sizes
char 16 / 8
short 8 / 8
int 4 / 4
long 2 / 2
half 0 / 8 (n/a)
float 4 / 4
double 0 / 2 (n/a)
Half-precision Floating-point support (n/a)
Single-precision Floating-point support (core)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Correctly-rounded divide and sqrt operations No
Double-precision Floating-point support (n/a)
Address bits 32, Little-Endian
Global memory size 2147483648 (2GiB)
Error Correction support No
Max memory allocation 1610612736 (1.5GiB)
Unified memory for Host and Device Yes
Minimum alignment for any data type 128 bytes
Alignment of base address 1024 bits (128 bytes)
Global Memory cache type Read/Write
Global Memory cache size 8192 (8KiB)
Global Memory cache line size 64 bytes
Image support Yes
Max number of samplers per kernel 16
Max size for 1D images from buffer 65536 pixels
Max 1D or 2D image array size 2048 images
Base address alignment for 2D image buffers 4096 bytes
Pitch alignment for 2D image buffers 1 pixels
Max 2D image size 8192x8192 pixels
Max 3D image size 8192x8192x2048 pixels
Max number of read image args 128
Max number of write image args 8
Local memory type Local
Local memory size 65536 (64KiB)
Max number of constant args 8
Max constant buffer size 134217728 (128MiB)
Max size of kernel argument 1024
Queue properties
Out-of-order execution No
Profiling Yes
Prefer user sync for interop Yes
Profiling timer resolution 80ns
Execution capabilities
Run OpenCL kernels Yes
Run native kernels Yes
SPIR versions 1.2
printf() buffer size 1048576 (1024KiB)
Built-in kernels __cl_copy_region_align4;__cl_copy_region_align16;__cl_cpy_region_unalign_same_offset;__cl_copy_region_unalign_dst_offset;__cl_copy_region_unalign_src_offset;__cl_copy_buffer_rect;__cl_copy_image_1d_to_1d;__cl_copy_image_2d_to_2d;__cl_copy_image_3d_to_2d;__cl_copy_image_2d_to_3d;__cl_copy_image_3d_to_3d;__cl_copy_image_2d_to_buffer;__cl_copy_image_3d_to_buffer;__cl_copy_buffer_to_image_2d;__cl_copy_buffer_to_image_3d;__cl_fill_region_unalign;__cl_fill_region_align2;__cl_fill_region_align4;__cl_fill_region_align8_2;__cl_fill_region_align8_4;__cl_fill_region_align8_8;__cl_fill_region_align8_16;__cl_fill_region_align128;__cl_fill_image_1d;__cl_fill_image_1d_array;__cl_fill_image_2d;__cl_fill_image_2d_array;__cl_fill_image_3d;
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_byte_addressable_store cl_khr_3d_image_writes cl_khr_image2d_from_buffer cl_khr_depth_images cl_khr_spir cl_khr_icd cl_intel_accelerator cl_intel_subgroups cl_intel_subgroups_short cl_khr_gl_sharing

Platform Name Clover
Number of devices 0

NULL platform behavior
clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) Intel Gen OCL Driver
clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [Intel]
clCreateContext(NULL, ...) [default] Success [Intel]
clCreateContext(NULL, ...) [other] <error: no devices in non-default plaforms>
clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) Success (1)
Platform Name Intel Gen OCL Driver
Device Name Intel(R) HD Graphics Haswell Ultrabook GT2 Mobile
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) Success (1)
Platform Name Intel Gen OCL Driver
Device Name Intel(R) HD Graphics Haswell Ultrabook GT2 Mobile
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) Success (1)
Platform Name Intel Gen OCL Driver
Device Name Intel(R) HD Graphics Haswell Ultrabook GT2 Mobile

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

There is the great makeresolvedeb.sh script which turns the RPM package into a Debian package.
I could so far install all 15.x versions on Debian 9 and Ubuntu 18 without any problems..

Well..the crashes still exist which has nothing to do with not running on CentOS (o;

I also use kdenlive...but mostly for just cutting commercials out of TV recordings captured with a DVB-C card...
and kdenlive can render the output with help of a Nvidia GPU as well...

Performance wise I would say that DRS feels snappier on Linux than on macOS 10.12 or 10.13. But I didn't compared rendering speeds as both my macOS and Debian system have different GPUs...maybe for xmas I build a new macOS Mojave system when hopefully Nvidia released new drivers for it (o;

I looked at other video editors as well for Linux...Blender is more a 3d program for me...and there is a node-based opensource editor which looks very complicated...but can't remember the name...

Despite the facts that Fusion is only 70% - 80% usable on Linux I very much like the interface of it...

And I still hope that BMD will release Fusion Studio 9 for Linux which also runs with the Davinci Resolve Studio dongle until all Fusions crashes are sorted out (o;

That's not surprising if that was case but I do believe this is a bug specific to linux and resolve 15. Here's why I think that...

1) Worked on resolve 14.
2) I confirmed, the mp4's loaded perfectly with resolve 15 on OSX, so it's not a license issue there.
3) Log files state the codec cannot be found

Well, while the ffmpeg conversion does work as a work around, I would prefer a proper solution.

Anyone know where resolve is looking for codecs or a way to turn up logging to show?

Hey mrooted, I think you got missed, but unless you shelled out for the Studio version, you probably can't import any media in h.264, or really any format that comes out of a consumer camera... I've pretty much resigned myself to using ffmpeg to transcode my GoPro and Lumix G7 footage to ProRes for editing because I need that $300 or so to go towards a graphics card that'll run Resolve better!

This is the syntax I use, but it's very slow and makes files about 10x the size of the original, however, it actually plays back nicely in Resolve.

Code: Select all

ffmpeg -i inputfile.MP4 -vcodec prores -acodec pcm_s16le -ar 48000 -ac 2 -f mov outputfile.mov

The Linux version has many bugs since 15.0 and nothings seems to be changed...
At least GPU errors are gone...but looks like GPU is just turned off in Fusion as it is much slower now...

Resolve comes with its own codecs installed under /opt/resolve/something...at least I remember I saw libavcodec and the like...also libopencv for tracking...

You could do a ldd /opt/resolve/bin/resolve too all the libs it uses...

does anyone have resolve 15 on a laptop running linux with intel with integrated GPU on? and could report about it? which linux? which graphics driver? which GPU?

Thanks.

jojo2203

Hi there,
at first resolve 15 worked fine with /opt/resolve/bin/resolve but since yesterday starts only with sudo /opt/resolve/bin/resolve.
/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
15.1.1 (#005) Linux/Clang
Main thread starts: 7704FB40
log4cxx: setFile(./logs/rollinglog.txt,true) call failed.
log4cxx: IO Exception : status code = 2
[0x7f2a7704fb40] | Undefined | INFO | 2018-10-13 10:25:39,013 | --------------------------------------------------------------------------------
log4cxx: No output stream or file set for the appender named [RollLogAppender].
[0x7f2a7704fb40] | Undefined | INFO | 2018-10-13 10:25:39,013 | Loaded log config from /opt/resolve/configs/log-conf.xml
[0x7f2a7704fb40] | Undefined | INFO | 2018-10-13 10:25:39,013 | --------------------------------------------------------------------------------
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,014 | Running DaVinci Resolve v15.1.1.005 (Linux/Clang)
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,026 | Updating display GPU information...
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,040 | Detecting Main Display properties
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,044 | Process to detect main display has finished
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,051 | Fallback process to detect main display has finished
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,051 | GPU Name = 'NVIDIA GeForce GTX 1060 3GB', Main display = 0
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,054 | 1 NVIDIA GPUs (excluding display GPU) found. Using CUDA for processing.
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,055 | Not GLmap capable. GPUs: 1 discrete, 0 integrated, 0 external. Auto mapping, CUDA processing, main display not on external GPU.
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,055 | Setting LsManager.3.NumGPUs = 1
[0x7f2a7704fb40] | IO | INFO | 2018-10-13 10:25:39,055 | RED InitializeSdk with library path at /opt/resolve/libs
[0x7f2a7704fb40] | IO | INFO | 2018-10-13 10:25:39,097 | 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
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,097 | 0 RED rocket cards available
There are 1 GPUs in the system.
libDeckLinkAPI.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,097 | Decklink model name: '', version: ''
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,103 | Installed custom font: Open Sans
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,103 | Installed custom font: Open Sans
[0x7f2a7704fb40] | Main | INFO | 2018-10-13 10:25:39,117 | Finished loading Application style sheet
Local.Speed.Debug switched OFF - ''
[0x7f2a384f9700] | LeManager | INFO | 2018-10-13 10:25:39,201 | 521, 38
[0x7f2a7704fb40] | BtCommon | INFO | 2018-10-13 10:25:39,651 | Memory config: reserved=6000M pinned=4500M log=0
[0x7f2a7704fb40] | BtCommon | INFO | 2018-10-13 10:25:39,651 | Using default pooled memory manager
[0x7f2a7704fb40] | BtCommon | INFO | 2018-10-13 10:25:39,651 | Daemon DPDecoder is started 15318
[0x7f2a7704fb40] | BtCommon | INFO | 2018-10-13 10:25:39,651 | Daemon DPDecoder is started 15319
[0x7f2a7704fb40] | BtCommon | INFO | 2018-10-13 10:25:39,651 | Daemon DPDecoder is started 15320
[0x7f2a7704fb40] | BtCommon | INFO | 2018-10-13 10:25:39,651 | Daemon DPDecoder is started 15321
[0x7f2a7704fb40] | BtCommon | INFO | 2018-10-13 10:25:39,651 | Daemon DPDecoder is started 15322
[0x7f2a7704fb40] | BtCommon | INFO | 2018-10-13 10:25:39,652 | Daemon DPDecoder is started 15323
[0x7f2a7704fb40] | BtCommon | INFO | 2018-10-13 10:25:39,652 | Daemon DPDecoder is started 15324
[0x7f2a7704fb40] | BtCommon | INFO | 2018-10-13 10:25:39,653 | Daemon DPDecoder is started 15325
[0x7f2a7704fb40] | Fusion | INFO | 2018-10-13 10:25:39,754 | Fusion Build: 62778-db2208c5a44e038e360ee8076bb3e1a139e8deb9 (Sep 26 2018 10:03:09)


Some required information is missing for email crash report, the crash archive will not be updated


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

#TIME Sat Oct 13 10:25:39 2018 - Uptime 00:00:00 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v15.1.1.005 (Linux/Clang)

/opt/resolve/bin/resolve() [0x40db879]
/opt/resolve/bin/resolve() [0x40dae7c]
/usr/lib/libpthread.so.0(+0x123c0) [0x7f2a7d3b83c0]
/usr/lib/libc.so.6(+0x15c0d7) [0x7f2a7b79d0d7]
/opt/resolve/libs/Fusion/libfusionsystem.so(_ZN6Fusion8LookPack20LoadCategorySettingsEPNS_12SkinCategoryEy+0x2c) [0x7f2a34fdc3fc]
/opt/resolve/libs/Fusion/libfusionsystem.so(_ZN6Fusion8LookPack12LoadSettingsEv+0x1d) [0x7f2a34fdc2bd]
/opt/resolve/libs/Fusion/libfusionsystem.so(_ZN6Fusion8LookPack13LoadLookPacksEv+0x123) [0x7f2a34fdb453]
/opt/resolve/libs/libFusionPage.so(+0x10f13) [0x7f2a35bc3f13]
/opt/resolve/bin/resolve() [0x438f3af]
/opt/resolve/bin/resolve() [0x438f139]
/opt/resolve/bin/resolve() [0x438f50a]
/opt/resolve/bin/resolve() [0x199a49a]
/opt/resolve/bin/resolve() [0x435297b]
/opt/resolve/bin/../libs/libQt5Core.so.5(_ZNK13QMetaProperty5resetEP7QObject+0x92) [0x7f2a9307c782]
/opt/resolve/bin/resolve() [0x42ce0ec]
/opt/resolve/bin/resolve() [0x30fd24d]
/opt/resolve/bin/resolve() [0x3100526]
/opt/resolve/bin/resolve() [0x31d1723]
/opt/resolve/bin/resolve() [0x31d69f4]
/opt/resolve/bin/resolve() [0x14deab7]
/opt/resolve/bin/resolve() [0x413658a]
/opt/resolve/bin/resolve() [0x14bba4b]
/opt/resolve/bin/resolve() [0x14a4734]
/usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7f2a7b665223]
/opt/resolve/bin/resolve() [0x14a358d]
Signal Number = 11

================================
[0x7f2a7704fb40] | CrashReport | ERROR | 2018-10-13 10:25:40,037 | Compress() : Failed to add file to archive.
[ch@ch-pc ~]$ 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
log4cxx: No appender could be found for logger (Main).
log4cxx: Please initialize the log4cxx system properly.

Hi guys,
I've got DR 15.1 running on Kubuntu 18.04, with an amd FX-8120 cpu, Radeon RX480 graphics, 16gb of RAM.
So far I've tested editing and color grading and rendering; it works fine except on fusion I can apply effects but nothing comes up on the fusion viewers, even when I click on the nodes and press 1 or 2. I can only see the result in edit mode. What am I doing, or not doing, wrong?

"at first resolve 15 worked fine with /opt/resolve/bin/resolve but since yesterday starts only with sudo /opt/resolve/bin/resolve.
/opt/resolve/bin/resolve"
resolved by deleting the folder .fusion in my home

I recently also have issues with DaVinci Resolve when running optirun.

Just two weeks ago it worked fine, but now the program doesn't boot up and I get a "quit unexpectedly" message.
I tried uninstalling and re-installing Davinci Resolve, but the same issue happens.

The program works fine when using nvidia-xrun instead (in a different environment), so it seems that there are issues with the bumblebee driver all of a sudden?


I found one type of workaround, which is using; optirun sudo '/opt/resolve/bin/resolve'
Just; optirun '/opt/resolve/bin/resolve' doesn't work.
sudo optirun '/opt/resolve/bin/resolve' also doesn't work.

Can't record audio through my mic on linux.. but other software is no problem...known issue ? any work arounds ?

does anyone have resolve 15 on a laptop running linux with intel with integrated GPU on? and could report about it? which linux? which graphics driver? which GPU?

Hi Joaquim, I've got my Dell XPS15 (see siggie) to work reasonably well apart from frequent crashes in Fusion, but I've been unable to run it using the integrated Intel. There's no off-loading between the GPUs going on either as far as I can tell.

I also have a smaller XPS13 with ONLY an integrated Intel, but DR crashes immediately after the initial splash screen.

Unable to Launch on Manjaro Here is my log:

Code: Select all

[0x7fa207a33b80] | Main                 | INFO  | 2018-10-25 23:45:38,363 | Running DaVinci Resolve Studio v15.1.2.008 (Linux/Clang)
[0x7fa207a33b80] | Main                 | INFO  | 2018-10-25 23:45:38,364 | Updating display GPU information...
OpenCL error -1001, GPUPropertiesUtilUnix.cpp:338.
terminate called after throwing an instance of 'ReactorGPU::GPUException'


Some required information is missing for email crash report, the crash archive will not be updated


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

#TIME Thu Oct 25 23:45:38 2018 - Uptime 00:00:00 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v15.1.2.008 (Linux/Clang)

bin/resolve() [0x413cd19]
bin/resolve() [0x413c29b]
/usr/lib/libpthread.so.0(+0x123c0) [0x7fa20df5c3c0]
/usr/lib/libc.so.6(gsignal+0x10f) [0x7fa20c074d7f]
/usr/lib/libc.so.6(abort+0x125) [0x7fa20c05f672]
bin/resolve(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x15d) [0x5ac3d0d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7fa2256fd036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x219d7) [0x7fa2256fc9d7]
bin/resolve() [0x14f5c54]
bin/resolve() [0x14f5449]
bin/resolve() [0x14efc2a]
bin/resolve() [0x14c01fa]
bin/resolve() [0x14bd8fe]
bin/resolve() [0x14bc53c]
bin/resolve() [0x14bbe18]
bin/resolve() [0x14cef9d]
bin/resolve() [0x14b7018]
/usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7fa20c061223]
bin/resolve() [0x14b591d]
Signal Number = 6

================================
[0x7fa207a33b80] | Main                 | INFO  | 2018-10-25 23:45:38,365 | Updating display GPU information...
OpenCL error -1001, GPUPropertiesUtilUnix.cpp:338.
terminate called recursively


Some required information is missing for email crash report, the crash archive will not be updated


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

#TIME Thu Oct 25 23:45:38 2018 - Uptime 00:00:00 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v15.1.2.008 (Linux/Clang)

bin/resolve() [0x413cd19]
bin/resolve() [0x413c29b]
/usr/lib/libpthread.so.0(+0x123c0) [0x7fa20df5c3c0]
/usr/lib/libc.so.6(gsignal+0x10f) [0x7fa20c074d7f]
/usr/lib/libc.so.6(abort+0x125) [0x7fa20c05f672]
bin/resolve(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0xed) [0x5ac3c9d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7fa2256fd036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x223a1) [0x7fa2256fd3a1]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x228f7) [0x7fa2256fd8f7]
/opt/resolve/bin/../libs/libc++abi.so.1(__gxx_personality_v0+0x6c) [0x7fa2256fdddc]
/usr/lib/libgcc_s.so.1(_Unwind_RaiseException+0x14b) [0x7fa20c21220b]
/opt/resolve/bin/../libs/libc++abi.so.1(__cxa_throw+0x66) [0x7fa2256fc9c6]
bin/resolve() [0x14f5c54]
bin/resolve() [0x14f5449]
bin/resolve() [0x14efc2a]
bin/resolve() [0x14c01fa]
bin/resolve() [0x14bd8fe]
bin/resolve() [0x14bc53c]
bin/resolve() [0x14bbe18]
bin/resolve() [0x14f12dd]
bin/resolve() [0x413c897]
/usr/lib/libpthread.so.0(+0x123c0) [0x7fa20df5c3c0]
/usr/lib/libc.so.6(gsignal+0x10f) [0x7fa20c074d7f]
/usr/lib/libc.so.6(abort+0x125) [0x7fa20c05f672]
bin/resolve(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x15d) [0x5ac3d0d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7fa2256fd036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x219d7) [0x7fa2256fc9d7]
bin/resolve() [0x14f5c54]
bin/resolve() [0x14f5449]
bin/resolve() [0x14efc2a]
bin/resolve() [0x14c01fa]
bin/resolve() [0x14bd8fe]
bin/resolve() [0x14bc53c]
bin/resolve() [0x14bbe18]
bin/resolve() [0x14cef9d]
bin/resolve() [0x14b7018]
/usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7fa20c061223]
bin/resolve() [0x14b591d]
Signal Number = 6

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


I installed using the MakeResolveDeb, but it didn't work, Resolve won't open.

Anyone on Pop!_OS with a GTX 1070 that have some tips and tricks to get it to work?

One of the reasons I finally decided to switch to Linux was because I saw Resolve was available on it, I didn't realize it was for CentOS only. I would've switched to CentOS if it wasn't for the other reason I switched to Linux, Bitwig, which I believe is only supported for Ubuntu based distros

Anyone on Pop!_OS with a GTX 1070 that have some tips and tricks to get it to work?

do you have installed the proprietary nvidia drivers -- the free "nouveau" driver will not work.
and you als have to install the nvidea OpenCL packages, cuda alone will not work.

I believe the Pop installer comes with the proprietary nvidia driver. This is it, right?

Code: Select all

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.57                 Driver Version: 410.57                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1070    Off  | 00000000:01:00.0 Off |                  N/A |
| N/A   56C    P0    39W /  N/A |    630MiB /  8119MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+


How do I install the OpenCL packages? I'm pretty new to Linux

I'm having an issue where anything imported has no video. Pictures work just fine. In the video you'll see even the audio doesn't work, that only happened after I re-ran the install script.

Ubuntu 18.10 with 396 Nvidia drivers.

I can't post links, but the YouTube code showing this issue is:

bk39faH9XWo

Do lsmod | grep -i nvidia. Just checking that you're using the proprietary driver and not nouveau.

If you are using the proprietary driver than you don’t need to worry about installing CUDA or OpenCL separately, as these come with the driver blob. CUDA internally, and OpenCL as NVIDIA’s OpenCL shared object.

Cheers,
Mike

Do lsmod | grep -i nvidia. Just checking that you're using the proprietary driver and not nouveau.

because of Michaels nvidia-smi output, you can be sure, that he has already installed the correct driver...

If you are using the proprietary driver than you don’t need to worry about installing CUDA or OpenCL separately, as these come with the driver blob.

that's not true for all distributions. e.g. on debian [and Michal is at least using a very uncommon derivative of this family] the nvidia software is split into many small packages and the necessary opencl parts ('nvidia-opencl-common', 'nvidia-opencl-icd') are not automatically installed as dependency, if you just install the driver.

because of Michaels nvidia-smi output, you can be sure, that he has already installed the correct driver...

Just because the proprietary driver is installed doesn’t mean it’s active. You should still be able to run nvidia-smi and get proper output, but the system could be using the nouveau driver if it wasn’t blacklisted correctly.

that's not true for all distributions. e.g. on debian [and Michal is at least using a very uncommon derivative of this family] the nvidia software is split into many small packages and the necessary opencl parts ('nvidia-opencl-common', 'nvidia-opencl-icd') are not automatically installed as dependency, if you just install the driver.

I am aware of that. I wasn’t sure how Pop_OS delivers their driver. If they deliver it in a more monolithic base, the way to driver is intended to work, then what I said would apply. If not then it doesn’t. Although it’s a Debian derivative, the System76 team could have taken liberty to alter to driver package(s).

Cheers,
Mike

I'm able to run resolve, but it seems that any action that involves encoding results in a hard crash (segfault). For example, attempting to build proxy version of clips, or exporting anything at all.

I'll have to post proper details later (not at that machine right now), but here's a summary:

I know my way around various linuxen fairly well... a sysadmin running them at both work and home since 1998. Have been using Lightworks successfully recently, but some oddities in how it processes some things has me wanting to move to resolve. Had resolve 15 running just fine on my old i5 2500 machine, so decided to go ahead and invest a little. Ordered a BMPCC4K, and just built a threadripper 1950 machine with 64GB Ram and moved my GTX 970 to it. The new machine is solid and stable (memtest for extended periods, blender, and plenty of other tests to be sure).

Installing resolve 15.1.2 is no problem, seems to run fine. But as soon as I touch a proxy workflow or export anything... bang, it's gone. There are some errors in the logs complaining about UI level things, and something about prores (my footage is 4K prores)... I'll copy/paste here when I get a chance later.

Any insight is welcome!

What Linux distro are you using?

You know that Resolve only runs on Supermicro servers with 8 32 cores CPUs with 8 Nvidia Titan GPUs on the bloody obsolete CentOS ? (o;

No seriously....I bought DRS two months ago and still can't do any serious works...even tried installing the CentOS which no company requires anymore besides BMD and the Lattice Semiconductor which tries to sell obsolete chips to developers

I've spent a lot of time recently in using blender and how it can replace my needs...especially 3D compositing....even camera tracking is possible...well no surprise as blender and resolve use the open source opencv projekt...

But in blender you got excellent render plugins possibilities like luxcore or even better octane...


I still striggle in which new hardware to invest....but doesn't like going into Linux way as there is still a serious bug open with crashibg in Fusion tab....see here for further details: viewtopic.php?f=21&t=79680


I still don't get why you would need to buy 20k US$ of hardware just to run a free or US$299 version of a software.....in the end it is just a Qt5 software they are doing which should run equally well on all OS....and Qt5 doesn't care about obsolete distros like CentOS...it is just lame excuse to customers...

I'm able to run resolve, but it seems that any action that involves encoding results in a hard crash (segfault). For example, attempting to build proxy version of clips, or exporting anything at all.
...
just built a threadripper 1950 machine with 64GB Ram and moved my GTX 970 to it. The new machine is solid and stable (memtest for extended periods, blender, and plenty of other tests to be sure).

this could be caused by the fact, that the used AVID DNxHD/HR codecs are not compatible with most AMD processors resp. their missing CPU instruction set extensions in the linux edition of resolve.

try to use another proxy/caching/export format on this kind of machines!

Just wanted to say hi and give my perspective on running Resolve on Linux. I'm just do this stuff as a hobby so YMMV. The OS I use is Linux Mint, which I have been using for around 4 or 5 years now. Before that I was using Fedora which is just too bleeding edge for me and caused a lot of issues I just didn't want to deal with. My system currently has a I7 5820K CPU with 6 cores and 32 GBytes of memory. I have two Nvidia GPUs, a GTX 980 and a RTX 2070.

I have to say that Resolve didn't have any issues running on my system, that I can see so far. Although I don't know how to use Fusion yet so I still need to look at that. It found both of my GPUs no problem, and even saw that my displays are only on the 980. I'm using the 2070 for doing rendering with Octane, etc.

I always install the Nvidia drivers manually, and they have always worked for me. Finding this program has got me interested in video again. I even dragged out my old camcorder (Cannon Vixia HV30) and started playing around with it. Lots of fun!

Jason

Hi - sorry if this is a FAQ, I've skimmed the forum but couldn't find an answer, so here goes...

I'm trying to get Resolve 15.1.2 running on my EPYC server. I've done a fresh install of Centos 7.5.1804 , I've got 48GB of RAM and an Radeon pro 8GB WX 7100 GPU, and the AMD 18.30 GPU drivers installed.

I have installed Resolve 15.1.2 (free), and I can get as far as the what's new section, but it core dumps as soon as I try and go on to the project browser. Are there any known issues / workarounds for a similar setup?


Cheers,
Joe.

Hi - sorry if this is a FAQ, I've skimmed the forum but couldn't find an answer, so here goes...

I'm trying to get Resolve 15.1.2 running on my EPYC server. I've done a fresh install of Centos 7.5.1804 , I've got 48GB of RAM and an Radeon pro 8GB WX 7100 GPU, and the AMD 18.30 GPU drivers installed.

I have installed Resolve 15.1.2 (free), and I can get as far as the what's new section, but it core dumps as soon as I try and go on to the project browser. Are there any known issues / workarounds for a similar setup?


Cheers,
Joe.

I'm embarrassed but pleased to say that after a bit of digging, I realised that while I had installed the GPU drivers, I had not installed the OpenCL optional components. So I reinstalled the drivers with OpenCL and Resolve fires up fine

I am pleasantly surprised just how well scrubbing through 4K DCI Prores works, even though the video is on my NAS and coming off good-old spinny disks. Well done BMD!

Hi

I have to say that Resolve didn't have any issues running on my system, that I can see so far. Although I don't know how to use Fusion yet so I still need to look at that.

Well, I am using Linux Mint as well and have a lot of issues with crashing. Could you please try to drop a few of the Fusion titles from the effects library onto a clip in your timeline? Does it crash? If not - what drivers do you use?

Most of those titles (but not all) crash Resolve instantly on my system (as described in another thread in this forum).

Thanks in advance

Dieter

Well the easiest test is to add a background node inside Fusion and merge it with MediaIn1 node...
crashes instantly on Debian 9, Ubuntu 18 and CentOS 7.5....

Seems to be an issue with GPU usage inside Fusion....

Haven't heard for since 8 days now from BMD support since I opened the ticket....

I'm able to run resolve, but it seems that any action that involves encoding results in a hard crash (segfault). For example, attempting to build proxy version of clips, or exporting anything at all.
...
just built a threadripper 1950 machine with 64GB Ram and moved my GTX 970 to it. The new machine is solid and stable (memtest for extended periods, blender, and plenty of other tests to be sure).

this could be caused by the fact, that the used AVID DNxHD/HR codecs are not compatible with most AMD processors resp. their missing CPU instruction set extensions in the linux edition of resolve.

try to use another proxy/caching/export format on this kind of machines!

I can confirm this. I'm on an AMD FX8320 and was having this issue when using proxies. Changed it to Cineform and the crashes went away. Even with this problem, I'm still sticking with AMD for my CPU, but I think I'll be buying Resolve Studio in the new year.

Hi

I have to say that Resolve didn't have any issues running on my system, that I can see so far. Although I don't know how to use Fusion yet so I still need to look at that.

Well, I am using Linux Mint as well and have a lot of issues with crashing. Could you please try to drop a few of the Fusion titles from the effects library onto a clip in your timeline? Does it crash? If not - what drivers do you use?

Most of those titles (but not all) crash Resolve instantly on my system (as described in another thread in this forum).

Thanks in advance

Dieter

Yep I tried several title sequences and most worked until I tried the "Title Zipper" then it crashed on me. I'm using Nvidia's driver version 410.66.

This is all I could find in the logs:

Code: Select all

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

#TIME Thu Nov  1 08:24:52 2018 - Uptime 00:01:21 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v15.1.1.005 (Linux/Clang)

/opt/resolve/bin/resolve() [0x40db879]
/opt/resolve/bin/resolve() [0x40dae7c]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7fde06908890]
Signal Number = 11

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

Yup, Resolve runs well on Linux Mint, as long as you stay away from Fusion.

does anyone have resolve 15 on a laptop running linux with intel with integrated GPU on? and could report about it? which linux? which graphics driver? which GPU?

Hi Joaquim, I've got my Dell XPS15 (see siggie) to work reasonably well apart from frequent crashes in Fusion, but I've been unable to run it using the integrated Intel. There's no off-loading between the GPUs going on either as far as I can tell.

I also have a smaller XPS13 with ONLY an integrated Intel, but DR crashes immediately after the initial splash screen.

BMD has never confirmed or denied the matter, but we've come to think only the Mac/Win ports support integrated GPUs. Maybe 16b1 will change things. Right now, the port only talks to what it sees an AMD/Nvidia GPU.

What Linux distro are you using?

On that machine, bone stock Ubuntu 18.10, with the appropriate proprietary drivers added of course. Also tried 18.04, 18.04 + KXStudio repos, etc. I'm happiest on dpkg based distros (especially straight Debian), but could easily switch back over to RPM if I had the impression that it would make a difference. From what I've read, it doesn't sound like it would, even with the official supported CentOS. CentOS and Fedora didn't even exist the last time I touched a Red Hat derivative, so I'd just as soon skip the clumsy reacclimatization period if I can.

You know that Resolve only runs on Supermicro servers with 8 32 cores CPUs with 8 Nvidia Titan GPUs on the bloody obsolete CentOS ? (o;

And here I thought my new machine was perhaps overkill.

I did read your other thread, thank you.

this could be caused by the fact, that the used AVID DNxHD/HR codecs are not compatible with most AMD processors resp. their missing CPU instruction set extensions in the linux edition of resolve.

try to use another proxy/caching/export format on this kind of machines!

That's pretty interesting, had no idea about that, sounds like I have a bit of reading to do on the topic, thank you.

I have no particular attachment to the AVID codecs, those are just what came up as defaults (perhaps preferred?). Without prores in the offered list I saw no reason to not give them a go.

"Not compatible with AMD" makes for a very compelling reason! Odd that it isn't detected and not offered as an option. It could at least fail a little more gracefully than *kaput*.

I can confirm this. I'm on an AMD FX8320 and was having this issue when using proxies. Changed it to Cineform and the crashes went away. Even with this problem, I'm still sticking with AMD for my CPU, but I think I'll be buying Resolve Studio in the new year.

Thank you!

Safe to assume that means you'd recommend Cineform as the best of the remaining options for general use? It appears to be supported (to some extent at least) by ffmpeg, which is very important to me. (I'm fond of pulling all kinds of silly stunts with raw ffmpeg.)

I'll give it a try tonight if I get the opportunity.

Yep I tried several title sequences and most worked until I tried the "Title Zipper" then it crashed on me. I'm using Nvidia's driver version 410.66.

This is all I could find in the logs:

Code: Select all

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

#TIME Thu Nov  1 08:24:52 2018 - Uptime 00:01:21 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v15.1.1.005 (Linux/Clang)

/opt/resolve/bin/resolve() [0x40db879]
/opt/resolve/bin/resolve() [0x40dae7c]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7fde06908890]
Signal Number = 11

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

When you run with the GNU debugger...what do you see when it crashes?
Especially when doing a backtrace command inside GDB?

So I tried using a non DNxHD / DNxHR codec last night (used Cineform) when doing a test export.

Big thanks to Martin Schitter and SteveMulcahy, I can now also confirm the cause was lack of stable AVID codec support in Resolve on Linux, when using an AMD CPU. Exporting with Cineform instead, it blasted right through my roughly 3 minute music video very quickly (didn't time it, probably well under 30 seconds) with zero problems. Whereas with the Avid codecs it always crashed, without outputting even a single frame (leaving behind a 0 byte file).

Let's make this nice, big and bold for search crawlers to pick up:
DAVINCI RESOLVE + LINUX + AMD + DNxHD = ALWAYS CRASH
DAVINCI RESOLVE + LINUX + AMD + DNxHR = ALWAYS CRASH



I also found all of these threads of folks running into the exact same problem:

DNxHD doesn't like AMD Threadripper
[Solved] Supported Linux codecs
DNxHR codec not working on CentOS
crash with Generating Optimized Media and DNxHR
DNxHD Crash Linux Mint/Ubuntu
[Known] Resolve 15b5 Linux crash on render in DNxHD


I just checked the Linux Installation Instructions for DaVinci Resolve 15.1.2... there is no mention of this problem in the Pre-Installation Notes, where other known compatibility issues are noted. It probably should be. (I would have seen it and saved many hours had it been there; of course I read it before installing.)

There also isn't a link or reference to any important documentation like the Manual, Configuration Guide, Feature Comparison, or Supported Formats and Codecs in there. Or even on the main DaVinci Resolve web page, for that matter... one has to go digging in the support section to find them, or to even discover that such things exist.

But even if one does read those, there is no mention of this known problem in any of those documents either. The Configuration Guide has both AMD Ryzen Threadripper and Linux sections... no mention of a problem with the AVID codecs in either. The feature comparison is where one discovers lack of any H.264 support in the free Linux version, but nothing about AVID codecs on AMD. The Supported Codec List will tell you all kinds of interesting and notable limitations (can't encode anything into MP4, or into any format with ProRes codecs without the megabucks panel dongle, and so on). But despite a zillion entries for the AVID codecs, not a peep about none of them working in Linux with an AMD CPU, not even with a footnote.

That's kinda crazy. It'd take what... 20-30 minutes tops to add that info to those docs, and to link to those docs from reasonably prominent places? Or at least from the install documentation?

Here's my current wish/suggestion list for Blackmagic:

Fix #1: On the DaVinci Resolve Page, at the very bottom, right below the download links for the free & Studio versions... put links to the manual, feature comparison, supported codec, and configuration guides right there. Or a single link like one of these:
More Info
Documentation
Manuals, Guides and Support

Fix #2: Put the same link(s) in the Installation Instructions (for all platforms)

Fix #3: In the Linux Installation Instructions, state "Currently AVID codecs (DNxHD, DNxHR) are not supported in Linux when run on systems with AMD CPUs" in the Pre-installation Notes section. Would be nice to mention it in the other support docs too, but at least put it here.

Fix #4: When actually run on a Linux system, and an AMD CPU is detected... disable those codecs, or at least default to something else. At the very very least, consider mentioning it in the logs when it causes a crash, lol.

Fix #5: How bout fixing it so it works, and doesn't crash in the first place? Of course that's more time and work... note that I put it last. That's somewhat reasonable, eh? There are clearly more demanding things I could ask for, such as proper installers for widely used modern distributions (it can be done, like this). But no... I can get by with Daniel Tufvesson's script for now. Just please tell me what's broken before I waste hours/days on it, and promise to eventually get around to fixing it. That will do!

Well, that and hurry up and get my camera built and shipped to the vendor I preordered it from. So I can start using it (and my copy of DaVinci Resolve Studio) already!

And hurry up and get Blackmagic RAW on it too, while you're at it.

OK, I'll stop there.

Nice thoughts

Let me put some more thoughrs on it working with DRS since two months on Linux, or bettersay, try to bypass the bugs...

First of all BMD makes it clear...only CentOS is supported...or better yet...only their selfmade CentOS ISO which can't be use for USB sticks...

I tried their latest DVD ISO and I could run DRS...but as soon you install all the system updates it renders the OS unusable....only power button helps (reset button won't do).

Running DRS after installing official CentOS works even after system updates..so dunno how BMD messed up their ISO, but they did...


And final statement...

I am only aware of one company that supplies their software as RPM only, but Lattice Semiconductor is an obsolete company selling even more obsolete FPGA chips...and they care nothing about current linux users...their counterparts like Xilinx and Intel support all major Linux distros....their software installs and runs out of the box....and their main business is also to sell hardware...

So BMD developers.....get your software ready for the 21st century....can't be that hard as Qt5 IDE makes it easy to develop for all Linux distros....all others can....and younprooved with MediaExpress that you can do Debian packages aswell....

I wonder why BMD doesn't just sell Resolve appliances....20000$ for Resolve and 20299$ for Resolve Studio...

I tried their latest DVD ISO and I could run DRS...but as soon you install all the system updates it renders the OS unusable....only power button helps (reset button won't do).

FWIW, I was going to download and try this ISO to see if it would solve my crashing problem. I knew that it existed, simply because it was referred to quite often in this forum.

But I couldn't find it anywhere. So much for that?

I wonder why BMD doesn't just sell Resolve appliances....20000$ for Resolve and 20299$ for Resolve Studio...

I wouldn't go quite that far. I mean, I do have it working, and it wasn't that hard thanks to the MakeResolveDeb script. (They should give him a commission for every full Studio copy installed that way!) My main problem was time wasted grappling with an known issue that could easily be avoided if it were only noted in the documentation.

Then again, I haven't gone digging around in Fusion yet, either. But I might not need to do much there, personally. As long as it holds up well for "nested" multicamera editing workflows (using both raw clips and prepared "edits" as available camera angles), with a bit of basic color correction/tweaking, and can handle lots of HD (and greater) crops from 4K footage without butchering the eventual output (hello major Lightworks processing flaw)... I'm good.

Well their latest ISO is referenced in the install PDF document when you download the zip file...

Makeresolveddb is really a great tool....but....can you do me a favour?

Add a solid color clip, convert to compound clip, open in fusion and just add a background node so it merges with MediaIn1 node? Should crash instantly on Debian, Ubuntu, official Centos...

When you run with the GNU debugger...what do you see when it crashes?
Especially when doing a backtrace command inside GDB?

This is not possible as BM would have to compile the program with the embedded symbols. Not only does this add the source code to the program (something I'm sure they wouldn't do) it also blows up the size of the executable, and in general slows the application down. I'm guessing that they are still ironing out issues withe Fusion and Linux, especially with them embedding it in Resolve. As a programmer myself I know how difficult this can be and the amount of work it takes

It would be interesting to make a list of the title sequences that cause Resolve to crash, there might be a common thread between them and this will make it easier to find the issue.

The ones that crash on my system are as follows:
Title Zipper
Title Two Line Twist Reveal
Title Text Ripple
Title Square Line Tilting Text
Title Slide From Center Line
Title Rise Fade
Title Horizontal Slide
Title Horizontal Line Reveal
Title Draw On Corners 2 Line
Title Draw On Corners 1 Line
Title Center Reveal
Lower 3rd Simple Vertical 2 Lines
Lower 3rd Simple Vertical 1 Line
Lower 3rd Simple Underline
Lower 3rd Simple Line - crashed when using play in the timeline preview
Lower 3rd Simple Box Thin 1 Line - crashed when using play in the timeline preview
Lower 3rd Simple Box 2 Line - crashed when using play in the timeline preview
Lower 3rd Simple Box 1 Line - crashed when using play in the timeline preview
Lower 3rd Draw On Two Line
Lower 3rd Corporate Corners 2 Lines - crashed when using play in the timeline preview
Lower 3rd Corporate Corners 1 Line
3D Title Reflective Type - crashed when using play in the timeline preview
3D Title Motion Background
3D Title Cinematic Type
3D Title 3rd Plane Behind Slide In - crashed when using play in the timeline preview

They all crashed just by placing them in the timeline, except those that I marked for crashing when i tried to play the timeline.

Jason

Add a solid color clip, convert to compound clip, open in fusion and just add a background node so it merges with MediaIn1 node? Should crash instantly on Debian, Ubuntu, official Centos...

Yes, crashes immediately. But I'm used to it, doesn't surprise me anymore. I can only hope the next update addresses this issues with silent crashing.

Well this crash exists since I am using the official 15.0 version I bought...

So far I came to the conclusion it has probably to do with libGL/libGLU versions...as those differ sometimes how you install the Nvidia drivers...like:

Code: Select all

/opt/resolve/libs/Fusion/libfusionsystem.so:
   libGLU.so.1 => /lib64/libGLU.so.1 (0x00007fa82f2b2000)
   libGL.so.1 => /lib64/libGL.so.1 (0x00007fa82f00e000)


Code: Select all

Fusion/libfusionsystem.so:
   libGLU.so.1 => /lib64/libGLU.so.1 (0x00007f65adb6f000)
   libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x00007f65ad8c6000)


The GDB backtrace has been sent to a developer according to the last reply from BMD support....
and the bug is definitively inside Fusion code...or how it picks up the libraries...

Though I am sure nothing will happen as they never can replicate such error as they are fixed on the system they are always using (o;

Hello all.. I dont know if this has been covered already but here goes.

I recently did a 12 hour shoot of an outdoor concert. I did all of the editing on windows. but then i was asked to do a short promo to send out to vendors for next year.

I installed the latest on an ubuntu machine. 8 core intel with a 1080ti all went well all worked fine.
but when i tried to export the video which was simple. 8 video clips with fades and 5 text overlays. no audio processing other than levels and a little eq. The mp4 Rendered with no audio at all. So i did some playing around. If i only used one video clip it would render fine. But with multiples it would not. video but no audio. So after pulling my hair out for a day. (project already finished under windows and delivered) i finally found that if i switch the bit depth to 24 instead of 16 everything worked just fine. also if i exported to a mov using dnxhd or dnxhr it didnt matter what bit depth i used.

I am using the free version. if that matters. Just thought i would post here in case this can help anyone else.
If there are any devs in the group I know that ubuntu is not supported but i had the same results in centos. If i can be of any help i am willing. My normal day job is contract data center consultant/engineer.

I've got these crashes too, but only when I have CUDA enabled. If I switch to OpenCl it doesn't crash, but that introduces other problems for me. You can also disable GPU acceleration for the specific nodes in Fusion and it should work, at least it does for me. Its not ideal but at least it works.

What OS and driver version are you using?

Would be nice if users here would update their signatures (o;

Oh yeah I forgot Right now I'm running Resolve Studio 15.1.2 on Elementary OS Juno (based on Ubuntu 18.04), but I have tried several Ubuntu based distros and it seems to be the same everywhere. I have a Nvidia Geforce 1070 8GB GPU, latest stable Nvidia driver (396 if I remember correct, I'm not in front of my workstation right now), 32GB of RAM and a six core Intel i7 (don't remember the exact model).

Everything else seems to be reasonable stable on my setup, its just Fusion that crashes when I use GPU accelerated effects.

Well I was able to replicate the exact same crash on a fresh CentOS 7 with obsolete 3.10 kernel

Still no feedback from BMD developers on my ticket....

We just need to put more pressure on this materr....and hey...they were able to release DesktopVideo as Debian package...

When I start DaVinci Resolve I get start icon but that's all.
DaVinci Resolve 15.1.2
Kubuntu 16.04 (all updates installed) Plasma Ver: 5.8.9 Qt ver: 5.6.1 Kernel Ver: 4.15.0-39-generic
Hardware is old. Intel Core 2 Duo CPU E6550 @ 2.33GHz Ram: 6.8 Gib Video: Intel 82Q35 Express

I've looked in /opt/resolve/logs and they are empty.

Please help & Thanks

Yes I really hope that they open up for supporting other distros than just CentOS. I guess it might be a good sign that they finally added support for native audio

By the way, has anyone gotten audio recording to work on the Linux version? I can't find my Steinberg UR22 on the patch panel, I just got a bunch of ALSA channels that does nothing... Is it not supported on Linux yet or am I missing something?