a rant on kdenlive!

2019/03/10 3:14 AM (UTC -5) | tildearrow

i kinda hate kdenlive... you wanna know why?

if you don't know what kdenlive is, then let me tell you: it's a video editor which is well-known in the Linux world.

ok, so here it goes.
there is a 1/10 chance every single change you do in your video project's timeline will result in the program borking your entire project and throwing it to the garbage.
you wanna know how that happens?
the program's timeline desyncs with MLT's (the framework used under the hood) timeline, causing the actual video and the timeline to be completely different for some stupid reason.
this results in things like "Cannot move video clip", and all the way up to crashes.
but the worst thing is, if you save your project while this has occurred, then you're basically saying goodbye to your project, since next time you come back to it, you'll have to fix everything! and as you may know, it is painful!

a freaking video editor shouldn't keep 2 timelines!!!
it should just have 1 timeline sync'ed to both the GUI, and the renderer (MLT)...

or better yet; why not use something that's not MLT, being aware of its stability problems?
it's stupid how so many open-source video editors rely upon the same engine... but the problem is when the engine is buggy!

every single open-source video editor sucks so far: (and i don't have resources for buying a commercial one)

• kdenlive has this stupid issue
• PiTiVi does not suit my needs, and its UI sucks (don't get me started with this... who the hell has the "Cancel" button at the top right and the "Remove" one at the bottom left?!)
• OpenShot has no features at all
• Flowblade may have the same issues as kdenlive (it uses MLT too)
• Cinelerra doesn't even launch
• blender is too slow (it's like trying to play crysis on your '90's PC)
• natron is slow too (despite being good), and STILL uses Qt4... when am I gonna talk about this?

open-source developers don't find issues because they don't test rigorously. they prefer to use automated tests and simple crap like opening the program, doing a single operation, and then quitting.
you don't do that! ever! the issues don't appear there. they appear when you actually *USE* the program. they appear on real-life cases.

this ends my rant... i might or may not add some pictures later, but for now, see you.