Bugzilla – Bug 6521
SqueezeCenter transcoded PNGs and JPGs (from BMP) not compatible with iPhone
Last modified: 2008-12-18 11:12:53 UTC
How is the server handling transcoding? If you've got cover art in the ID3 tag stored as Windows ".bmp" file, the transcoded .jpg or .png files (both types) cannot be read on mobile safari on an iPhone (you get an unknown filetype error). Since it works well on a PC I imagine it could have something to do with byte-ordering or so... Don't know how this works on a MAC. Server OS can be Linux or Windows, both show the issue.
Created attachment 2598 [details] MP3 with ID3 including cover art in BMP format
Andy will take a look, as he has an iPhone.
OK the problem is GD cannot handle BMP files, so the files are actually served as raw BMP but with a content-type of image/jpg and the extension cover.jpg. I fixed this so at least the right image/bmp content-type is returned. However, Mobile Safari does not even support rendering BMP files: http://www.alistapart.com/articles/putyourcontentinmypocketpart2 You should store cover art in PNG for best results.
Thanks for fixing this. Is my understanding correct, that SC will now deliver the default "cover.png" or "cover.jpg" if I request a ".png" or ".jpg" file? I am aware I should use PNGs (and I do so), yet I don't have any influence on what other users do. But Showing the default cover is better than an "invalid filetype" icon.
No it will still try to deliver the huge bmp file but it will just use the proper image/bmp content type (although the URL is still cover.jpg). Since this works on most browsers we don't want to show the default cover image in this case.
Note that the real bug is that GD doesn't support BMP, this may be possible to fix but it's very low priority as only a very small minority of people are using BMP files.
This bug is being closed since it was resolved for a version which is now released! Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html If you are still seeing this bug, please re-open it and we will consider it for a future release.