Kdenlive 24.02 open source video editor released
kdenlive.org
kdenlive.org
On Linux for the last 6 or 7 years, I've used Lightworks just because the free version has been good enough for what I've needed for nearly everything, and for the few times I need higher resolution I have just paid like $20 for one month of "premium". I didn't have any objective criteria for choosing Lightworks, other than "it's been used for 'real' movies!"
That said, I'd prefer to keep things open source, so I'd rather move to a FOSS thing like Kdenlive or Blender, if they're comparable (or better!) than Lightworks. Anyone have experience with all three?
Unfortunately I can't compare against Lightworks or Blender, because I tried Kdenlive and it worked great, and there was no reason to search for alternatives.
One thing to note is that Kdenlive and Shotcut both use the MLT video editing framework [2] under the hood, so their capabilities and constraints are very close to each other's. That said, their UIs are their own and some things may be easier to do in one over the other, may be a matter of personal preference. AFAIK Shotcut is developed by the same people who built MLT, but I don't think that gives it any particular advantage. Also both of these apps have the largest ready-made effects toolbox out of the four apps I mentioned at the top.
Blender's VSE (video sequence editor) is great if you need fine-tuned 2D animations of elements because you can use all the same awesome keyframing tools you'd use for 3D animation, but it's severely lacking in other aspects, especially in the effects dept (you can crop, blur, mask, but not much else). For some reason you can't use Blender's compositor node system with video, which would enable many more capabilities if possible. There's also a steeper learning curve if you've never used Blender before because its UI breaks many conventions.
Olive is a newcomer that doesn't get enough attention, but IMHO it was at one point the most promising OSS video editor out there. Sadly the developer works on it on his free time, and he's recently said that he's pausing development because he doesn't have the resources to work on it any more. I'm really hoping a miracle happens.
There's two versions of Olive, 0.1 and 0.2 which is a complete rewrite. Both versions are good, but they work pretty differently. What got me excited about 0.2 is that its effects are node-based (unlike MLT-based editors which are stack-based), which enables far more advanced editing, although you probably wouldn't need that unless you're working on something quite ambitious.
With Kdenlive, it's frustrating to add a simple block of text (you can have to create an overlay, and then configure that overlay, and place it roughly where you want), but the final rendering takes only minutes and it's stable enough to work with for larger projects.
Can't comment on Lightworks.
Might be time to think about trying Blender again. This was posted here on HN about a month ago. https://aras-p.info/blog/2024/02/06/I-accidentally-Blender-V...
Do Kdenlive or Shotcut even support GPU rendering yet?
Blender is probably still the best open source video editor by quite some margin.
if you need a feature set like iMovie, why not use davinci resolve? its available on linux. not open source but neither is imovie
or simply H264/H265 which is a dealbreaker for a lot of people.
Linux H.264 and H.265 support is Studio-only[1] (presumably because royalties).
If you don't care about any other Studio features, converting to/from an intermediate codec — DNxH[DR], say — on import/export using another tool like FFmpeg seems like a reasonable workaround for most applications.
Since Resolve doesn't support H.264/H.265 passthrough (on any platform), the only generation loss added by this approach will be from DNxH[DR] encoding, which, assuming a sufficiently high bitrate for the intermediate codec, should be minimal.
Note that even Resolve Studio doesn't support AAC audio on Linux[2], so, for many H.264/H.265 projects, you'd end up with pre-/post-conversion steps even if the video codecs were supported.
[1] https://documents.blackmagicdesign.com/SupportNotes/DaVinci_...
[2] https://documents.blackmagicdesign.com/SupportNotes/DaVinci_...
Blender features a node-based compositor (Like Nuke) and an NLE (movie editor). Both these tools are fine when used within a Blender workflow, but they are troublesome to use in a stand alone capacity.
In my opinion, the most important feature of an NLE is its media optimization strategy without which editing is a chore. I now use DaVinci by Blackmagic, which is free. They inherited the amazingly efficient proxy system from the DaVinci colour grader. To this Blackmagic added their own codec voodoo which is not insubstantial. DaVinci and Blackmagic footage together run as smooth as butter.
Avid Media Composer is also free but limited to 1080p and has many other limitations that can make it tricky for all but the simplest projects. Again, if you pay up you get what Hollywood editors use, but at $20 to $50 per month subscriptions isn't great for occasional use. It requires some setup and configuration that's not intuitive. I had to google how to have it use only one display and not to just assume I want it to take over all attached displays. It also has a bunch of DRM and copy protection crap that requires a bunch of additional programs and runs permanent Java processes.
Blender has a video editor. That much is true. It just isn't very good. Editing is imprecise and clumsy. You have to manually add frame allotments to the timeline if you go past the runtime. It's only saving grace is the ability to do 4K (probably higher if you want). There's no previewing a clip before you place it on the timeline. All editing is done on the timeline by positioning the playhead. There is an upfront cost for proxy editing, so if your source material is high resolution and long, expect to wait a long time for it to process the clips before you can play or edit them. I've found that when performance starts to suck you'll have to manually rebuild the proxies—maybe go to lunch.
I haven't tried Kdenlive, but its editing ability looks similar to Blender in that you have to put the clip on the timeline before doing anything. Coming from Lightworks or Media Composer this workflow sucks. I'm still going to give it a try, but I'm not sure it is for me.
Of course, like any open source project, part of the reason why those bugs exist is my fault for not engaging with the project ... but let's ignore that
It's really good; the developers should be proud.
I think it's fair to say Kdenlive exposes much more power to the user, but I felt that I had a bit of learning to do to understand a few things which have opinionated defaults in programs like Davincei Resolve. For instance, I had to use a composition between two tracks and choose the type of compositing to use between them in order to get transparency exported, whereas in other programs this would default to add or multiply which behaves in a predictable way with less effort (but with less control).
In saying that it feels like Kdenlive is an incredible amalgamation of very powerful plugins and parts!
I wish it had a bezier curve editor for things like fades or tweaking keyframe animations.
After a while I switched to blender (since I used it to create the source footage) but it was a little glitchy, the video somehow getting out of sync with animated opacity and it confused me how you "Render Animation" in blender which is the same option as for rendering your (3D) Scene in blender, and where to find the option to turn off the video editor composition which overrides this as soon as you start adding clips to the video editor. It doesn't really compare as it's just blender, with all it's intricacies, and video editing bolted on to it, whereas Kdenlive is just about video editing.
Anyway, great work!
Another obvious thing I often miss is the ability to change the length (duration) of static image clips in the project bin (currently? - haven't tried the latest version yet - the only way is to set a length in the settings before importing). It seems like it doesn't matter at first, since it's a static image, but start adding effects and keyframes and any resizing done in the timeline can mess everything up.
I always use KDE as my primary desktop and love it. It's amazing. Kdenlive is only one of the many amazing apps they produce. And I'm proud to donate to them monthly.
Do you do green screen? I've had a horrible time finding a web camera that doesn't mess up the green screen by auto color correcting. It ends up putting a weird tint on the video that looks awful. Any web cam recommendations that work good with linux/obs?
Sometimes I need to archive trainings for later use. So I use the HDMI out to record it from another computer. Then I can edit the video to make it more to the point, add some on-screen popups etc. Then I share those on MS Stream (because unfortunately that is the platform we have to use despite it being crap).
It's a bit of a workaround but it does the job. The cheap Aliexpress HDMI dongle does the job admirably, it gets really really hot but it survives the day :)
But green screen yeah no never tried that, sorry.
I am a newbie, so I am learning to make videos and edit them.
Yes! I'm a professional editor and I've waited years for this. Seems it's not quite there, but they're getting close. At work I have to use Premiere I have to use Premiere and Resolve, but at home I'm on this long quest to open source everything. The lack of easing has held me off from Kdenlive even for home use. Nothing looks more amateurish than those stiff linear animations and transitions.
Is that the case with say 24.02 or has that thing been improved?
Far less regularly, I've seen crashes when replacing video files used in the project.
I also recommend setting the framerate of a project first thing and then never touching it again.
The UI and features were plenty for my use case otherwise.
Admittedly I always want kde apps to be good but in this case it actually is. Openshot was easier to learn though, personally.