Good example to show usage of tee

[Krzysztof Konopko]

On 13/11/12 16:06, Nathanael D. Noblet wrote:
> On 11/12/2012 09:30 AM, William Manley wrote:
>> On 09/11/12 16:53, Nathanael D. Noblet wrote:
>>> On 11/09/2012 12:44 AM, Baby Octopus wrote:
>>>> Thanks for your suggestion. I see gst_launch_parse takes in commandline
>>>> string and then creates a pipeline based on this, which actually
>>>> simplifies
>>>> my task. But all I want to know is, is this the right way to create a
>>>> pipeline even when you are creating a product of your own, which you
>>>> will
>>>> market? Can I create any possible pipeline using gst_parse_launch(or
>>>> gst-launch) ?
>>>
>>> I would expect that you want to manually build the pipes. Often with
>>> complex pipes you need to attach to signals/events and doing so requires
>>> knowing the element etc.. which is easier if you instantiated it
>>> directly than searching through a pipeline for a matching element...
>>
>> I disagree.  With complex pipes I think parse_launch becomes even more
>> helpful as it becomes harder to visualise what the pipeline actually
>> contains, particularly with teeing and muxing, etc.  You can use
>> gst_bin_get_by_name to easily retrieve the elements.
> 
> How do you know what the element's named?

By setting its 'name' attribute.

> Also what happens if there are
> multiple of the same type of element, how will your code know which one
> you are looking for?
> 

Once you set the 'name' attribute for each of them, you know their
names. GStreamer won't let you set the same name for more multiple elements.

Cheers,
Kris