On Sat, 2005-11-05 at 18:44 -0800, Michaelwagner wrote: > I think you'd have to store such things somewhere else. The Slim > software is far too quick to clear the database. > It's one button push. Or one software failure. Too easy to lose.
I agree that the SlimServer process has to stop assuming that the database is valueless. I expect a preference can fix the server clobbering it so quickly. There are other implications that were covered long ago, things like how you tell if a songfile is the same or not. Cryptographic hashes handle this easily at a cost of more CPU for each scan. So folks with underpowered servers will not want to enable the preference. >Perhaps a second meta file in the same directory as the song file? With >your own tags that don't fit into the MP3 scheme (yet). Slim could be >taught to read those as well. No, this is a very bad idea. it is a global, serverwide collection of metadata, not something directory specific. But details belong over on dev-list. I've mentioned it here because all of the hard work has been done and many people don't seem to realize that the database is there. The schemas are in the slimserver directory tree, /usr/local/slimserver/SQL on my installation. The standard sqlite front end works well on the database. Things like proper backup, schema alterations to support new releases, etc. all will take a small amount of work. -- Pat Farrell http://www.pfarrell.com _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
