I just upgraded to 5.2. I'm glad to see that the user can now define columns/fields to display in tyhe browser. I think remember reading that all files must be re-scanned because of the new BPM engine. Is this correct?
Posté Fri 22 Aug 08 @ 1:01 pm
Columns and Fields have been there since the initial release of v5. And you can do the same in the Playlist column as well -- (a lot of people still don't realize that one!)
And you don't have to rescan your library, however; the BPM is considerably improved upon than the prior 2 BPM engine options. Also, you can just wait until you start playing the tracks and they will be scanned as you put them on the decks.
And you don't have to rescan your library, however; the BPM is considerably improved upon than the prior 2 BPM engine options. Also, you can just wait until you start playing the tracks and they will be scanned as you put them on the decks.
Posté Fri 22 Aug 08 @ 1:24 pm
Yes - but if we have an incorrect BPM (which there are many from pre 5.2) previously scanned by the old engine, and we load that track in 5.2, then it will not re-calculate the BPM, correct? It will still use the wrong number...??
Posté Tue 26 Aug 08 @ 10:11 am
From the manual ...
"If the BPM (or the Key) is manually entered using the File Info dialog, then VirtualDJ will remember this and will not analyze the BPM or Key unless forced by selecting the BPM -> Re-Analyze function. So a song analyzed by prior versions will be reanalyzed. But a song where the BPM was manually changed in prior versions will not be automatically reanalyzed. "
"If the BPM (or the Key) is manually entered using the File Info dialog, then VirtualDJ will remember this and will not analyze the BPM or Key unless forced by selecting the BPM -> Re-Analyze function. So a song analyzed by prior versions will be reanalyzed. But a song where the BPM was manually changed in prior versions will not be automatically reanalyzed. "
Posté Tue 26 Aug 08 @ 11:22 am
OK I see. Thanks.
Posté Tue 26 Aug 08 @ 11:25 am