this is what happened;
when the jogwheel is assigned to scratch on with interaction mode to
- hold: spinning the jogwheel forward locks the track into a 'forward spin' (sounds like spinning the wheel forward with cd-dj jog), and countering this will lock it into a 'backward spin'.
- toggle: as you can imagine, spinning the jogwheel in either direction will constantly toggle the scratch (on off on off...), however letting go of the wheel when the scratch turns off (this is by chance of course ) will resume the track from a scratch (had me entertained for a few minutes).
- direct: same effect as hold.
the sensitivity and acceleration do not noticeably change these actions.
i've tried searching the n.i. forums, and so far, nothing (partly due to the fact that so many posts include the word 'scratch'). it seems like this would have occured to many, many users who have tried to customise their mappings, but how did this slip under the table?
any other ideas? i'm not exactly desperate for an answer (don't use scratch), but this one is slowly getting to me.
i completely agree with you. the factory mapping for this controller was barely working (the scratch on button hadn't even been assigned) as well, so i built my own mapping from the ground up. custom mappings is definately the way forward!
thanks for your inputs so far, i hope this issue gets resolved for everyone soon.
Bookmarks