On Mon, 2005-05-02 at 16:51 -0700, JJZolx wrote:
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.
Is it in the plans that sometime in the future this will be doable?
This is one of the major reasons behind the use of an external database, so lots of cool utilities could be written without changing any of the SlimServer code.
Part of the early design work was a long discussion about what a song (or track) is, so that the database can be built up with external data sources. For simple pop songs, using the internal tags is fine, but for classical works, there is no realistic way to keep all the important information in the file.
The "duplicate track" thread clearly shows that differing folks
have different definitions of what a duplicate track is. My personal definition is bit identical music bytes, without
tags or filenames or other stuff. But the whole idea
is to remove those theological arguments from the code that accesses the music bytes.
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.
I've not seen anything about this in the developer lists. It is a relational database accessable by SQL from nearly any language or tool (perl, php, java, etc.).
Of course, once you populate the database with lots of external metadata, you don't want a 'wipe cache' to zap it all. I'd want that button to be removed :-)
The wipe cache is a nuclear strike from orbit, which is handy now but hopefully will become less desirable in future releases. But it's going to be a while til we get there -- the Browse Music Folder issues are relevant.
-- Jack at Monkeynoodle dot Org: It's a Scientific Venture... Riding the Emergency Third Rail Power Trip since 1996! _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
