OK, my bad... Forgot to add it to the pipeline. Sorry for that. Thanks again. <div>On 3/18/07, Itay Kirshenbaum <<a href="mailto:ikirsh@gmail.com"> ikirsh@gmail.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Didn't have queues after the tee, thanks for that. Can't seem to link them together though, I get "Trying to connect elements that don't share a common ancestor: video-tee and queue1" Since google is no help for this one, any idea what it means and how I should link the tee to the queue? Thanks, Itay.<div> <div>On 3/18/07, Mark Nauwelaerts <<a href="mailto:manauw@skynet.be" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> manauw@skynet.be</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Itay Kirshenbaum wrote: > Hi, > > I'm trying to build a simple pipeline with multiple sinks. > The structure is - videotestsrc ! ffenc_mpeg4 ! tee > I then create two src pads on the tee, link each of them to a different > muxer (matroskamux) and link each muxer to a filesink. > With only one sink in the pipeline, it works great. The tee pushes the > buffer on both source pads, and both muxers  receive them. > Once I include the second sink in the pipeline, it stops working. > > Any idea what i'm doing wrong? Anything special that I need to do for it > to support multiple sinks? If by "stops working" you mean that the pipeline simply stops, i.e. blocks, then you may not have inserted queue's following the tee element.  Doing so should solve this [since each sink will hold its thread in PAUSED state, but with only 1 thread the other sink does not get a chance to reach PAUSED]. If you mean something else (or do have queues), then what precisely ? Regards, Mark. </blockquote></div> </div></blockquote></div>