One thing I think the "Removing duplicate tracks" thread brings up - something I've been wondering about - is the possibility of using outside maintenance programs on the track database.
Say you had a task that was too complex or too low priority to be integrated into SlimServer itself. Removing duplicate tracks might be one such task, compiling album covers might be another. Maybe even picking up multiple artist tags in FLAC files and cataloging them. Ideally, now that the data is in a neat little RDBMS, we might develop scripts or programs to maintian the track catalog independant of SlimServer. The idea of having to muck about with the SlimServer code itself and then having the code integrated and tested within the server isn't very attractive when you could knock out a script in an hour and a few lines of your favorite language. But I realize that this isn't likely to work very well with the way SlimServer currently operates. Doing a wipe database (which I tend to do several times a week these days) will likely wipe out any changes made to the data. Is it in the plans that sometime in the future this will be doable? This was one of the reasons I was excited about SlimServer moving to the use of a database backend, but as it currently stands, about the only thing you can do in an outside app is read-only. -- JJZolx _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
