Bugzilla – Bug 540
No track scrolling in single size nowplaying screensaver
Last modified: 2011-03-16 04:40:40 UTC
2004-09-08 CVS, SLIMP3, in single size, nowplaying screensaver, the track information never scrolls when required. doublesize scrolling does work fine.
Created attachment 127 [details] Parse lines to fix. This fixes the missing parsed lines in the scrolling works, and keeps track of the proper $line1 info with overlay so that progress bar gets rendered properly.
fixed in cvs. give 'er a run and reopen if there is a problem.
Thanks Kevin, I tried out the fix. It is scrolling again but I noticed two things that have changed. One is probably related to your fix - I'm not sure of the other. First, scrollPause for the display seems to be greatly reduced from the preference setting. For the default of 3.6 seconds, scrolling begins almost instantly when the previous scrolling stops. I set this to 30 seconds as a test and it started scrolling in about 5 seconds. Second, every time I manually advance a track in the playlist with the remote, it displays my screensaver (Now Playing ... jump back on wake) instead of the next track. This one might have been caused by some other change but it is definitely new since 9 Sep or so.
The first one was likely hidden by the fact that there was no scrolling :) I'm on it. the second, I'm not following you. if you press SKIP, it shows the next track for me. If it shows the Now playing screensaver...it seems to be that would also look just like the normal now playing screen anyway. can you elaborate?
first issue: Slim/Display/VFD/Animation.pm Line 681 changes to: $pause_count + $rate); I can commit tonight if you can confirm this works for you.
I updated line 681 and everything works fine as far as I can tell. About the second issue I was seeing ... not reproduceable after I made the change and restarted the server. So it seems we're good to go - thanks!
cool. post here if it comes back or if you get more info on it. I'll mark fixed when I commit later.
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.