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 761540 - mpegaudioparse: streaming stopped, reason error in beets with replaygain
mpegaudioparse: streaming stopped, reason error in beets with replaygain
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
1.6.0
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-02-04 10:13 UTC by wriesnikpeter
Modified: 2017-01-26 21:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Debug log, trimmed to last 1000 lines. (199.21 KB, application/octet-stream)
2017-01-26 21:23 UTC, KJ
Details

Description wriesnikpeter 2016-02-04 10:13:47 UTC
Beets (https://github.com/beetbox/beets), an id3-tagging tool written in python, offers a plugin (http://beets.readthedocs.org/en/latest/plugins/replaygain.html) which calculates replaygain using gstreamer. For some files, Gstreamer produces an error:

Error GLib.Error('GStreamer encountered a general stream error.', 'gst-stream-error-quark', 1) - 'gstbaseparse.c(3457): gst_base_parse_loop (): /GstPipeline:pipeline0/GstDecodeBin:decbin/GstMpegAudioParse:mpegaudioparse5:\nstreaming stopped, reason error' on foo.mp3

running mp3val on the file producing the error doesn't show anything. Any ideas where this might come from? A bug maybe? Gstreamer version is 1.6.0-1ubuntu1 on ubuntu 15.10 with linux 4.2.0-27-generic. I can provide additional information if required.

Thanks os far!
Comment 1 Tim-Philipp Müller 2016-02-04 10:21:40 UTC
Could you make such a file available?

If not, could you run beets like this from the command line:

$ GST_DEBUG=*:6 beets 2>dbg.log

and then reproduce the error, then xz -9 dbg.log and attach dbg.log.xz to this bug report.
Comment 2 wriesnikpeter 2016-02-04 12:12:36 UTC
For some reason, after running beets in the debug mode you suggested, it finished the replaygain command. Anyways, debug file attached. Maybe you find something fishy.
Comment 3 Sebastian Dröge (slomo) 2016-02-16 16:41:15 UTC
You forgot to attach the debug log
Comment 4 Tim-Philipp Müller 2016-11-11 19:26:25 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!
Comment 5 KJ 2017-01-26 21:22:55 UTC
Hi there,

I'm also running into this issue when using beet's gstreamer replaygain backend to calculate gain on an album. Like the original reporter, when the comment is run again it tends to error on a different file.

I re-ran the command with the additional debug flags to generate a log, however the resulting log is about 2GB in size. I have trimmed it down to the last 1000 lines and attached it to this report.

Although the original poster was attempting to calculate replaygain data on MP3 files, i'm attempting to calculate it on FLAC files and so the error is sourced from flacparse3 instead of mpegaudioparse. Other than that though, the error and the method of triggering it is identical.

Many thanks.
Comment 6 KJ 2017-01-26 21:23:23 UTC
Created attachment 344360 [details]
Debug log, trimmed to last 1000 lines.