first of all, thanks for your quick responses (not only answering messages,
but also solving bugs :-)).
Regarding your comments to my previous message, I agree with you that trying
to give too many options to "normal" users will create more problems than
solve ! And also try to control all options will require the use of a huge
database and lot of programming, so no practical at all.
So what do you think about next idea: Create two differenciated tabs, one
for "normal" users and other for "advanced" users. In the first one, we'll
work always with templates, not allowing the user to make any changes. User
will select the template (DVD, for example), select the quality (High,
Medium, Low) with radio buttons and maybe another useful and not problematic
options (?). Something quite similar as now, but much more simple (far less
For advanced users, as I proposed, we may let them set any standard ffmpeg
parameter and, if choosed, even pass directly the parameters to the program
in the same way as now. It's supposed for an advanced user that he knows
which parameters are compatible or not, so if the final output is not what
he wants is his fault !!!
Regarding my second point in the message (option to create image clip),
please is up to you to decide ! From a user point of view, doesn't matter to
have the option. My suggestion was more related to the fact that, from a
programming point of view, maybe it's better to maintain as few option as
possible. But I repeat, it's up to you.
Finally, two new small bugs detected (maybe now for version 0.6 ? :-)):
- When you open a project and, for any reason, any of the files is missing,
you receive a message from the program asking if you want to find the file
elsewhere or remove from the project. If you select the option to remove,
the program always crash !!!
- When you work with keyframe effects (for example audio volume) and have
some key frames in your clip, if you select any of them (say key frame 4),
the information in the effects stacks tab is OK (index no., position and
gain). But if you then select another clip to work, do anything and then
come back to the original clip, the index no. has changed to 0 although the
rest of parameters are OK and the selected key frame is also OK (blue mark
in the clip). Don't know if this may affect the program, but just in case
Thanks as always for your help and best regards.
On Wednesday 21 March 2007 18.55:03 Juan M wrote:
> This example is based on my previous messages and, obviously, can be
> ammended as needed to fit other needs. But I think should be a good basis
> to start. Simple and practical !
First, thanks for your input!
Some comments: the design looks ok for me but the big problem is that you
can't really just let people change a codec or a bitrate because there are
many incompatibilities. I don't understand all ffmpeg parameters but I did a
lot of trial & error to find some usable profiles for Kdenlive. My
showed that you can't just let user change bitrate or any other parameter
freely, because it simply won't work. If you set the bitrate too low or too
high for your image size, it will fail. Some codecs (quicktime for example)
only accept frame size if it can be divided by 16... Also, you can't mix
audio codecs with some video codex...
It seems to me that it would almost require a database to calculate which
codecs are compatible, which size, which bitrate can be set for each size,
If someone has an idea how to solve the issue, I am listening because that
too much for me.
> more useful as previous. But my question is. Is it still necessary the
> option to "Create image clip" ? I think now is obsolete as you can obtain
> the same result (and much more) with the other via.
Well I don't really care... the "create image clip" menu entry still allows
you set the clip duration without having to open the clip properties
afterwards, but you think it is cleaner to remove it I can do it...