djdonn
The description says:
When enabled, automatically detected bpm and beat-grid will not be updated when the bpm analyzer has been updated. Only manual re-scan will then update the bpm and phase with the new analyzer. Options are Yes and No.
I'm not quite sure what that means. For example, when I initially analyze a track, I'll then set the 1st beat of the track by clicking the 'Tap" button on the skin. If I go back and re-analyze the track (for whatever reason), regardless of the setting, the first beat will change back to the original analysis. I would expect that, if it's set to either yes or no, whenever I re-analyze, the first beat shouldn't change after I initially set it, but that's not the case with either setting.
What does the "yes' setting do, and what does the "no" setting do? What is it affecting?
Thanks.
When enabled, automatically detected bpm and beat-grid will not be updated when the bpm analyzer has been updated. Only manual re-scan will then update the bpm and phase with the new analyzer. Options are Yes and No.
I'm not quite sure what that means. For example, when I initially analyze a track, I'll then set the 1st beat of the track by clicking the 'Tap" button on the skin. If I go back and re-analyze the track (for whatever reason), regardless of the setting, the first beat will change back to the original analysis. I would expect that, if it's set to either yes or no, whenever I re-analyze, the first beat shouldn't change after I initially set it, but that's not the case with either setting.
What does the "yes' setting do, and what does the "no" setting do? What is it affecting?
Thanks.
geposted yesterday @ 6:44 pm
locoDog
Setting applies to bpmEngine updates.
setting no means when engine is updated and it sees a track scanned on old engine it will rescan like it's a new track [cue and poi will still remain]
setting yes means when it sees a track scanned by old engine it will only change a database flag saying "I've scanned by new engine", but really nothing changes.
Manually choosing to rescan bypasses this and it scans with the newest engine right now as if it was a new track.
setting no means when engine is updated and it sees a track scanned on old engine it will rescan like it's a new track [cue and poi will still remain]
setting yes means when it sees a track scanned by old engine it will only change a database flag saying "I've scanned by new engine", but really nothing changes.
Manually choosing to rescan bypasses this and it scans with the newest engine right now as if it was a new track.
geposted yesterday @ 7:00 pm
djdonn
locoDog wrote :
Setting applies to bpmEngine updates.
setting no means when engine is updated and it sees a track scanned on old engine it will rescan like it's a new track [cue and poi will still remain]
setting yes means when it sees a track scanned by old engine it will only change a database flag saying "I've scanned by new engine", but really nothing changes.
Manually choosing to rescan bypasses this and it scans with the newest engine right now as if it was a new track.
setting no means when engine is updated and it sees a track scanned on old engine it will rescan like it's a new track [cue and poi will still remain]
setting yes means when it sees a track scanned by old engine it will only change a database flag saying "I've scanned by new engine", but really nothing changes.
Manually choosing to rescan bypasses this and it scans with the newest engine right now as if it was a new track.
OK, makes sense. So, I'm assuming there's no way to preserve the beat grid settings and first beat settings when a track is scanned/re-scanned?
Also, is there a way to tell if a track has been rescanned with a bpm engine update?
geposted yesterday @ 7:04 pm
locoDog
No on all cases, scan version isn't accessible from get_browsed_song.
With rescan all bets are off, honestly it's not something I see that needs to be done that often.
My setting is yes, anything that is off I manually correct, rescan is something I use if I've made several mistakes and by that point first beat has a hotcue so it's not a big deal.
With rescan all bets are off, honestly it's not something I see that needs to be done that often.
My setting is yes, anything that is off I manually correct, rescan is something I use if I've made several mistakes and by that point first beat has a hotcue so it's not a big deal.
geposted yesterday @ 8:04 pm