Warping frustration
Posted: Sat Oct 23, 2010 8:27 am
Folks- i *think* I am doing the same thign everythig I try to warp, but am getting an intermittent, but consistant error.
Using v 8.0.4, the steps I am taking to warp (really pretty constant tempo) electronic music are:
1) Load file
2) Find first downbeat, create warp marker here
3) Right click > 'set as 1.1.1'
4) Right click > 'warp from here (straight)
5) [unsure at this point if I should be changing the 'seg. BPM to a whole number if it is close to it- trying both ways, but same result {read on} but advise on tis point appreciated]
6) Listen with metronome- it is 90% of the time not perfect
7) In those 90% of times, skip through sone with metronome on and click and drag transients to move beats to main numbers on scale
Now, 50% of the time, it works fine. The other 50%, when most of the way through the track, clicking on the transients causes the scale at the top of the waveform to go wacko (back to -300,000 odd) causing the waveform to be very compressed.
At the same time, the 'Seg. BPM' is ALWAYS reset to exactly '5'.
Anyone seen this before? Is it something I am doing wrong? A bug?
Thanks,
Paul
Using v 8.0.4, the steps I am taking to warp (really pretty constant tempo) electronic music are:
1) Load file
2) Find first downbeat, create warp marker here
3) Right click > 'set as 1.1.1'
4) Right click > 'warp from here (straight)
5) [unsure at this point if I should be changing the 'seg. BPM to a whole number if it is close to it- trying both ways, but same result {read on} but advise on tis point appreciated]
6) Listen with metronome- it is 90% of the time not perfect
7) In those 90% of times, skip through sone with metronome on and click and drag transients to move beats to main numbers on scale
Now, 50% of the time, it works fine. The other 50%, when most of the way through the track, clicking on the transients causes the scale at the top of the waveform to go wacko (back to -300,000 odd) causing the waveform to be very compressed.
At the same time, the 'Seg. BPM' is ALWAYS reset to exactly '5'.
Anyone seen this before? Is it something I am doing wrong? A bug?
Thanks,
Paul