Mnyb;578375 Wrote: > What beats me as an dB n00b is the fact that the dB created is not "good > enough" to be used by all optional ways to "see" the collection ? > Why not create a complete dB that has all info needed ?
That's a good question that's been asked before. First, you have to figure out how to do it, if it can be done at all. Looking at it more closely, I see three options that require a full wipe and rescan when changed: 1. Group multi-disc sets 2. Articles To Ignore When Sorting 3. Treat TPE2 MP3 tag as Album Artist As I said above, I think #1 could be accomplished without requiring rescanning. The other two settings concern how tagging data is interpreted. There are probably some ways around #2. You would have to keep the raw genre data for each track. It wouldn't take the elaborate two-phase system above, just an added column to the tracks table. Use the data to 're-genre-ize' all of the tracks if the delimiter is changed. It would be faster than running a full rescan, but you have to wonder if the effort is worth it, as people aren't likely to change this very often. Number 3 might also be possible. Instead of interpreting the TPE2 tag to mean the role 'AlbumArtist', you could always store it in the database as the role 'Band' and then construct queries to either pull just 'AlbumArtist' or else pull both roles, as dictated by the setting. I think the current approach is just the easier path - if it's done at scan time then the query code stays relatively simple. -- JJZolx ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=82096 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
