Are you sure you understand the table relationships in the database? The 'contributors' table is just a collection of names with name, name_sort & name_search fields. There's nothing in the contributors table that identifies a contributor as a track-artist, album-artist, conductor, etc. That is found in other tables. So ArtistSort and AlbumArtistSort tags aren't being overwritten. Rather, contributors.name_sort records are being overwritten.
The 'contributor_track' table links a tracks table record with a contributors record and further contains a 'role' field that defines the role of the contributor to the track. The currently defined roles are: Role Name 1 Artist 2 Composer 3 Conductor 4 Band 5 Album Artist 6 Track Artist So, please understand that a single contributor record can be "pointed to" under a variety of roles: album artist, track artist, composer, conductor, etc. If you are ending up with multiple records in the contributors table for what ought to be the same person, that's generally understood amongst the LMS developers that there's a problem with your tags, rather than a problem with the scanner. If you truly believe that you've found a bug in the scanner, isolate two audio files that, when scanned, produce two records in the contributors table. Then use a command-line tag dumping tool to report out the contents of the tags in the audio files. That should be enough information to then file a bug report on bugzilla. (..and please forgive me if I've misunderstood what you're trying to get at here..) ------------------------------------------------------------------------ gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115 View this thread: http://forums.slimdevices.com/showthread.php?t=103454 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
