GNOME Bugzilla – Bug 162243
Muine fails to load MP3's with large ID3 tags
Last modified: 2006-09-29 15:43:37 UTC
Since EasyTag 1.99.2 was released, I've been embedding my album covers in my MP3's. These covers range from 3KB to 150KB and there may be several per file. Muine fails to load tags with larger tags. I've noticed files with small tags, around the 10KB range being loaded and files in the 40KB range failing to load. There may be a cap in the id3 reader at 16 or 32KB or another bug. The tags loaded successfully in Rhythmbox w/ GStreamer and Totem w/ Xine.
confirming. after seeing this bug i modified some of my files to reduced the embedded image sizes (from ~200KB to ~25KB) and these files now show up in muine's database.
Created attachment 46989 [details] [review] Fix for bug 162243 I was having the same problem. Fixed, now. (Please tell me if I messed up the file... this is my first patch to an OSS project.) This patch also removes some useless code under /* If we haven't found anything, try again with 8 more kB */.
Created attachment 46990 [details] [review] The fix without the mistakes The last one just shows how long it's been since I've written any C. Sorry about that. This is the one that should be commited.
Created attachment 47365 [details] [review] Same patch, but universal diff (-u) and applied to main dir Same patch, but this should be easier to apply.
Created attachment 47756 [details] [review] Possible different solution Does this solve the problem ?
It solves the problem for me applied against the current CVS. I haven't tested it with really large embedded images though, just ones that are failing with the current Muine release (0.8.3).
Jorn's patch works for me against CVS. I've tested it with two albums and a file with a 1 MB cover image.
Ok, I've just commited this to CVS. Am going to do another pre-release and hopefully get more testing on this that way before this hits in a real release. Marking this FIXED, will re-open if this still doesn't fix the issue for everyone.
*** Bug 138968 has been marked as a duplicate of this bug. ***