[Kdenlive-devel] KDEnlive Bugs I encountered

[Till Theato]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/17/2012 06:49 PM, Alexandre Prokoudine wrote:
> On Tue, Jan 17, 2012 at 8:32 PM, Dan Dennedy wrote:
> 
>> Was it not obvious that this troll needs the Easy button that
>> makes everything crash-free and 10X faster?
> 
> Actually he raised quite a few valid points.
> 
> I've been asked about proxy clips activity and flags on multiple 
> occasions, applications should handle crashes nicely indeed, and 
> personally I find the current UI for keyframes counterproductive
> and incosistent.

The recently introduced clip jobs
(http://kdenlive.org/users/j-b-m/kdenlive-latest-developments) should
improve the visibility issues with proxies. What's the problem with
the flags? Should we maybe provide more presets for proxies, so users
do not have to deal with ffmpeg (yes, we should ;)), or is this not
the problem you are talking about?

How can you handle a crash in a nice way? An application shouldn't
crash, but when it crashes it's too late. The only option then is to
offer crash recovery and to provide ways for getting in touch with the
developers. Both is done by Kdenlive.

Oh yes and the different UIs for keyframes are a bit of a mess. Both
from user and from developer perspective. Hopefully someone can work
on improving the situation there after refactoring is done on this
part of the code.


regards

Till
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8Ye54ACgkQzwEyz7QP6nSGSQCcDkM8dF05RVt3MacJ0b4TdLBS
daYAn1iUxAuHQav0Ue6460vBQQeR10gL
=Elsb
-----END PGP SIGNATURE-----