djdonn
Here's my situation. I want to replace some tracks that are currently mp3 with the same tracks, but in flac format. The issue is, when I replace the tracks and analyze and batch reload tags, it seems VDJ keeps the track history, but displays the old, mp3 bit rate.
So, what I'm doing is, deleting the track OUTSIDE of VDJ (NOT deleting through VDJ), then load the old mp3 track which I get an error (expected), then right clicking on the old mp3 track and clicking 'relocate missing file'. It re-adds the track with all the correct id3 tag info but after I re-analyze, it still shows the old mp3 bit rate.
If I delete the tracks first which also deletes the history, upon adding to database and analyzing, the bit rate will be correct.
I want to retain the history and have the new bit rate displayed correctly. Short of going into the xml database and editing manually, how can I get VDJ to display the new, flac bitrate while retaining the old history?
So, what I'm doing is, deleting the track OUTSIDE of VDJ (NOT deleting through VDJ), then load the old mp3 track which I get an error (expected), then right clicking on the old mp3 track and clicking 'relocate missing file'. It re-adds the track with all the correct id3 tag info but after I re-analyze, it still shows the old mp3 bit rate.
If I delete the tracks first which also deletes the history, upon adding to database and analyzing, the bit rate will be correct.
I want to retain the history and have the new bit rate displayed correctly. Short of going into the xml database and editing manually, how can I get VDJ to display the new, flac bitrate while retaining the old history?
Posted yesterday @ 10:31 pm
jeromeip
I've been able to reproduce this, more or less, with two mp3 with different bitrates.
Analyse for BPM etc. keeps the bitrate "unknown".
(Well, this results from manipulation outside VDJ, so it's not that surprising that something buggy happens, yet there should be a way to have a full proper reanalyze of the track.)
Analyse for BPM etc. keeps the bitrate "unknown".
(Well, this results from manipulation outside VDJ, so it's not that surprising that something buggy happens, yet there should be a way to have a full proper reanalyze of the track.)
Posted 4 hours ago