Bug 17629 - Some Vorbis files with large comments still crash player
: Some Vorbis files with large comments still crash player
Status: NEW
Product: SB 2/3
Classification: Unclassified
Component: Audio
: 137
: PC Other
: -- normal with 4 votes (vote)
: 7.7.x
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-04 06:49 UTC by Andy Grundman
Modified: 2014-01-04 12:44 UTC (History)
1 user (show)

See Also:
Category: Bug


Attachments
vorbis file with albumart that plays fine (12.68 MB, application/octet-stream)
2014-01-03 15:33 UTC, Dominique Cote
Details
File with album art tagged with foobar 1.1.7 - WORKS (15.07 MB, application/octet-stream)
2014-01-04 10:31 UTC, Dominique Cote
Details
File with album art tagged with foobar 1.2.9 - BROKEN (15.07 MB, application/octet-stream)
2014-01-04 11:33 UTC, Dominique Cote
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Grundman 2011-10-04 06:49:56 UTC
http://forums.slimdevices.com/showpost.php?p=660502&postcount=92

Test file: 01 - Hold On to Love.ogg
Comment 1 Dominique Cote 2014-01-03 15:33:18 UTC
Created attachment 7706 [details]
vorbis file with albumart that plays fine
Comment 2 Dominique Cote 2014-01-03 15:36:42 UTC
i'd like to add a vorbis file with album art that plays fine.
I run LMS 7.8.0 - 1387542508 @ Sat Dec 28 19:20:00 PST 2013.

while I grudgingly acknowledge that the chances of getting this bug fixed are slim to none (given the squeezebox roadmap), maybe someone could point out what is different between the two files, so we can perhaps find a work-around when tagging our vorbis files?

thanks in advance,
dominique
Comment 3 sk-public 2014-01-04 05:33:04 UTC
I noticed the problem (ogg file with artwork leads to "Ran out of decoder data memory" error) most often on the Boom, which AFAIR had particularly little memory to spare.  However on at least one occasion I got the same error on my SB3.  My workaround was to use vorbiscomment in custom-convert.conf to remove metadata from all ogg files destined for my ip3k devices:

ogg ogg * 00:04:20:01:02:03
    # F
    [vorbiscomment] -w $FILE$ -

Track information displays anyway. I think it breaks synchronization due to the inability to specify start time -- I remember considering piping the ogg file through sox with start and resample parameters before sending it to vorbiscomment.

I wouldn't hold my breath for a fix. The assigned developer's final 2011 comment was: "I advise you to remove cover art from Vorbis files. Use cover.jpg files instead." http://forums.slimdevices.com/showthread.php?89198-Do-you-have-7-6-problems-PLEASE-READ-THIS/page10. He was unfortunately canned by Logitech when they shut down the line.
Comment 4 Dominique Cote 2014-01-04 10:31:42 UTC
Created attachment 7707 [details]
File with album art tagged with foobar 1.1.7 - WORKS
Comment 5 Dominique Cote 2014-01-04 11:27:51 UTC
Comment on attachment 7707 [details]
File with album art tagged with foobar 1.1.7 - WORKS

The mystery deepens....

I re-tagged this file using foobar 1.1.7.

IT WORKS - but it shouldn't. same album art, same file, just used an old foobar version instead of the newest version 1.2.9.

I will try to reproduce on some other files and report back.
Comment 6 Dominique Cote 2014-01-04 11:33:05 UTC
Created attachment 7708 [details]
File with album art tagged with foobar 1.2.9 - BROKEN

This is the same file tagged with the same album art, using the newest version of foobar 1.2.9.

it will (as expected) crash my squeezeboxes.

as far as I can see it, foobar 1.1.7 somehow manages to attach album art in such a way that my squeezeboxes can play them fine.

that's as far as my diagnostic capabilities go, i'm afraid.
anyone else willing to venture ideas if and how this fact can be used to make vorbis with albumart WORK on squeezeboxes?
(other than exclusively using foobar 1.1.7 for tagging, of course ;-)
Comment 7 Dominique Cote 2014-01-04 12:44:56 UTC
BTW, I have opened a correlating thread in the foobar forum @ hydrogenaudio:
http://www.hydrogenaudio.org/forums/index.php?showtopic=104088

just in case the bug actually lies within foobar itself...