[gst-devel] Overhead of 1-to-1 `tee' elements

[Leif Johnson]

Hi Lars -

As far as I understand it (which is very little, so beware)
an additional element in the pipeline just adds one more
element to the scheduler, and a 1-1 tee element should be
fairly fast ; in the 1-1 case the tee would just copy each
incoming buffer to a single output buffer.

For the second part, it depends on how you want to use your
pipeline. If you want to be able to add and remove elements
to the tee *while the pipeline is playing* (i.e. by pausing
just the tee element for a very brief time, then
adding/removing the element and setting the tee to play
again) then you'd always need a tee element in your
pipeline. If you want to add or remove elements from the tee
while the whole pipeline is stopped, then you could leave
the tee out entirely when you don't need it. Hope this
helps.

leif

On Tue, 21 Jan 2003, Lars Weber wrote:

> Hi everyone!
> 
> A short (and hopefully simple) question:
> 
> What is the overhead introduced by 1-to-1 (i.e. non-multiplying) tee
> elements?  If a dynamically created pipeline _only sometimes_ needs a tee
> element at a certain point, would I still _always_ insert the tee-element
> for simplicities sake or should I try to avoid this?
> 
> Regards,
> Lars
> 
> PS: Thanks for all your hard work on GStreamer!
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Scholarships for Techies!
> Can't afford IT training? All 2003 ictp students receive scholarships.
> Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
> www.ictp.com/training/sourceforge.asp
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

-- 
Leif Morgan Johnson . http://ambient.2y.net/leif/
IAESTE trainee      . http://www.iaeste.org/
Salomon Automation  . http://www.salomon.at/