[Kdenlive-devel] moved here from kde-multimedia (was Re: Multimedia Frameworks)

[Jason Wood]

On Friday 25 Oct 2002 7:50 pm, Christian Berger wrote:
> > > > Easy. But my engine can do _much_ more already. And of course I
> > > > don't want to get the features burried because the XML can't handle
> > > > them ;-)
> > >
> > > What kind of things are you talking about here? Is it a case of
> > > transitions, effects, etc?
> >
> > Yes. My goal is neither an engine nor a GUI, I want a video solution. I
> > will not work on effects for an engine I cannot use in the GUI. If
> > somebody else wants a gui that ignores half of the features, ok, I would
> > say that both needs to go hand in hand.
>
> Well the GUI can do all effects by definition. An effect is just like a
> function in a compiler. You have inputs and parameters and a name. Maybe
> later even something which specifies how the effects should be previewed
> in the engine.

The realisation that I have had recently is that if you are going to make a 
preview, you might as well ask the cutter to do it. If you don't, then you 
have to effectively duplicate a cutter within the GUI, and you will also have 
a great amount of inconsistancy between what the preview is and what the 
final output will be.

This, along with the need to ensure that the GUI is capable of viewing exactly 
the same files that the cutter can generate that makes me think it is 
essential to use the cutter dierctly for all playback.

My plan on how to do this will all become (hopefully!) clear as to how to do 
this when I upload the null cutter.

Cheers,
Jason

-- 
Jason Wood
Homepage : www.uchian.pwp.blueyonder.co.uk