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 634598 - playsink: Add a property to forward seek events to all pads
playsink: Add a property to forward seek events to all pads
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
unspecified
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-11-11 16:10 UTC by Edward Hervey
Modified: 2011-05-09 10:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
playsink: Add a property to forward seek events to all pads (3.33 KB, patch)
2010-11-11 16:10 UTC, Edward Hervey 		none Details | Review

Description Edward Hervey 2010-11-11 16:10:01 UTC 
When using playsink with un-related incoming streams (like for example two
gnlcompositions), we need to make sure the seek events are forwarded to
all incoming streams (as opposed to just one)
Comment 1 Edward Hervey 2010-11-11 16:10:03 UTC 
Created attachment 174260 [details] [review]
playsink: Add a property to forward seek events to all pads

In the case where we use playsink with un-related incoming streams
(like two gnlcompositions), the seek events need to be forwarded
to all incoming streams.
Comment 2 Sebastian Dröge (slomo) 2010-12-12 23:01:48 UTC 
I remember adding something to playbin2 for this too already for external subtitle files. I'm not sure if the property in playsink is the correct way to do it though, it might be better to handle this in the application/element using playsink because only there you know which streams belong together and which streams should get the seek event.
Comment 3 Sebastian Dröge (slomo) 2011-05-09 09:38:23 UTC 
Is this still needed? Do you agree with my comment? ;)
Comment 4 Edward Hervey 2011-05-09 10:36:01 UTC 
I circumvented the issue by directly handling playsink in the GESTimelinePipeline as you mentionned. Sorry for the delay in replying :)