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 722769 - about-to-finish signal being fired twice for the same play of the same track for OGG files
about-to-finish signal being fired twice for the same play of the same track ...
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
1.2.2
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-01-22 14:08 UTC by Andrés G. Aragoneses (IRC: knocte)
Modified: 2018-05-05 16:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andrés G. Aragoneses (IRC: knocte) 2014-01-22 14:08:25 UTC
Tracked down an issue in banshee whose culprit is this: about-to-finish signal being fired twice for the same play of the same track, at the end of the song.

For now I have only tested gstreamer 0.10 and 1.0.6 with OGG files.

I will test in a little bit with 1.2.2 and other formats.
Comment 1 Tim-Philipp Müller 2014-01-22 14:29:53 UTC
Please test with recent stable branch, but could you also check if the ogg files have multiple chains? (oggz-info should show you).

You can test with:

 gst-play-1.0 --gapless file1 file2
Comment 2 Andrés G. Aragoneses (IRC: knocte) 2014-01-22 14:41:38 UTC
I have just tested with MP3s (still 1.0.6 and 0.10), and I cannot reproduce the bug, so I think this is OGG-only.

(In reply to comment #1)
> Please test with recent stable branch, but could you also check if the ogg
> files have multiple chains? (oggz-info should show you).

How can I know if they have multiple chains from the output of oggz-info? This is the output of one:

$ oggz-info panic2.ogg 
Content-Duration: 00:00:44.307

Vorbis: serialno 0000013295
	3547 packets in 148 pages, 24.0 packets/page, 1.485% Ogg overhead
	Audio-Samplerate: 44100 Hz
	Audio-Channels: 1


> You can test with:
> 
>  gst-play-1.0 --gapless file1 file2

What do I achieve with this exactly?
Comment 3 Tim-Philipp Müller 2014-01-22 14:48:08 UTC
That output means there's only one chain.

gst-play-1.0 prints some output when it gets the about-to-finish signal, so if you get it twice it should show that output twice, thus proving the bug with standard GStreamer tools :)
Comment 4 Andrés G. Aragoneses (IRC: knocte) 2014-01-22 15:04:33 UTC
Just tested this with gstreamer 1.2.2 (the one packaged in ubuntu trusty: 1.2.2-1ubuntu1) and the bug is definitely present.

If you want a particular file as a testcase, here's one:

https://github.com/GNOME/banshee/blob/master/tests/data/A_boy.ogg


(In reply to comment #3)
> gst-play-1.0 prints some output when it gets the about-to-finish signal, so if
> you get it twice it should show that output twice, thus proving the bug with
> standard GStreamer tools :)

Ok, but unfortunately doing this doesn't seem to trigger the bug, this is the output:

$ gst-play-1.0 --gapless A_boy.ogg A_girl.ogg 
Now playing /home/knocte/banshee/tests/data/A_boy.ogg
About to finish, preparing next title: /home/knocte/banshee/tests/data/A_girl.ogg
0:00:01.1 / 0:00:01.1
Reached end of play list.
Comment 5 Sebastian Dröge (slomo) 2014-05-26 12:54:37 UTC
Can you provide a debug log with GST_DEBUG=6 for that problem in Banshee? Or GST_DEBUG=decodebin*:9,play*:9

From looking at the code it seems not possible for this signal to happen twice.
Comment 6 Vivia Nikolaidou 2018-05-05 16:09:46 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!