Hi,

I've got a beta quicktime reader plugin but I've done it like the avi parser from gstreamer 1.1. So, it seems that I will have to make a few modifications in my code to use the new gstreamer power toys... There is no problem about that, but before beginning the changes, I wonder why the avi (and so my quicktime plugin as well) contains the supported codecs hardcoded in the plugins ? What I understand is that the avi plugin create a decoder plugin following the fourcc of the track and this matching fourcc/decoder is hardcoded.

Wouldn't it be possible to output compressed chunks from the avi/quicktime plugins and let gstreamer autoplugin mechanism handle the problem ? To help the autoplugin mechanism, specific mime types could be added (video/avi/'fourcc') , or the buffer meta-data could be used, or maybe the caps negociation system... 

This permits to add directly a new avi/quicktime codec without rewriting any lines of the parsers. And the same thinks could be applied to the avi/quicktime writers plugin...

Just my two cents,

Yann.


Find the best deals on the web at AltaVista Shopping!
http://www.shopping.altavista.com