Bugzilla – Bug 10701
Playlist RIGHT from "Now Playing" not shown/cover art missing
Last modified: 2009-10-05 14:30:07 UTC
Using SC7.3.2-24638/Windows (and previous 7.3.2 versions) and SqueezePlay/Win from the nightlies, when pressing RIGHT from the "Now Playing" screen, the playlist is either shown as only rotating "loading" icons or without cover art (the "note" icon is shown instead). SP from 2009-01-12 nightly showed the rotating "loading" icons forever (15 minutes until I gave up). This seems to have improved by the transition from SC7.3.2-24623/SP 2009-01-12 to SC7.3.2-24638/SP 2009-01-14: Now it shows a playlist, but all (existing!) cover art is instead shown as the "note" cover icon. Sometimes the cover art for the current song is shown in "Now playing", more often not. (ALL cover art I use is only ONE image 160x160px, 72dpi, JPEG, embedded in the files' tags, APIC Type 3 (Front Cover) for MP3.) The cover art is shown in the WebUI.
Seems more or less random: I just restarted SP, and the covers were shown again. (Without doing anything else in between. COULD that be a memory problem?)
This appears to be an artwork redering issue, the more you have in the playlist, the longer it takes to render the artwork. with 1 item in the playlist, it's very fast with 100 items in the playlist, it's very slow with 1000 it takes about 5 minuts
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
this is fixed in current 7.4
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.