I am still trying out different #video #editors whenever I have to do some editing. After having had good experiences with #pitivi in the past, I recently tried #davinciresolve in a #distrobox container. Yesterday, I took a look at #lightworks, which, among the commercial options, can be installed refreshingly easily as a #flatpak. #linux
#lightworks
0 posts0 participants0 posts today
Continued thread
#Lightworks vs. #DaVinciResolve
Well, Resolve is the standard tool now. The free version can do a lot, and to pro version is less expensive than others (such as Avid Media Composer… and who likes subscription models like Adobe Premiere).
It has a very good audio engine that is more like the one of a #DAW. Poeple love it for its sophisticated FX pipeline that can do incredible things, like motion tracking masks, or really pro color grading.
You won't get it to run on #Linux if you're not a full nerd. The installation is too broken.
Lightworks runs out of the box. You can do pretty decent editing with it. No motion tracking, no speed ramps, and the audio mixer tab makes you cry. It can't even normalize a track. It has learned VST3 by now, but you can only apply FX to segments, not to entire tracks.
The video FX of LWKS are pretty decent, good color grading, you can apply LUTs… and they are all computed in the GPU. Sadly it does not do h264/h265 GPU decoding, which is key in 4k editing.
Professional #VideoEditing on #UbuntuStudio #Linux 24.04:
#Lightworks #NLE works, but when set to #Jack audio and actually using #Pipewire in the back… in case of a crash, your Pipewire is jammed, you need to reboot like a #Windows system. Lightworks has the usual pile of bugs, and with every bug fixed, the dev team introduces some new ones. Like the desired #CineForm RGB444 export, resulting in files like… see attached.
#DaVinciResolve installer complains about dependencies, but the libraries are present. It installs its own libraries which are incompatible with Ubuntu, so you need to remove them. Then you find out that it doesn't find your GPU and refused operation. You find this blog post with a instructions how to install the proprietary graphics driver by AMD, but this fails. You end up not using Resolve (again).
For most people, #kdenlive will do the job.
Replied in thread
Migrating to #UbuntuStudio 24.04 from Kubuntu 18.04 / kxStudio.
Well, looks good, is tedious. Basically spent the whole day already on this.
#vcvRack refuses to use Jack (which is indeed #Pipewire here)… but it seems to to the job when set to #Alsa.
#DaVinciResolve insists on having no GPU, turns out it needs proprietary #amdgpu drivers. Not a priority. It also needs manual intervention removing some bundled libraries that actually do not work on any Ubuntu and that kind of BEEP.
#Lightworks is a priority and after some fiddling it works in #Jack mode. (Latest Lightworks Pro 2025.1 release, I did the upgrade.)
Got all my #WindowsVST to run again except for some crap by Melda which I had used only once. #Ardour and #Mixbus are good. But I need to re-enter the $§%& license stuff for the VSTs everywhere, now where did I put that…
Now what I didn't even touch is my other user on the same machine that does the office work.
Replied in thread
Continuing with #UbuntuStudio 24.04 – my hard disk bay has given up working with the new #Linux, so how will I re-import data from my old SSD now?
#DaVinciResolve, as usual, does not run for no apparent reason.
#Lightworks however, as usual, does.
I uninstall the #Ardour of Ubuntu Studio because I have my own installation. Which works out of the box. So does #Harrison #Mixbus.
A where did the X kill go with Ctrl+Alt+ESC? Not possible any more. Why are #Ubuntu makers taking the fun out of #Linux?
Is anyone here using #lightworks for video editing on #linux and would like to share their experience in a sentence or two? 