The very I-st snag here is identically the same as it was with the Blender = both seem to be oriented not around the initial video file, but rather around the "Project" instead.
Which is fine of course, but both pose the very same problem for a I-st time user: how to open an existing video file? :LOL
Sony -> Magix Vegas is similar. Project is needed to assemble video + audio + titles etc.
Oh, don't get me wrong, the project's oriented SW has certainly its place and some important niches, esp. if one is starting an assembly from scratch.
However, there is a substantial fraction of users who just want to open an existing vid. file, then do some culling/cutting out unwanted pieces, do edits & fine tuning, and then to save it in the exact same, original format. And since SW clearly can read such files, meaning it has a full knowledge encoded already, then it is a waste of time and effort to enforce I-st the transcoding it into another (which I think this is being done within the KDEnlive - perhaps unto the MOV, but it needs a further confirmation), and II-nd to recode it back to the original formatting upon completion of the whole process

; moreover the KDEnlive seems to be very slow a processor there.
I saw your other post about color correction. It looks like you are very far along with Blender, so you might want to stick with it, because it is truly professional quality software.
Yep, the B is very powerful, GUI is extensively flexible and rich, so much so that one can reconfigure it to suit the needs at hand to an extent that two such new configurations will look completely unsimilar.And if one is still usatiated, there is also a Python console for some auxiliary user's scripting to stich and streamline the processing (haven't tried it yet, so just reporting).
At first I was completely lost, intimidated even, but the effort paid out in a relatively short time, despite one of steepest learning curves ever experienced. Also reassuring... is the fact the authors went to pains to buy it from the originally owing company (at the times when crowdfunding was at its infancy, for $100k), and hence there is a pledge it is going to be a free SW perpetually. With an amount of users' support and development it might even stand a chance to NOT disappear for some foreseeable future
Unfortunately, as already stated in another post earlier, the B's rendering is disappointingly slow.
Maybe, just maybe, there is a way to output the final ffmpeg script for the actual encoding instead of B's execution; after prototyping it first there and utilizing all the perks of such fantastic GUI? But so far I was out of luck in finding HOW
So, the bottom line is that I'm still going to examine the other SW vid-editing packages mentioned here - in a quest that perhaps one of them can be The Grail: allowing to do every necessary task within it, and... speedily too!
Which is very highly unlikely, though, as in my current workflow one must use pretty many different SW packs for completion - and that is so even for quite simple and rather primitive edits.
jpr2
--
~
street candids (non-interactive):
http://www.flickriver.com/photos/qmusaget/sets/72157609618638319/
music and dance:
http://www.flickriver.com/photos/qmusaget/sets/72157600341265280/
B&W:
http://www.flickriver.com/photos/qmusaget/sets/72157623306407882/
wildlife & macro:
http://www.flickriver.com/photos/qmusaget/sets/72157600341377106/
interactive street:
http://www.flickriver.com/photos/qmusaget/sets/72157623181919323/
~