Maybe we could invent something like a "Database cleanup" routine (in addition to the "new & changed") - I saw something like this in Media Monkey.
What would such a clean up do which the regular scan shouldn't already be doing?... I think we have to clearly identify the open issues we have. Some of them already are on Github (eg. https://github.com/Logitech/slimserver/issues/547). Can we compile a complete list, with easy descriptions to reproduce the issue?
Once we have a good understanding of what was wrong we can look into how to fix the issues. I believe if they were easy to fix, this would have happened long before. But maybe we could indeed simply add a purely database based cleanup step, eg. figure out orphaned entries etc.
There are a few more "bugs" (e.g. the "Windows bug" (I know, it is caused by windows and not by LMS, but it's frustrating) of being not case sensitive (e.g. If You correct a file name from "...beatles..." to "...Beatles..." You have TWO entries in Your database, pointing to the same file (one with small letter, one with capital letter)...
Could probably be tweaked to behave better, too. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
