GNOME Bugzilla – Bug 784851
Internal Data Stream Error when trying to play certain ogg vorbis files
Last modified: 2018-11-03 11:57:54 UTC
I am using Ubuntu 17.04 and the default gstreamer version from the ubuntu 17.04 repo. I can not play some of my ogg vorbis files. Some of them have worked before but do not work now after setting tags with EasyTAG (I set the album cover and track-/album-title). I get an "internal data stream error" on Rhythmbox, Lollypop and Clementine. I can play these files with ffplay. Sadly, I can not upload an example file because of the file size limit. They are all encoded in 256kbit/s, so they are too big. Also, copyright could be an issue. Output of "gst-play-1.0 01\ Hells\ Bells.ogg": Geben Sie »k« ein, um die Liste der Tastenkombinationen zu sehen. Momentan wird /home/ahahn94/Musik/AC-DC/Back In Black/01 Hells Bells.ogg wiedergegeben ERROR Internal data stream error. for file:///home/ahahn94/Musik/AC-DC/Back%20In%20Black/01%20Hells%20Bells.ogg ERROR debug information: gstoggdemux.c(4851): gst_ogg_demux_loop (): /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0/GstOggDemux:oggdemux0: streaming stopped, reason error (-5) Das Ende der Wiedergabeliste wurde erreicht. I hope you can help me fix this problem. Greetings from Germany.
Dear ahahn94, It seems I have the same kind of issue on Debian 9 based today on gst-plugins-base 1.10.4. Having a look at easytags issues I found this: https://bugzilla.gnome.org/show_bug.cgi?id=776110 And actually verifying with the ogginfo command... $ ogginfo "/path/to/01 - Fly Shadow Fly.ogg" on one buggy ogg file displays... ... Negative or zero granulepos (-268) on Vorbis stream outside of headers. This file was created by a buggy encoder Vorbis stream 1: Total data length: 6516309 bytes Playback length: 5m:17.613s Average bitrate: 164.131875 kb/s Logical stream 1 ended So from my understanding it could rather be an easytag issue. Keep care of your original untagged ogg files. Hope this helps Thierry
It's probably enough to just attach the beginning of the .ogg file, created with e.g. $ head --bytes=250k foo.ogg > start.ogg
ping?
Not sure it is the same issue as ahahn94, however as mentioned in comment1: ## rip a CD audio to ogg, file is OK ## use easytag 2.4.3 on debian 9 and add a large image ## then $ ogginfo foo.ogg Processing file "foo.ogg"... New logical stream (#1, serial: 160cea6b): type vorbis Vorbis headers parsed for stream 1, information follows... Version: 0 Negative or zero granulepos (0) on Vorbis stream outside of headers. This file was created by a buggy encoder Negative or zero granulepos (-268) on Vorbis stream outside of headers. This file was created by a buggy encoder Vorbis stream 1: Total data length: 5328006 bytes Playback length: 3m:30.133s Average bitrate: 202.842868 kb/s Logical stream 1 ended $ head --bytes=250k foo.ogg > start.ogg ## file start.ogg added as attachment
Created attachment 367219 [details] first 250k of an ogg file failing to play
Hi. First of all, sorry for not replying. I have been (and still am) rather busy the last months and failed to notice the replies to the bug report. I can not contribute any new details to this, as I a) have switched from Ubuntu to Solus only a few weeks after opening this bug report and I b) have reorganized my music library into mp3 and deleted the ogg files. I could not reproduce this bug under solus. "01 - Hells Bells.ogg", which previously always showed this bug, still works after being modified by easytag 2.4.3... Greetings
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/366.