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 698306 - Gapless playing using 'about-to-finish' callback fails wih HTTP-URIs
Gapless playing using 'about-to-finish' callback fails wih HTTP-URIs
Status: RESOLVED DUPLICATE of bug 698750
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
1.0.6
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-04-18 14:32 UTC by Henner Z.
Modified: 2013-05-07 10:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Program to reproduce. Find version with Makefile and test-sound on https://github.com/hzeller/gstreamer-gapless-test (3.32 KB, text/x-csrc)
2013-04-18 14:32 UTC, Henner Z.
Details

Description Henner Z. 2013-04-18 14:32:18 UTC
Created attachment 241829 [details]
Program to reproduce. Find version with Makefile and test-sound on https://github.com/hzeller/gstreamer-gapless-test

Using the 'about-to-finish' callback to set the next URI to play to get gapless playback (as documented) works fine with file-URIs, but fails with a network resource such as a HTTP-URI.

Instead of playing the resource set by the about-to-finish event, it quickly re-emits the event without even having started to play the new resource -- looping forever, racing to the next resource.

Attached, you find a simple program to reproduce the problem. For easier reproduction, a version including Makefile and test-sound can be found on https://github.com/hzeller/gstreamer-gapless-test
Comment 1 Henner Z. 2013-04-18 14:33:33 UTC
To clarify: this is using the "playbin" pipeline.
Comment 2 Tim-Philipp Müller 2013-05-07 10:41:01 UTC
The other bug has more info, so marking as dup of that.

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