by sylMV on 06 May 2010, 15:27
Hi,
the low bpm is not a clue, it only means when Cross switched to flexible mode, the instantaneous bpm was that low (during a scratch movement for instance).
The question is, why Cross did switch to Flexible mode....
Theoretically, Cross automatically switches to Flexible when it detects the Browsing track, or when it reaches the "last position" before the browsing track.
So, were you scratching at the end of the groove (close to the browsing track) ?
If not, it means the signal was bad enough to make Cross decode the normal timecode as the browsing one ...
If you can find a scenario to reproduce the bug, I'll be glad to try and find if something's going wrong in Cross.
For now, I know the probability to confuse browsing and normal timecode is very low...
Check you're not scratching close to the end of the groove and your signal (timecode quality) is not too bad.
Let us know if you've got some further info !
Cheers,