[gst-devel] set same caps for all tee's branches

[Miron Kunz]

Thanks Stefan,

Looks like I had my caps filter in the wrong place. I begun with this:

...!tee ! queue ! mycapsfilter ! audioconvert !audioresample ! audioconvert!audiosink

same on the second branch - mycapsfilter was placed between queue and audioconvert. The pipeline was paused when the second branch was being added. The second branch was the same as the first except that audiosink was replaced with monoscope!videosink.



Thereafter I moved mycapsfilter one step closer to the sink like this:

...!tee ! queue ! audioconvert ! mycapsfilter !audioresample ! audioconvert!audiosink.


And it seems to be the cure to avoid renegotiation causing the pipeline halt.

Thanks,
Miron.

-----Original Message-----
From: Stefan Kost <ensonic at hora-obscura.de>
To: Miron Kunz <mironoz at mail.ru>, 
Discussion of the development of GStreamer <gstreamer-devel at lists.sourceforge.net>
Date: Fri, 22 Jan 2010 23:46:40 +0200
Subject: Re: [gst-devel] set same caps for all tee's branches

> Am 19.01.2010 21:35, schrieb Miron Kunz:
> > 
> > Hi,
> > 
> > I have a pipeline ...!rtpdepay! alawdec ! tee name=m ! queue !audioconvert!audiosink m.!queue!audioconvert!monoscope!fakesink.
> > 
> > Monoscope and audiosink are using different number of channles and this leads to caps change while pushing data to alawdec's sink. Which in turn results in "non-negotiated" and stop of data flow.
> > 
> > How can I assure that 2 branches after the tee end up with the same capabilities?
> > 
> > I tried to use same caps filter before the queue element on each branch but it did not help.
> 
> How did you use it? Becasue thats exactly what you should do - use a capsfilter
> and fixate the properties that would otherwise be renegotiated.
> 
> Stefan
> 
> > 
> > Thanks,
> > Miron.
> > 
> > ------------------------------------------------------------------------------
> > Throughout its 18-year history, RSA Conference consistently attracts the
> > world's best and brightest in the field, creating opportunities for Conference
> > attendees to learn about information security's most important issues through
> > interactions with peers, luminaries and emerging and established companies.
> > http://p.sf.net/sfu/rsaconf-dev2dev
> > _______________________________________________
> > gstreamer-devel mailing list
> > gstreamer-devel at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>