Re: [slim] Re: server database is case sensitive and that's bad. read why.
CeeJay's right in spirit, but separate linked databases scare me as a great source of problems. A single database extended on demand with an externally described schema can be done, but it's not particularly easy. Hence our current state. I'd like to see a persistent database with support for useful information like ratings, and a separate database from the tags might be the right way to get that. Seems the LazySearch and other plugins could really benefit from a persistent database, and the performance gains from more infrequent scanning are hard to argue with. -- I spent all me tin with the ladies drinking gin,So across the Western ocean I must wander -- traditional ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
Re: [slim] Re: server database is case sensitive and that's bad. read why.
On 5/25/06, Mark Lanctot [EMAIL PROTECTED] wrote: Going back to the original subject of this thread regardingcapitalization, I do have a problem with SlimServer ignoring what I so-purposefully put in the tags.I'm trying to maintain album and track names as faithfully as possibleto how they are listed on the album itself, and this includes thoseoften-annoying stylistic capitalizations (or lack thereof) that various artists go through.Personally I find it rather silly, but the artistsdidn't put it on there by chance, it was for a definite reason.Therefore for the sake of accuracy I have tried to preserve theseaffectations in tags. See here:http://forums.slimdevices.com/showpost.php?p=107576postcount=15Myproblem is that SlimServer is doing exactly what the OP wishes it to do - it is case -insensitive- in my case, listing tracks and albums thatshould be attributable to The Smashing Pumpkins with smashingpumpkins.I wish it wouldn't!This is not accurate. I have never seen it do that, unless there was a difference between v1 and v2 tags. I've been deletng v1 tags and forcing v2 tags, then forcing a full rescan.-- I spent all me tin with the ladies drinking gin, So across the Western ocean I must wander -- traditional ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
Re: [slim] Re: server database is case sensitive and that's bad. read why.
On 5/24/06, JSonnabend wrote: Perhaps a better solution would be to stop SlimServer from messing with DB entries once they've been populated. That way, anyone could write an external app to populate the db without worrying about tags, sorting algorithms, etc. As it stands now, SlimServer updates DB entries whenever it plays a track. There was a thread on this earlier. This viewpoint comes up every now and then, and gets hotly contested. I agree that the database would be more useful if it was 'persistent', i.e. didn't rely on wipe/rescan to fix minor problems. BUT, that said, I think it is worth treating the DB as more of an index to your tags. The tags are the actual data that means something; the database is just an optimised way of indexing those tags to make searching faster. If the index gets corrupt, say, that implies the need for an index rebuild (wipe/rescan). Personally, I think that any extra data (e.g. ratings) should be stored in the file as custom tags, since that's as persistent as it gets, and generically indexed in a similar fashion to the standard tags in the DB; but I don't have to synch my music to limited-function portable players, so have no clue whether having non-standard tags would create problems. Cheers, Geoff ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
Re: [slim] Re: server database is case sensitive and that's bad. read why.
On 5/24/06, JSonnabend [EMAIL PROTECTED] wrote: @geoffb: I disagree that the tags are the actual data. I keep my actual data in an Access DB (I use CATraxx). A real DB is more efficient than file-to-file tags, whose real purpose is to allow players to extract data about tracks they're playing. Presumably you remove tags from your files, so the data is only in one place, and store the path/filename in the DB? And make efforts to not move files after they've been DB-tagged? If you want to use the files on another system (like a portable player), what do you do? I agree in principle; but until iAccess is released for the iPod for iAverageJoe, I suspect your implementation will be in the minority :) Cheers, Geoff ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
Re: [slim] Re: server database is case sensitive and that's bad. read why.
On 5/24/06, JSonnabend [EMAIL PROTECTED] wrote:Seriously, though, instead of telling me why I'm wrong to not want to use Slim as my data management program, why not admit that users shouldbe allowed to populate the Slim DB without fear of SlimServer muckingwith the data?Because there is probably only one person who is requesting it. Even if there are five it still shouldn't be a priority for SD. Ben ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
