Didn't have queues after the tee, thanks for that.<br>Can't seem to link them together though, I get <br>"Trying to connect elements that don't share a common ancestor: video-tee and queue1"<br><br>Since google is no help for this one, any idea what it means and how I should link the tee to the queue?
<br><br>Thanks,<br>Itay.<br><br><div><span class="gmail_quote">On 3/18/07, <b class="gmail_sendername">Mark Nauwelaerts</b> <<a href="mailto:manauw@skynet.be">manauw@skynet.be</a>> wrote:</span><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:<br>> Hi,<br>><br>> I'm trying to build a simple pipeline with multiple sinks.<br>> The structure is - videotestsrc ! ffenc_mpeg4 ! tee<br>> I then create two src pads on the tee, link each of them to a different
<br>> muxer (matroskamux) and link each muxer to a filesink.<br>> With only one sink in the pipeline, it works great. The tee pushes the<br>> buffer on both source pads, and both muxers receive them.<br>> Once I include the second sink in the pipeline, it stops working.
<br>><br>> Any idea what i'm doing wrong? Anything special that I need to do for it<br>> to support multiple sinks?<br><br>If by "stops working" you mean that the pipeline simply stops, i.e. blocks, then
<br>you may not have inserted queue's following the tee element. Doing so should<br>solve this [since each sink will hold its thread in PAUSED state, but with only<br>1 thread the other sink does not get a chance to reach PAUSED].
<br><br>If you mean something else (or do have queues), then what precisely ?<br><br>Regards,<br>Mark.<br></blockquote></div><br>