[gst-devel] Totem, Gst-Player, libgstplay showstoppers

Mathrick mnews2 at wp.pl
Mon Jan 26 14:25:10 CET 2004


W liście z pon, 26-01-2004, godz. 16:58, Julien MOUTTE pisze: 

> 4) Informations about codecs. xine provides the app developer with some
> informations about video/audio codecs. I need to get those informations
> from gstplay pipeline to compete with them.

What exactly do you mean by 'codecs'? Decoder elems used? Mime type of
video / audio? Something else?

> Proposed solutions :
>  a) Add some gst_element_found_tags calls in decoders so that they tell
> about the codec format they are about to decode.

Hmm, isn't format info already provided by caps? But if not, then unless
you're thinking of something wicked, it's probably the best bet.

>  b) Add some gst_element_found_tags calls in demuxers so that they tell
> about the different format of video/audio...

(see disclaimer in a) No, you don't want to burden demuxers with any
more info discovery that's strictly necessary to do proper demuxing. IMO
demuxers only give streams, and let decoders decide what to do with
them. Anything more comes from evil spirit ;)

>  c) Invent a new communication system/signal for that kind of stuff.

I don't think so, AFAIK tags were designed to be generic enough to
handle many types of info. Besides, we didn't spend week enlightening
Benjamin on streaminfo concept just to let you invent some other
mechanism for that now ;). And codecs probably count as a streaminfo.

Cheers,
Maciej

-- 
"Tautologizm to coś tautologicznego"
   Maciej Katafiasz <mnews2 at wp.pl>
       http://mathrick.blog.pl





More information about the gstreamer-devel mailing list