(1) Even though I had previously run a new full scan since the change to DST here in the US, all my files were seen as changed.
Oh... I only tested this change with the upcoming change over here in mind... a "new & changed" scan would now check whether DST has changed since the last scan. But as the flag for the last scan is only set in a new build, it would be empty (considered "false" -> no DST during last scan). I'm sorry about that. Hopefully this was the last DST change causing this kind of problem.
[15-03-19 07:03:22.7626] main::main (337) Error: Failed when running main scan: [Can't locate object method "parseList" via package "Slim::Formats::Playlists" (perhaps you forgot to load "Slim::Formats::Playlists"?) at
Thanks, fixed in the next build.
I emptied my playlists folder and tried another "new and changed" scan to see if it would complete. This time, about 15K of my 36K files identified as new. It completed properly. I immediately ran again - about 9K files identified as new this time - completed properly. I ran a third time - about 4K files identified as new this time - completed properly. I decided to stop that fun at this point!
That's a long standing bug which is (almost) only exposed when the DST issue hits the "new & changed" scan. Whenever there are more than X changed items (I don't remember the exact value of X), the scanner would expose this odd behaviour. Unfortunately I haven't found a fix yet. But as this rarely ever happens (the only reports I can remember are all related to the DST change), I stopped investigating.
Please update to tomorrow's build and run a full wipe & rescan. That should fix both issues.
-- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
