KDEnLive mockups

On the prompt of KDEnLive enthusiast Lucio Correa, I had a look at the usability of KDEnLive — the only serious OSS Linux video editing app today (Cinelerra is still an unusable joke for me, sorry). I have used KDEnLive very cursory, so giving real feedback about the usability, will take a long time. But their exporting dialog is the one that mostly caught my attention for being so inflexible and useless for my needs. So, I redesigned that before anything else.

And when you click custom, the window expands:

Of course this second dialog looks busy — audio should be in its own tab if the developers don’t want the window to get longer. However, I mostly wanted to show which features I need to be there, easily accessible, rather than the actual widget arrangement.

I left out the “render selected zone, from time __ to time __”, because this is a feature that should not be part of the standard exporting dialog, but instead a right-click option on a selection in the timeline that automatically fills up the right timecode values and loads the exporting dialog.

6 Comments »

Lúcio Corrêa wrote on October 18th, 2007 at 4:44 PM PST:

Thank you again, Eugenia! And we are waiting for your thoughts in the main application too.


Luis wrote on October 19th, 2007 at 5:17 AM PST:

Yes, I agree that the exporting dialog is not very user friendly now if you want to customize the options and I also thought it’s the most urgent improvement it needs (now it’s a command line that you have to edit).

Your suggestion looks much better. The “custom” view is already an advanced feature, so it’s good that it offers enough options.

Hopefully once they port it to QT4 we’ll continue to see this application mature rapidly. As you say, it’s the only serious app of its kind for Linux today. And a very good addition to the Linux desktop that would help to take it to a higher level.


Richard wrote on October 19th, 2007 at 6:17 AM PST:

Yes, I like that approach, although I do have one little grief that have been struggling myself with how to present it. That is the “Analog Blank”, which does interfere a little with non-square pixels.

Example from PAL-Land:
Video from a DV-Camcorder is 720×576. But a square pixel TV Image has 768×576 Pixels. You do not scale directly though, but you scale to 788×576 Pixels, and then chop of 10 Pixels on the left and right. Don’t ask me why, but appearently this is some legacy thingy, and I find it really hard the present that in a user interface without lengthy explainations.


Richard wrote on October 19th, 2007 at 6:22 AM PST:

And another question: what is the supposed behaviour for storing and naming new templates?

I would understand it like this: When I click “Custom” Button, the current preset is shown in the form, and when I change it, and select another preset, my changes are discharged, but when I click the “Disk/Store” Button, A dialog pops up where I can enter a new preset Name.


This is the admin speaking...
Eugenia wrote on October 19th, 2007 at 12:35 PM PST:

Yes, that’s it. The presets that come with the app can not be modified. If you change them, you must give them another name.


This is the admin speaking...
Eugenia wrote on October 19th, 2007 at 1:43 PM PST:

>The “custom” view is already an advanced feature

There are actually three levels in the UI. Each one more advanced than the other. The first level, is the first screenshot and it’s meant for newbies. The second level, is the second screenshot and it’s meant for intermediate users. The third level is the “configure codec” and “customize command line” popup dialogs which will be different for each codec and only experts should use.


Comments are closed as this blog post is now archived.

Lines, paragraphs break automatically. HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

The URI to TrackBack this blog entry is this. And here is the RSS 2.0 for comments on this post.