Bugzilla – Bug 4105
clearing all current playlists and stopping playback when initiating a clear/rescan is REALLY ANNOYING
Last modified: 2015-02-11 12:50:41 UTC
trivial. but a pretty annoying usability issue.
elaborated the title.
http://forums.slimdevices.com/showthread.php?t=25676
Dan: is there anything that can be done about this?
Do you want database integrity? Or would you rather have a bunch of "Can't open song for ..." pop up on the screen?
Subject: Re: clearing all current playlists and stopping playback when initiating a clear/rescan is REALLY ANNOYING On Sep 17, 2006, at 9:33 AM, Slim Devices Bugzilla wrote: > Do you want database integrity? Or would you rather have a bunch of > "Can't open > song for ..." pop up on the screen? Shenanigans! Those aren't the only choices. For example, you could take the playlist state, turn it into a list of URLs, delete the database, then scan those lists first.
This came up on the forums yesterday... http://forums.slimdevices.com/showthread.php?t=27909
We would need more than the URLs.. we would need all the data for those tracks, as the user may choose to go into the TrackInfo listing for an item, move up and down the playlist. No to mention any 'title format' choices the user may have selected, which all go through the database. This is relevant for both the web & player UI.
Subject: Re: clearing all current playlists and stopping playback when initiating a clear/rescan is REALLY ANNOYING Ok. Then my modest proposal is that the proper fix is to move the ability to do a wipe and rescan to a double-secret setup page and make the db and scanning process robust enough that we don't need a wipe and rescan. Ever.
I just ran across a bug that seems related to this one: Had an album in the playlist of a player that was turned off. Did a full wipe & rescan (./scanner.pl --wipe --rescan --progress) Later, hit play to continue the playlist. Playback started at track 1 (instead of track 4 or so where it left off), and all the track metadata was wrong, since the artist/album/genre IDs had been changed. I noticed the behavior mentioned in this bug where the playlist is cleared only happens if you use the "Clear library and rescan everything" option in the web UI. The fix for both these issues would seem to be that after a wipe has finished, deflate all playlists into lists of URLs, then inflate them all back again from the database getting the new IDs in the process.
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.
This bug was closed by mistake it looks like.
Moving 7.4 bugs to 8.0.
Change the currently playing playlist to use tmp:// protocol handler for local tracks. Continue playback using those volatile track objects during the scan.