To Robin B.: re-calculate: ============= Solution 1: store the computed hash in the file tags, recalculate become necessary only if the tag has been wiped Solution 2: store in a table hash and file url (file://), recalculate on "force update" or file not found/file not in db
mismatch between tracks and physical files: =========================================== If you refer to embedded cue sheet, a composite id like <file_hash><cue indice> could do the trick To Pfarell: I'm not sure sha1 vs md5 would be useful and wouldn't sha1 longer to compute? Whatever sha1, md5 or anything... anyway, what really matters is the idea of an audio data hash whatever the hash algorithm. > > This is not so much an SC issue as a software issue. It represents a > different way of looking at catalog information. And its not just SC. > Nearly all library management software assumes that tags are Truth, > and > the whole truth. > I know it's not just a SC things, I only meant that it did not look like a difficult thing, but with SC, I fear what looks simple and is not at all in reality (the message from Robin B. about embedded cue sheet is one of the difficulty to handle). > > > And as long as you respect those few constraints, XML data survive > move > > and rename actions. > > I believe, IMHO, YMMV, etc., that this assumption is too limiting. If > we > are going to do all the work to separate information about the music > from the music bits, we should break all bindings to 'album' and > 'folder' and focus on the music. > > The music should be able to be organized for > play/information/comparison > by album when applicable, but at other times you want all first > movements of a given symphony, or all music that is X movement of Y > piece played with Joshua Bell as the soloist. > This "one xml by album" is not incompatible with what you say. It's stuck to this "album" scheme right now because it's still the way music is sold (this design is just definitely not oriented toward "track/single" handling). When I say "album", you can read "group of works/songs that have are logically bound together". But I must admit that in the model there is an "album title", "releases/release/dateOfRelease" concepts :). -- vrobin ------------------------------------------------------------------------ vrobin's Profile: http://forums.slimdevices.com/member.php?userid=11705 View this thread: http://forums.slimdevices.com/showthread.php?t=43851 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
