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 776606 - playbin3: Send SEEK event directly to adaptivedemux
playbin3: Send SEEK event directly to adaptivedemux
Status: RESOLVED DUPLICATE of bug 778763
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-12-30 07:24 UTC by Seungha Yang
Modified: 2017-02-17 02:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
playbin3: Store pointer of adaptivedemux element (4.21 KB, patch)
2016-12-30 07:28 UTC, Seungha Yang
none Details | Review
playbin3: Send SEEK event directly to adaptivedemux (1.31 KB, patch)
2016-12-30 07:28 UTC, Seungha Yang
none Details | Review
playbin3: Querying SEEKING/DURATION directly to adaptivedemux (1.27 KB, patch)
2016-12-30 07:29 UTC, Seungha Yang
none Details | Review

Description Seungha Yang 2016-12-30 07:24:38 UTC
Similar to how decodebin2 is doing, send SEEK event directly to adaptivedemux.
Comment 1 Seungha Yang 2016-12-30 07:28:22 UTC
Created attachment 342603 [details] [review]
playbin3: Store pointer of adaptivedemux element

To allow sending event and querying directly to adaptivedemux element
Comment 2 Seungha Yang 2016-12-30 07:28:54 UTC
Created attachment 342604 [details] [review]
playbin3: Send SEEK event directly to adaptivedemux

Since reconfiguration of pipeline can easily happen with adaptive streaming
demuxer, send SEEK event directly to adaptivedemux
Comment 3 Seungha Yang 2016-12-30 07:29:25 UTC
Created attachment 342605 [details] [review]
playbin3: Querying SEEKING/DURATION directly to adaptivedemux

Similar to SEEK event, querying SEEKING/DURATION directly to adaptivedemux
Comment 4 Edward Hervey 2017-01-31 16:07:28 UTC
One of the main goals of pb3/db3 was to not have to do such workarounds since everything should be connected/linked (as opposed to the previous case of db2 where we had hanging/pending groups).

Do you have an example log and use-case where you need this ?
Comment 5 Seungha Yang 2017-02-16 14:44:43 UTC
(In reply to Edward Hervey from comment #4)
> One of the main goals of pb3/db3 was to not have to do such workarounds
> since everything should be connected/linked (as opposed to the previous case
> of db2 where we had hanging/pending groups).
> 
> Do you have an example log and use-case where you need this ?

Please close this bug. I'd like to solve seeking issue on bug #778763
Comment 6 Nicolas Dufresne (ndufresne) 2017-02-17 02:16:32 UTC

*** This bug has been marked as a duplicate of bug 778763 ***