>I don't see why one should assume that <blank>=first disc, since it could just >as easily be from the last disc, or disc 3/5. > That's what I was getting at really. It can't tell what disk it should be associated with, and may have even intentionally been left blank.
eg. hypothetically, there could be an option to buy a live album from Play.com, comprising of 2 CDs, and get a bonus song for download, to promote a download service. That song could be tagged with the same album name, but it doesn't belong to disk 1 or disk 2. Some people may tag it as a single song living on disk 3, or if tags are not amended it won't have a disk number, because it was a download, not ripped from a disk. What should SbS do to decide what disk it is associated with - nothing! Leave it to the tag content. >I suppose that 1/1 could be treated as a special case, because 1/1 >implies that it's *not* a multiple disc album to begin with (assuming >that the 1/1 tag is correct). What if the disk number is set, but not total disks? I don't like special cases. I think disk 1/1 is rather naff, and has no place in a music library. In fact, I don't use disk tags at all now; I change all tracks to be contiguous across the album as a whole. I know some rippers like to set disk 1 of 1, but it's a little bit mad. _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
