🧵 So, in order to do further testing with #BlackmagicResolve, I make it want to think it is activated already.

Because the demo version does not even read files from my cameras, so how could I test anything? Should I spend towards 400€ just to find out that the Pro version also doesn't work with my camera data?

(On Windows and OS X, there is no demo limitation on h264 video data. Only on Linux…)

There's a tool written in #Rust that will solve this for Resolve…

Theoretically. Now I cam facing Rust errors. I don't speak Rust. So I have to learn Rust in order to test #Resolve?

So, #NLE manufacturers are fooling #Linux users, and #Linux nerds are fooling Linux users again?

Rust explaines: “Feature attributes are only allowed on the nightly release channel. Stable or beta compilers will not comply.”

https://github.com/unknowntrojan/resolvepatch

Other “patches“ are written in good old Perl and don't have an effect.

I'm glad I don't do video editing for money these days, I'd have to by a Mac after 26 years on Linux.

🧵 20 min of 1-camera video shoot, already over 1hr trying to get a #NLE on #Linux to work.

#Lightworks current beta (I paid for the entire product range)… crashes on displaying RGB parade or vectorscope.

#DavinciResolve: Hard to install, free version does not read h264 video on Linux (only on Windows, Mac), “patch” to enabled Proversion testing without spending almost 400€ requires advanced knowledge of #Rust.

Now #OpenShot offers an #AppImage download, that by nature cannot work with #Pipewire audio. There is a #PPA for #Ubuntu users, though… https://launchpad.net/~openshot.developers/+archive/ubuntu/ppa

… turns out OpenShot cannot do fullscreen video preview. Just not possible. WTF.

Ultimately I must get #Resolve to run and learn to use it, it's an industry standard at least.

After all, this journey started with the desire to make a 3 minute video with the tool I already have and did pay for.

🧵 #Lightworks fails me, #Blackmagic doesn't want me to try their #DaVincieResolve since it can't do h264 on #Linux (except you pay a lot of cash), #OpenShot is too stupid (can't do full screen monitor, and after 5 minutes of not finding out how to mute an audio track, I gave up on it)…

… now back at where it all started with my video editing on 2014 or so: #Kdenlive.

Now that looks familiar still. And it still can't do GPU acceleration. Oh well, it can, but the option is greyed-out even though I have libmovit8 installed.

So while Lightworks has learned to effectively play back even h265 on elderly machines, even without GPU decoding, Kdenlive already struggles playing back 4k h264 with flip and flop effect on that clip. (Lightworks uses OpenCL for FX, as would Resolve)

Actually after now 1,5hrs of trying to get a decent #NLE to run on Linux, after more than 10 years of doing video on Linux, I'm not at all in the mood for doing creative video work any more now.

@phreaknerd

I opened up blender, tried to find anything that looked like basic video editing, got frustrated after 20 minutes of not being able to put a video file into it…

Sorry to say so, but… it doesn't make too much sense.

Tools like Lightworks and Resolve are made the way they are made for a reason. No, not referring to the bugs and incapabilities, but the way how editing, color grading, etc. does work in these.