After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 742789 - event: element should send pending sticky events before send EOS event.
event: element should send pending sticky events before send EOS event.
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
1.4.1
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-01-12 02:02 UTC by kevin
Modified: 2018-05-06 09:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description kevin 2015-01-12 02:02:33 UTC 
We have clips which has valid media information for audio track, but haven't
any audio data, we can't get audio TAG information on playbin. Audio and video
decoder base should send pending sticky events before send EOS event. This is
another issue, should submit one ticket for it. But segment event must send
before EOS, or streamsynchrinozer can't work.

One clip has shorter audio then video. Demuxer will send audio segment and EOS when seek to only video part. Decoder should send segment event before send EOS.

How about caps event? How to handle output caps if no output before EOS?
Comment 1 kevin 2015-01-12 02:08:00 UTC 
How about caps event? How to handle decoder output caps if no output buffer before EOS?
Comment 2 Sebastian Dröge (slomo) 2015-01-12 08:42:03 UTC 
The CAPS event is not mandatory
Comment 3 kevin 2015-01-12 08:45:42 UTC 
sink element can't initialize if no caps event. audiosink can't run anymore. So I send EOS to sink in streamsynchronizer. is it right?
Comment 4 Sebastian Dröge (slomo) 2015-01-12 09:22:47 UTC 
That's a different bug, this here is only about sending pending sticky events.
Comment 5 Sebastian Dröge (slomo) 2015-02-04 10:47:58 UTC 
What should happen about this bug? Is there a simple testcase to reproduce the problem, do we know which elements are affected?
Comment 6 kevin 2015-02-04 14:42:44 UTC 
I want ensure it in audio/video decoder element. will check it later.
Comment 7 Tim-Philipp Müller 2015-05-24 13:17:35 UTC 
Kevin: did you find out more details?
Comment 8 kevin 2015-05-25 03:24:38 UTC 
I am busy on other issues. This isn't my priority currently. Do I need close it? And re-open it if I found issue after I come back to check this issue?
Comment 9 Edward Hervey 2018-05-06 09:31:53 UTC 
Closing.