Hakim Craddock wrote:That sounds awesome. Do you know of any GUi's i can install for Manjaro to use ffmpeg?

I don't know about Manjaro, but you could try QWinFF, WinFF, Handbrake or FFmpegYAG to name a few. But you might be able to use a Google search. Or you use a script for Nautilus/Nemo - I use the latter because my DE is Cinnamon.

Hakim Craddock wrote:That sounds awesome. Do you know of any GUi's i can install for Manjaro to use ffmpeg?

I don't know about Manjaro, but you could try QWinFF, WinFF, Handbrake or FFmpegYAG to name a few. But you might be able to use a Google search. Or you use a script for Nautilus/Nemo - I use the latter because my DE is Cinnamon.

Hakim Craddock wrote:but honestly. I am not wasting anymore time on it until the microphone issue is resolved.

I don't think that using ffmpeg is a waste of time. Please use the search engine of your choice to find more information about ffmpeg and Prores. And as I said before - using a terminal or bash script is the easiest and quickest way of achieving your goal.

Hakim Craddock wrote:That sounds awesome. Do you know of any GUi's i can install for Manjaro to use ffmpeg?

I don't know about Manjaro, but you could try QWinFF, WinFF, Handbrake or FFmpegYAG to name a few. But you might be able to use a Google search. Or you use a script for Nautilus/Nemo - I use the latter because my DE is Cinnamon.

Thank you. i tried handbrake, didnt see a prores option in it.

That is largely the issue with GUIs and why CLI will always generally beat them. A GUI won't always include every format that FFMPEG is capable of. While it's very easy to transcode with a simple command, unless the GUI makes the time to include every format, you'll only have access to a fraction of the codecs available.

As others have said, they will go all the way to creating bash scripts and creating links in their film browsers' kicker menu. I don't do anything that fancy. I keep a text document of all possible commands so I can cut and paste as needed.

So for example, if I want to convert all of my mp4s in a folder to prores I can simply open that folder in the terminal and paste:

This is what I'm trying to do, build a collection of ffmpeg instruction lines for my needs while learning to understand codecs/formats and ffmpeg. One conversion I'm not getting quite right is mxf XAVC L to mp4. This may sound odd, but what I want to do is basic editing on a Samsung S4 tablet. I spend a lot of time camping in our national parks where laptops are not always practical. The more serious stuff is done when I get home.

My xavc l to mp4 conversions will play in some media players but Kinemaster, the app I'm using will not read them. Any help with the ffmpeg instructions would be a great help.

But as I said, I'm just guessing here based on a few minutes of research. To be honest, if it was ME, I'd see if the Sony Camera allows you to film to a less-proprietary format on those times when you know you are going to be editing on your tablet.

deezid wrote:I would like that and maybe some kind of simple tutorial how to embed these ffmpeg scripts into Nautilus.Will try to fiugure out how to create watchfolders as well, might become handy

I'd like to do that but first BMD has to sort this thread - it's now 28 pages with all possible topics. Maybe a forum part for Linux in general and helper scripts in particular would be extremley helpful.

Dieter Scheel wrote:I'd like to do that but first BMD has to sort this thread - it's now 28 pages with all possible topics. Maybe a forum part for Linux in general and helper scripts in particular would be extremley helpful.

Believe me, we've asked for that over 10 pages ago. All we got is unstick topic.

Oh, well. It seems there's a need for a user-maintained discussion forum centering on Davinci Resolve. Different sections for different OS', etc (also Fusion & Fairlight). I encourage everyone interested to come up with viable solutions, as BMD wants to run this forum on a certain way and that's alright. But it also looks like Resolve users need to solve this issue own their own.

Augh, I wrote a very lengthy piece here and when I tried to submit it, I was logged out! Perhaps it was a good thing though...

To sum my thoughts:- BMD seems to be primarily a hardware company- Big money is not in the Advanced panels but in Pocket 4K cameras (and software is used to sell cameras)- DaVinci Resolve is no longer a turn key solution, hasn't been for a long time!- There are more and more people leaving MacOS ("Modular" Mac Pro, Mojave and NVIDIA, need I say more!) and Windows (Telemetry, forced updates, MS-DOS filesystem layout C: D: E: ...) to become Linux users-----> it makes sense to treat all Linux users like good, potential customers -- Linux doesn't need to be a "turn key island" compared to other platforms (and TBH, the fact that R15 has the support for system sound tells me that they don't intend that either, as otherwise bringing this feature wouldn't have made sense!)

The way Resolve is packaged on Linux should be addressed ASAP. It's a nightmare even for professional environments installed from the official BMD ISO. It shouldn't be necessary to reinstall the whole operating system if something breaks. It should be possible to keep system up to date (Just imagine if BMD told all Mac users to keep using Snow Leopard 10.6.3 from release to release ).

BMD, hear us: If CentOS is too difficult target, move to Ubuntu (/Debian). It's very stable, extremely popular distribution. I think it is the most supported Linux distribution if we use as a metric the variety of proprietary, commercial consumer software available for it (for example, gaming platform Steam). After having used Ubuntu 16.04/18.04 for many years using CentOS 7.3 was like being thrown back to the early 2000s...

Paul, thanks for the links. The info there has added a bit more to my knowledge. ffmpeg is fascinating software, lots to learn there!If I can contribute anything to a list of useful examples I will, but I'm very much a beginner.

Hakim Craddock wrote:seems this thread is being hidden from the main DR forum. I have to search to find it.

No it's not. Found it on the first page, about 10 topics down (8 if you don't count the pinned topics).

It was pinned before. Now it's not.@Hakim Craddock:Hoping they'll fix (USB-) audio input. Had to go back to V15.2.2 because there's another dealbraker in later versions: Alpha channel messed up when using RCM or ACES.

Wasn't really able to continue working on my feature film before switching back to 15.2.2

One fails, but doesn't matter opencl goes through and Davinci Resolve runs just fine. Note, I copied these specific rpms and relocated into a separate folder and dnf installed all of them together. It failed in the past when I didn't do that method.I did the same process again with a 2700 and rx 570, but Davinci Resolve still can't find OpenCl, also on this build Desktop Video/Media Express can't detect two captures cards I have installed on the build.I'm shocked the process didn't work again. I'm wondering if it's because it's polaris vs vegaI did make a mistake that I'm not sure matters. I installed the same rpms I did for Vega 56 from the amd 18.50 drivers for centos. I retried with the rx 570 drivers and Davinci Resolve still didn't see the Opencl capable gpu.

I really don't think this matters though, from what I can tell the driver is the same linux driver, even Centos and RHEL appear to have the same gpu drivers. I've noticed it's the same with Nvidia. In fact Nvidia seems to just release one propriety gpu driver that works with all they're cards or at least is supposed to work.

Any info would be appreciated, ultimately I just want to see BMD support open source mesa drivers, that is the new standard for amd on linux.

One fails, but doesn't matter opencl goes through and Davinci Resolve runs just fine. Note, I copied these specific rpms and relocated into a separate folder and dnf installed all of them together. It failed in the past when I didn't do that method.I did the same process again with a 2700 and rx 570, but Davinci Resolve still can't find OpenCl, also on this build Desktop Video/Media Express can't detect two captures cards I have installed on the build.I'm shocked the process didn't work again. I'm wondering if it's because it's polaris vs vegaI did make a mistake that I'm not sure matters. I installed the same rpms I did for Vega 56 from the amd 18.50 drivers for centos. I retried with the rx 570 drivers and Davinci Resolve still didn't see the Opencl capable gpu.

I really don't think this matters though, from what I can tell the driver is the same linux driver, even Centos and RHEL appear to have the same gpu drivers. I've noticed it's the same with Nvidia. In fact Nvidia seems to just release one propriety gpu driver that works with all they're cards or at least is supposed to work.

Any info would be appreciated, ultimately I just want to see BMD support open source mesa drivers, that is the new standard for amd on linux.

P

Problem with Centos is that it's outdated quite a lot.Try a rolling release distribution like Manjaro with Kernel 4.20 and it should run just fine- that's what I've been doing for quite a while.

I finally managed to get DR starting, but apparently it does not find any OpenCL capable GPU. My system is a laptop with an i7 8705G CPU. So I have an Intel UHD GPU and also an AMD GPU. I am able to run other programms (some simulation stuff) on the second AMD GPU with DI_PRIME=1. So this should be ok.

However in CLINFO I get only the Intel GPU shown as OpenCL compatible. Even that I installed the amdgpu and also opencl-amd and also ocl-icd.

If I install opencl-mesa clinfo finds the GPU, but shows only OpenCL 1.1 and If I understood it right DR needs at least 1.2

Wondering if any of y'all have issues with 15.3 Studio recognizing the Mini Panel on a vanilla build of upstream CentOS 7.6? Have tried fidgeting around with adding /opt/resolve/bin to the first spot in the $PATH so that they system can access libusb-1.0, have also been fidgeting with udev rules, and now wondering if maybe SELinux is blocking something somewhere. Don't know how to let something through SELinux though. Any ideas?

Seth Goldin wrote:Wondering if any of y'all have issues with 15.3 Studio recognizing the Mini Panel on a vanilla build of upstream CentOS 7.6? Have tried fidgeting around with adding /opt/resolve/bin to the first spot in the $PATH so that they system can access libusb-1.0, have also been fidgeting with udev rules, and now wondering if maybe SELinux is blocking something somewhere. Don't know how to let something through SELinux though. Any ideas?

For other folks who might find this: I think I figured it out. I believe everything went haywire when I tried to run Resolve from several different non-administrator users. It's best to just run it from one administrator user. Mini Panel is working fine now.

So i tried to do an edit with resolve on Ubuntu 18.10 and it crashes as soon as i try to do anything in fusion other than basic text, and playback is not very smooth and i am using prores hq 4k footage. The same machine handles this much better when i use windows 10. I do have gtx1060 6gb , 32gb ram, ryzen 7. I am trying my best to get off the windows but Linux is fighting me every step of the way.

Hakim Craddock wrote:So i tried to do an edit with resolve on Ubuntu 18.10 and it crashes as soon as i try to do anything in fusion other than basic text, and playback is not very smooth and i am using prores hq 4k footage. The same machine handles this much better when i use windows 10. I do have gtx1060 6gb , 32gb ram, ryzen 7. I am trying my best to get off the windows but Linux is fighting me every step of the way.

Hakim, the Linux build is designed for RHEL or CentOS on an Intel CPU. When you deviate from that, you're really on your own, trailblazing.

Hakim Craddock wrote:So i tried to do an edit with resolve on Ubuntu 18.10 and it crashes as soon as i try to do anything in fusion other than basic text, and playback is not very smooth and i am using prores hq 4k footage. The same machine handles this much better when i use windows 10. I do have gtx1060 6gb , 32gb ram, ryzen 7. I am trying my best to get off the windows but Linux is fighting me every step of the way.

Hakim, the Linux build is designed for RHEL or CentOS on an Intel CPU. When you deviate from that, you're really on your own, trailblazing.

Hakim Craddock wrote:Ok i will give manjaro a try again. I only switched because it seemed Ubuntu has the most support. i never tried a full Edit on Manjaro. I did attempt a Full edit on Ubuntu with no luck.

BMD literally designs the build for CentOS. Why do you say that Ubuntu has the most support?

Hakim Craddock wrote:Ok i will give manjaro a try again. I only switched because it seemed Ubuntu has the most support. i never tried a full Edit on Manjaro. I did attempt a Full edit on Ubuntu with no luck.

Editing a whole feature on Manjaro Gnome, using lots of Fusion sequences as well. Works just fine and really speedy (with mutter performance patches).

Hakim Craddock wrote:Ok i will give manjaro a try again. I only switched because it seemed Ubuntu has the most support. i never tried a full Edit on Manjaro. I did attempt a Full edit on Ubuntu with no luck.

BMD literally designs the build for CentOS. Why do you say that Ubuntu has the most support?

Sent from my iPhone using Tapatalk

Ubuntu does have the most support as an OS.. Not talking about BMD making the poor decision to build the Linux Version of Resolve around CentOS. But Using Ubuntu as a daily driver seems IMO to be the easiest way to go except for using Resolve.

Hakim Craddock wrote:Ubuntu does have the most support as an OS.. Not talking about BMD making the poor decision to build the Linux Version of Resolve around CentOS. But Using Ubuntu as a daily driver seems IMO to be the easiest way to go except for using Resolve.

Agree, but I wouldn't "except" Resolve. I'm using Resolve on three up-to-date Ubuntu 18.04 workstations with NVIDIA 418.56 drivers (very fast) and they all work quite well. Building a new Ubuntu system with NVIDIA and other drivers is a breeze compared to CentOS.

BMD seems to have fixed a few of the initial Ubuntu installation problems. They have a .deb install for Desktop Video now, and I suspect at some point (maybe even NAB) there will be a .deb for Resolve. Fingers crossed.