Capsfilter causes problems in master

Matej Knopp matej.knopp at inmethod.com
Fri Oct 7 02:41:34 PDT 2011


Hi,

I updated gstreamer today and I'm having weird issue when using capsfilter.

I have following pipeline

audioconvert -> capsfilter -> audioresample

I set the following caps on caps filter:
audio/x-raw-int, endianness=(int)1234,signed=(boolean)true,
width=(int)16, depth=(int)16,
channels=(int)2,channel-positions=(GstAudioChannelPosition)<
GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT,
GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT >
(note that there is no audiorate)

and I get the following warning:
GStreamer-WARNING **: pad audioresample0:sink accepted caps
audio/x-raw-int, endianness=(int)1234, signed=(boolean)true,
width=(int)16, depth=(int)16, channels=(int)2,
channel-positions=(GstAudioChannelPosition)<
GST_AUDIO_CHANNEL_POSITION_FRONT_LEFT,
GST_AUDIO_CHANNEL_POSITION_FRONT_RIGHT > although they are not a
subset of its caps audio/x-raw-int, endianness=(int)1234,
signed=(boolean)true, width=(int)16, depth=(int)16, rate=(int)48000….
(because there is no rate set in caps; The rate is later of course set
on buffer passed to elements)

What happens is that the exact same caps as I set on capsfilter is
also set on the downstream element sink. I don't understand why this
happens suddenly.The caps is supposed to filter format of the upstream
element, so why is it being sent downstream?

Can anyone clarify this behavior?

Cheers,
Matej


More information about the gstreamer-devel mailing list