Quote:
Is there some piece of this data you're particularly interested in preserving?


No, I'm trying to figure out whether it's worth to save data at all.

The problem with using mp3tofid and rsync is that there is no guarantee that anything in the dynamic database tied to a fid will remain tied to the same fid. So even if we could save something, it will be very hard to move the dynamic data to a different position if a tune has its fid number changed.

When I started developing mp3tofid, tunes would almost never change their fid number. I tag all my tunes myself, and at that time they were id3v1 only. fid numbers were tied to inode numbers, and they wouldn't change if a tag was updated. But nowadays, almost every tag tool creates a new file, unlinks the old one and renames the new file to the old one. This is how libid3 works, sadly. The result is a changed inode number, and thus a new fid number.

Maybe I should pick a new fid number allocation strategy, like rid's instead of inode numbers. But calculating rid's every time is a lot slower than just stat'ing.

Pim


Edited by pim (23/06/2005 22:44)