Post
FollowRecommendation -> Use file hash/checksum for database
I noticed that if I relocate any of my audio files to a new location, that all the metadata gets lost. That includes the hot cues, the beat grid, the analysis, etc. I assume that the database uses the audio file's location as a key and since that key is being changed, the relationship to the metadata is lost.
How about adding an option to use the file's name + a file hash as a database key instead of the file's location? That way, should you move the file, all your metadata will remain intact.
Right now I have hundreds of audio files that I wish to relocate but the loss of metadata makes it a pain.
Post is closed for comments.