sticky events

Stefan Sauer ensonic at hora-obscura.de
Mon Mar 3 11:46:19 PST 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/03/2014 08:35 PM, Sebastian Dröge wrote:
> On Mo, 2014-03-03 at 20:23 +0100, Stefan Sauer wrote:
>> On 03/02/2014 11:20 PM, Sebastian Dröge wrote:
>>> On So, 2014-03-02 at 22:51 +0100, Stefan Sauer wrote:
>>>> On 03/02/2014 09:44 PM, Stefan Sauer wrote:
>>>>> hi,
>>>>>
>>>>> I tried to do the proper pad blocking thing in buzztrax again, now
with
>>>>> 1.0. One issue I face right now when adding sources (or sources +
>>>>> transforms) to adder/audiomixer is that the new elements are not
>>>>> negotiated. While debugging I was wondering whether sticky events are
>>>>> replayed on the new request (sink)-pad of adder. They are not. In tee
>>>>> this is done. If I simply create the counterpart of the tee code in
>>>>> adder (https://gist.github.com/ensonic/b73c16958d9304dfd2e0), I get
>>>>> (lt-buzztrax-edit:6264): GStreamer-WARNING **: pad '':sink_2 pushing
>>>>> stream-start event in wrong direction
>>>>> (lt-buzztrax-edit:6264): GStreamer-WARNING **: pad '':sink_2 pushing
>>>>> caps event in wrong direction
>>>>> (lt-buzztrax-edit:6264): GStreamer-WARNING **: pad '':sink_2 pushing
>>>>> segment event in wrong direction
>>>>>
>>>>> Now I am a bit confused:
>>>>> 1.) how come we store these events on the sticky list of the src-pad?
>>>>> How would one use gst_pad_push_event() to sent them there in the first
>>>>> place?
>>>> Now after some chat on irc, I learned that we actually don't have any
>>>> upstream stick events right now. Still these are stored on the pad, a
>> bug?
>>>
>>> They are stored on all pads through which they travel, that's intended.
>> If that is the case wouldn't the code in tee that does
>> gst_pad_sticky_events_foreach (tee->sinkpad, forward_sticky_events,
srcpad);
>>
>> where forward_sticky_events() is basically
>> gst_pad_push_event (srcpad, gst_event_ref (*event));
>> break as soon as we introduce a sticky upstream event?
>
> Yes, but I currently don't even know what the meaning and behaviour of
> upstream sticky events would be :)
>
Yes, thats a good question. I'd like to have a seek with with
automatically updated play-back pos :)

Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMU3AsACgkQITDA+qr9gcwskwCgmms23TpswhoGYKi6KNflvcl0
UtwAnRZRuyAO5hvAslr9nzl3uPFICcPG
=UX+V
-----END PGP SIGNATURE-----



More information about the gstreamer-devel mailing list