locoDog
I've just discovered the 'shift_all_cues' script, so that's a bit of pain saved (quite a bit, but it still leaves a lot of pain)
So I tried it 'shift_all_cues -0.05' which is almost accurate, but it then also shifts the down beat
So then I tried being clever, and adding some precision 'shift_all_cues -0.01 & beat_tap' but repeatedly tapping screws up the bpm.
So now I'm pondering, why did the error occur?, is it consistent?, ie frame based (because time based error doesn't compute with me) and if it is consistent, what is the required correction
So I tried it 'shift_all_cues -0.05' which is almost accurate, but it then also shifts the down beat
So then I tried being clever, and adding some precision 'shift_all_cues -0.01 & beat_tap' but repeatedly tapping screws up the bpm.
So now I'm pondering, why did the error occur?, is it consistent?, ie frame based (because time based error doesn't compute with me) and if it is consistent, what is the required correction
Posted Tue 03 Jun 14 @ 9:50 am
groovindj
I've compared the cue point info from a track in 7 to the same one in 8 and:
In VDJ 7 the cue info is <Cue Num="0" Name="Cue 1" Pos="941073" />
In VDJ 8 the cue info is <Poi Name="Cue 1" Pos="21.339524" Num="1" />
The "Pos" data is completely different. Same with various other numerical data (song length, automix points...)
In VDJ 7 the cue info is <Cue Num="0" Name="Cue 1" Pos="941073" />
In VDJ 8 the cue info is <Poi Name="Cue 1" Pos="21.339524" Num="1" />
The "Pos" data is completely different. Same with various other numerical data (song length, automix points...)
Posted Tue 03 Jun 14 @ 10:27 am
locoDog
Pos is the Sample frame that coincides with the hotcue 941073 divided 44.1K =21.33952380952381,
I'm wondering why V8 puts V7 cues slightly late.
I'm wondering why V8 puts V7 cues slightly late.
Posted Tue 03 Jun 14 @ 2:15 pm