#4 Album Art Issue - Sony 40W4500 TV


On testing the latest CVS version and altering the album art filename array so that Folder.jpg was served rather than AlbumArtSmall.jpg, noticed that the "larger" album artwork images were not shown on my Sony TV.

It appears that the setting of dlna_pn to 'JPEG_SM' for the larger file (200x200), rather than 'JPEG_TN', is at fault. Changing 'JPEG_SM' to 'JPEG_TN' in albumart.c on line 49 and refreshing the database resolves the issue.

Whether the TV refuses album artwork set to 'JPEG_SM', or if there is some problem serving these files, I'm not sure.


  • Justin Maggard

    Justin Maggard - 2009-02-09

    Setting the DLNA Profile Name to JPEG_TN when its resolution is greater than 180x180 is a direct violation of the DLNA spec, so I can't really do that. I was considering adding code to downscale album art greater than 180x180 and saving it somewhere on the filesystem. But I always hate when apps do things like that and end up eating up hard disk space.

    Hmm... might make sense to make that optional, or perhaps do it on the fly if the source file's resolution is close to 180x180, since it probably wouldn't use too much CPU. But it's really more of feature request than a bug, so I'm going to move it to the Feature Request tracker. :)

  • Steve Hollis

    Steve Hollis - 2009-02-09

    Thanks for the response, Justin :)

    Sounds like a tricky one... I can see a lot of Sony Bravia users being drawn to miniDLNA since it's basically the only Linux based media server that talks to their TV properly. It'd be a shame if it didn't show the best available album artwork from WMP libraries.

    Again, perhaps configuration options are the way to go here, controlling how strictly miniDLNA adhers to the DLNA spec. The 'out of the box' configuration should probably be 100% compliant (which is important), but your average user will probably care much more about making it work with their hardware.

    Perhaps a --force-tiny-artwork flag or something?

    On the fly transcoding should be reasonably quick for small files, possibly cached in /tmp (or even the sqlite db?) The files would be very small (~7-8Kb) so would only eat up significant hard disk space once tens of thousands of different album artwork files have been served.

    On a personal level, I'm happy to hack the source code and make it work for me :) But that's going to be too much to ask of most users.

  • Justin Maggard

    Justin Maggard - 2009-06-18

    This is taken care of in recent releases.

  • Justin Maggard

    Justin Maggard - 2009-06-18
    • status: open --> closed

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks