
- Posts: 222
- Joined: Thu Sep 28, 2017 11:39 pm
theenngee wrote:I hope I annoy noone if this issue has already been resolved in this thread, the thread is very long and I only skimmed the first few pages
theenngee wrote:I can run it and import files, but video files aren't being replayed. they show a timecode counting up, but nothing nothing else. Images work, Audiophiles show the waveform but don't play any sound.
Sulo Kokki wrote:Yup. Dwayne or Peter @BMD, could we please get a subsection for Linux? The topic is a bit too wide to be enclosed in one big thread. As you can see, because of this new users keep asking the same questions all over again.
theenngee wrote:The Linux version is really picky with import formats. The Lite version supports Apple and Avid video codecs (Prores, DNXHD/R), the Studio version includes h.264/5.
Sound output is currently only via a BMD expansion card (Decklink, Intensity) or breakout box (Ultrastudio, via Thunderbolt). Supported audio formats include WAV and AIFF.
Martin Schitter wrote:many of the reported issues here in this board are easily fixable for developers with minimal efforts.
Martin Schitter wrote:i still have to conclude: "don't try it, it 's simply unusable on this platform! -- if you really want to utilize resolve on linux workstations, you still have to utilize complicated virtual machine setups and the windows version,
Martin Schitter wrote:as long as none of the BMD developers is listening or they still deny to include all the necessary fixes in the upstream product,
root@kali:/opt/resolve/bin# ./resolve
./resolve: error while loading shared libraries: libssl.so.10: cannot open shared object file: No such file or directory
Peter Chamberlain wrote:Guys, I can see opportunity for us to improve, but please, don't try to suggest the Linux config we recommend is unusable, after all, well more than 50% of Hollywood films and a much higher percentage of TV programs use that exact config every day.
Peter Chamberlain wrote:I get that's not what you want to hear. You would like your disti to work better, or work at all. We have a working Linux config, we don't promote it other than in our recommended config. We offer it at no cost to you.
Peter Chamberlain wrote:We will get to some requests post NAB, there are even some items sooner,
Peter Chamberlain wrote:but for now, thanks for those who help others with the items they can.
We're grateful, even when we don't sound like it. I use the free Windows version, when I saw there would be a free Linux version I was really hoping to use that because I want to ditch Microsoft. So I start looking into it and you only support this particular distro version, okay... but then I had to dig quite a bit more to realize that oh, it doesn't support these codecs.... oh, it doesn't support normal system sound.... and then there's real platform-specific bugs all mixed in with people who clearly are trying to do something unsupported or hasn't read the documentation. I'm not saying you should solve everything or well that'd be nice too, but it took a lot of digging to understand what I'd actually get and what's possible.Peter Chamberlain wrote:We have a working Linux config, we don't promote it other than in our recommended config. We offer it at no cost to you.
Dwaine Maggart wrote:Resolve Disk databases do not support shared system access. Using it this way will likely lead to issues.
Only PostgreSQL databases support shared access.
Martin Schitter wrote:Dwaine Maggart wrote:Resolve Disk databases do not support shared system access. Using it this way will likely lead to issues.
Only PostgreSQL databases support shared access.
you are right! -- but i think, this proposal was more related to typical dual-boot setups, where you will never access the same disk from more than one OS at the same time.
Martin Schitter wrote:i think, if you really want to escape OS barriers, you better use virtual machines.
you'll need an addition graphic card in your machine ... that can be pass trough straight to the virtual instance
... i only have to use this kind of virtual windwos setup to make better use of davinci resolve and mistika insight frequently, everything else i usually do on linux.
Sulo Kokki wrote:You are both right. It's a dualboot solution, which I forgot to specify. Thanks for that
Sulo Kokki wrote:It's basically different means to the same end, only it roots the user to Linux, in which the Win Resolve is brought up in a sandbox.
Sulo Kokki wrote:It's certainly a more elegant way to do it, but it does stipulate another GPU. Our hack is more quick and dirty in comparison, but it gets the job done with only one. We'd probably go for the virtualization if it would be possible in terms of GPUs in our current config
Sulo Kokki wrote:One reason to bother with the Linux Resolve is because, on equal terms, it feels faster; read-write speed, response time, even the cursor.
Sulo Kokki wrote:Your suggested solution for virtualization on the same local machine, with 2xGPU, is even better, if applicable. It definitely wins over dualboot, as the environment would be all-Linux. Yet, I agree with you, both are workarounds instead of a solution.
Oh yes, and that's a big reason why we kept going - the dream of having a software of Resolve's caliber running natively on Linux. The community here has been invaluable in finding enough solutions for a specific working config. It comes with caveats, but if you accept the end-user workarounds - it works.Martin Schitter wrote:actual linux users [beyond the bounds of hollywood] may feel, when they see, how close we have already come to an excellent solution for video postprocessing on this system, but still doesn't get those few desperately need refinements, which would let a dream become finally true.
BMD looks like a company that does requests only when there's enough noise. While it is counterproductive to cry like a baby over this and that with the Linux port, the bottom line seems right. I think we need to tell them, in very clear ways, what is needed, why, and how we (using our collective knowledge on Linux) would solve the issues. And repeat. They do follow this thread with interest.Martin Schitter wrote:i know, this kind of unduly criticism is hard to accept for responsible decision makers, because it's indeed always compromising the prestigious main product to some degree.
Yes, it's a bit odd. But Resolve has an unusual development history. The Linux port may still have a lot of DavSys code in it, as opposed to the other ports, built from scratch by BMD. A key thing seems to be the distro. BMD switched the Linux config from RHEL to CentOS at the turn of the decade, and left it that way.Martin Schitter wrote:Sulo Kokki wrote:One reason to bother with the Linux Resolve is because, on equal terms, it feels faster; read-write speed, response time, even the cursor.
that's an intresting observation -- and actually you are not the only one, mentioning this difference! it's somehow a strange discovery, because linux per se isn't the most optimal choice for interactive work and minimal latencies.
Debian in general seems like a very good choice to run Resolve with. It circumvents most of CentOS' inherent update/compatibility issues and is just plain fast.Vassilis Kontodimas wrote:The reason I'm indeed trying Ubuntu Studio is that my SSD now reads 423MB/sec, which is more than double than it did on my CentOS. Not to mention that my AMD GPU works as -ahem- intended (for the most part, but much better than CentOS).
Yes, equality is what we want! Currently, we're far from it.Martin Schitter wrote:better native linux support -- something, which really works in a satisfaying and equal manner, like on the other operating systems!
It also says something about Resolve, how it already can be scaled and re-jigged to configs completely different from the AP/Supermicro solution. BMD would do well to endorse this modding further (or at least, allow these little side-doors to remain unlocked for the community).Martin Schitter wrote:it's quite surprising, how often this kind of flexibility, asked by common desktop users, may at the end become congruent to advanced needs appearing in the high end sphere.
Truly. CentOS this and pro that. Pish. The AP users are a different breed with their turnkey systems, but some stand-alone users parroting the company line of "official working config" have been proven, in this thread, to talk through their hats. People, BMD are basing their arguments on their SuperMicro setup, anyway.Martin Schitter wrote:anybody, who wants to make use of resolve in a manner, which isn't strictly oriented around this one and only decklink output device [and you could also replace it with: "CentOS resolve for linux installer"], has to be treated as an unworthy idiot in principle.
Yup. The Prores implementation is a good example. BMD originally forewent it with the Linux, as it was not their idea of a "pro feature". It was added only after the AP users came up and said they need it, repeatedly.Martin Schitter wrote:if software gets improved and becomes more open and versatile, it's usually not to the detriment of those few experts and high end customers, which didn't have reason to miss or claim the relevant features from their specific point of view sooner. but at the end it's more often than not opening new practical possibility to all of us.
Sulo Kokki wrote:Martin Schitter wrote:anybody, who wants to make use of resolve in a manner, which isn't strictly oriented around this one and only decklink output device [and you could also replace it with: "CentOS resolve for linux installer"], has to be treated as an unworthy idiot in principle.
Truly. CentOS this and pro that. Pish. The AP users are a different breed with their turnkey systems, but some stand-alone users parroting the company line of "official working config" have been proven, in this thread, to talk through their hats. People, BMD are basing their arguments on their SuperMicro setup, anyway.
Arun Gurung wrote:Sulo Kokki wrote:
Can't blame BlackMagic Design, the problem must be due to licensing and marketing issues because BMD support have been professional. The obstacles come from criminal programmers who pose as engineers, e.g. Anonymous hacker group https://www.facebook.com/bluekitteh13.
...criminal programmers...John Morris wrote:Please don't put the Linux community into disrepute.
# yum downgrade kernel-tools-libs kernel-modules kernel-devel kernel
# ./amdgpu-install --opencl=rocm
# yum install libopencl-amdgpu-pro-icd
$ clinfo | head -6
Number of platforms 1
Platform Name AMD Accelerated Parallel Processing
Platform Vendor Advanced Micro Devices, Inc.
Platform Version OpenCL 2.1 AMD-APP (2527.3)
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd cl_amd_event_callback cl_amd_offline_devices
$ glxinfo | grep -A5 "Extended renderer info"
Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org (0x1002)
Device: Radeon RX 570 Series (AMD POLARIS10 / DRM 3.20.0 / 4.13.9-300.fc27.x86_64, LLVM 5.0.1) (0x67df)
Version: 17.2.4
Accelerated: yes
Video memory: 7325MB
$ ffmpeg -i DSCF7003.MOV -acodec copy -vcodec prores -profile:v 0 -f mov filename.mov
linuxfreak wrote:First, slightly off-topic, I want to reply to rants about BMD "having to" support $whatever_distribution and $whatever_sound_hardware: One of the basic principles behind free software is that one creates something for his own need and shares it so that others can also profit. While DaVinci "Lite" is "only" free in beer and not in speech, that part well applies.
linuxfreak wrote:For the typical use case, a decklink or something similar is installed anyway...
...
Due to lack of a decklink card I could not test audio yet,...
Martin Schitter wrote:linuxfreak wrote:For the typical use case, a decklink or something similar is installed anyway...
...
Due to lack of a decklink card I could not test audio yet,...
so much about "reality" and the practical impact of resolves actual limitations on this platform
(...and if you got your decklink card and dig deeper, you'll find a lot more of them...)
in case of free software, [...]
Got that right. However...linuxfreak wrote:BMD did not release it as open source, and you're not forced to use it.
linuxfreak wrote:This won't be a dedicated workstation and I'm just doing some hobbyist NLE. As I'm hence not running on a supported platform, I wanted to verify if it even runs properly before I do spend money on a decklink.
linuxfreak wrote:in case of free software, [...]
You don't need to sell me on free (as in speech) software, I do work for a fairly big open source company. But BMD did not release it as open source, and you're not forced to use it.
Don't get me wrong, I'd also prefer if it would support h.264 in the free version, plus audio via common linux audio infrastructure. But I do understand why this is not on top of BMD's prio list, hence it's bit of "take it or leave it" for the free beer version, right?
main@localhost:~/veriumMiner-main7.3> cat /opt/resolve/logs/ResolveDebug.txt | grep GL
libGL: Can't open configuration file /home/main/.drirc: Datei oder Verzeichnis nicht gefunden.
libGL: pci id for fd 10: 1002:679a, driver radeonsi
libGL: OpenDriver: trying /usr/lib64/dri/tls/radeonsi_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/radeonsi_dri.so
libGL: dlopen /usr/lib64/dri/radeonsi_dri.so failed (/usr/lib64/dri/radeonsi_dri.so: undefined symbol: amdgpu_cs_syncobj_import_sync_file)
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL: pci id for fd 10: 1002:679a, driver radeonsi
libGL: OpenDriver: trying /usr/lib64/dri/tls/radeonsi_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/radeonsi_dri.so
libGL: dlopen /usr/lib64/dri/radeonsi_dri.so failed (/usr/lib64/dri/radeonsi_dri.so: undefined symbol: amdgpu_cs_syncobj_import_sync_file)
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL: OpenDriver: trying /usr/lib64/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/swrast_dri.so
libGL: dlopen /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: undefined symbol: amdgpu_cs_syncobj_import_sync_file)
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
Unrecognized OpenGL version
Unrecognized OpenGL version
[0x7f674882bc00] | UI | INFO | 2018-03-26 16:25:47,746 | Not creating special GL widget for screen 0
libGL: Can't open configuration file /home/main/.drirc: Datei oder Verzeichnis nicht gefunden.
libGL: pci id for fd 9: 1002:679a, driver radeonsi
libGL: OpenDriver: trying /usr/lib64/dri/tls/radeonsi_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/radeonsi_dri.so
libGL: Can't open configuration file /home/main/.drirc: Datei oder Verzeichnis nicht gefunden.
libGL: Can't open configuration file /home/main/.drirc: Datei oder Verzeichnis nicht gefunden.
libGL: Using DRI3 for screen 0
Unrecognized OpenGL version
Unrecognized OpenGL version
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
Unrecognized OpenGL version
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
QOpenGLFunctions created with non-current context
/opt/resolve/bin/../libs/libQt5Gui.so.5(_ZN21QPlatformBackingStore15composeAndFlushEP7QWindowRK7QRegionRK6QPointP20QPlatformTextureListP14QOpenGLContextb+0x11b)[0x7f6745b9938b]
/opt/resolve/bin/../libs/libQt5Gui.so.5(_ZN21QPlatformBackingStore15composeAndFlushEP7QWindowRK7QRegionRK6QPointP20QPlatformTextureListP14QOpenGLContextb+0x11b)[0x7f6745b9938b]
jackson1 wrote:I can install OpenGL provided by the amdgpu-pro driver this will let resolve start but it's instantly crashing the whole os because the pro driver isn't installed.
jackson1 wrote:The amdgpu-pro driver is basically useless since kernel 4.10.x (i'm on 4.15.x)
jackson1 wrote:Seems like some people here got the amdgpu-pro opencl part working too and are ending up with similar issues.
jackson1 wrote:As soon as i use the OpenGL part from the amdgpu-pro driver davinci resolve starts (although the driver isn't working). I've done some research and found out that some programs have issues recognizing the OpenGL version if mesa is being used (just because of the mentioned version output) which would explain the error log.
jackson1 wrote:I think i'll just switch to a used nvidia 980ti when the new nvidia generation is being released, i'm sick of multi gpu issues too.
Arun Gurung wrote:I get this with DaVinci Resolve 14.3, hope somebody can assist. Linux 4.11 on CentOS 7.
[arun-g@macbook-air ~]$ /opt/resolve/bin/resolve
ActCCMessage Already in Table: Code= 2282, Mode= 0, Level= 0, CmdKey= 8, Option= 0
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
14.3 (#014)
Main thread starts: 60808B40
[0x7fd460808b40] | Undefined | INFO | 2018-03-11 10:50:11,141 | --------------------------------------------------------------------------------
[0x7fd460808b40] | Undefined | INFO | 2018-03-11 10:50:11,142 | Loaded log config from /opt/resolve/configs/log-conf.xml
[0x7fd460808b40] | Undefined | INFO | 2018-03-11 10:50:11,142 | --------------------------------------------------------------------------------
jackson1 wrote:I can install OpenGL provided by the amdgpu-pro driver this will let resolve start but it's instantly crashing the whole os because the pro driver isn't installed. I think this is only happening because the Mesa opengl version is called "4.5 (Mesa 18.0.0-rc4)" instead of just the OpenGL version number.
Unrecognized OpenGL version
QOpenGLWidget: Failed to make context current
QOpenGLFunctions created with non-current context
Looks promising!Sulo Kokki wrote:General improvements
* Support for native audio on Linux
You go, BMD.
I'm on it SuloSulo Kokki wrote:Here's hoping you'll have the motivation to update makeresolvedeb
`sudo dpkg -i cuda-repo-ubuntu1704_9.1.85-1_amd64.deb`
`sudo apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1704/x86_64/7fa2af80.pub`
`sudo apt-get update`
Users browsing this forum: David E King, Google Feedfetcher, Kenzo, Rick van den Berg and 105 guests