[gst-devel] RE : Re: AMR caps incompatibility between muxer and encoder

[SP GLE]

Hi,
thanks for your answer, but if i change the amr decoder (amrnbdec) i
also have to change :
qtdemux, amrnbdec, rtpamrpay, rtpamrdepay,...

gst-ffmpeg and amr elements seems to handle the same thing with two
different names, 'audio/AMR' and 'audio/x-amr-nb'. 

Is it possible to 'force' negotiation to handle differents encoding
names in capabilities as the same entity, something like an adapter.

Thanks.


--- Benoit Fouet <benoit.fouet at purplelabs.com> a écrit :

> Hi
> 
> SP GLE wrote:
> > Hi, 
> > I'm trying to link an 'amrnbenc' element and a 'ffmux_mov',
> > amrnbenc SRC caps are
> >    Capabilities:
> >       audio/AMR
> >                    rate: 8000
> >                channels: 1
> >
> > ffmux_mov SINK Caps are
> >       audio/x-amr-nb
> >                    rate: [ 8000, 96000 ]
> >                channels: [ 1, 2 ]
> >
> > so linking seems incompatible, how can i link these elements ? Is
> there
> > a way to change capabilities ?
> >
> > failed negotiation between pads is attached for the following cmd :
> > GST_DEBUG=4 GST_DEBUG_NO_COLOR=1  gst-launch audiotestsrc !
> > audioconvert ! amrnbenc ! ffmux_mov ! filesink location=/tmp/f.mov
> >
> > Thanks.
> >   
> you have to change the source code of amr decoder, so that it is
> audio/x-amr-nb too on its sink pad.
> then compile and install back the library, and this should be ok :)
> 
> Hope that helps,
> 
> -- Ben
> 
> 



	

	
		
___________________________________________________________________________ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com