[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-multimedia
Subject:    Re: Arts::Video
From:       Ewald Snel <ewald () rambo ! its ! tudelft ! nl>
Date:       2002-04-10 20:27:23
[Download RAW message or body]

Hi Jason,

[...]

> I've had a quick read of the white paper and it looks to me like an attempt
> to bring the same conceptual modularity of art's sound to video.
>
> As far as I can understand, this is perfect for what I had in mind for
> video editing - there's space in the "raw video" on the diagram to add
> extra video-processing modules, including merging two videos together
> (cross fades, wipes, chroma, 3D?), colour balancing, distortion effects, as
> well as the host of arts sound plugins, followed by mixing everything
> together and then replace the on-screen renderer with a "render to file"
> module. How possible it is to add hardware acceleration into this, I'm not
> sure because I have not looked into the topic yet.
>
> Can the xine framework also be extended to do this kind of functionality?

It would be possible, but you don't need to add this functionality to xine. 
You can use xine for implementing the "Worker" and possibly parts of the 
"Master" as well. The xine video drivers could be use as "Video Renderer", 
although it might be better to use libav for this. Another use for xine could 
be the "Producer" part, especially for inputs like mms:// which are supported 
by xine but not by KDE.

Using xine or GStreamer will not limit the possibilities. You can still use 
the design for Arts::Video. It should only be used (IMHO) for implementing 
certain functions of the framework (like decoding), not the framework itself. 
This will speed up the development process significantly.

> Cheers,
> Jason

bye,

ewald
_______________________________________________
kde-multimedia mailing list
kde-multimedia@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-multimedia
[prev in list] [next in list] [prev in thread] [next in thread]