Andy, Nice. If I understand it, these are runtime optimizations, for given/preferred input artwork.
How hard would it be / what would be involved it be to have an offline program that would * 1: identify / flag non optimal artwork (e.g. sbs would use this file, but its a) not a jpeg, b ) progressive , c ) non square - tell user "you might want to look at/investigate this" * 2: possibly normalize artwork (e.g. make backup of identified file, then convert it to a square , non progressive jpeg, called cover.jpg ?) Then you could run this utility offline once, and end up with the "best" / normalized artwork for sbs? Album artwork is more available on the net these days, and assumptions we made when making our libraries may no longer hold true with the advent of newer clients (smart phones, ipads etc) What are the best practices for artwork? There are probably opportunities for other plugin / app authors to * display other artwork - from an artwork folder - not just the cover * identify bigger (better?) artwork than you currently have (or is missing) Would you like to upgrade / replace (after previewing + confirmation). Just some thoughts. I always thought it was just about the music, but it seems people like the visuals as well :) -- Grahame ------------------------------------------------------------------------ Grahame's Profile: http://forums.slimdevices.com/member.php?userid=1200 View this thread: http://forums.slimdevices.com/showthread.php?t=82087 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
