a bit nooby question, is there a way to LOCK the "cue" button while deck is playing ? i want to make a little experiment and try djing for a while with audio 2 & kb covers keyboard only and for safety is better the cue is locked
a bit nooby question, is there a way to LOCK the "cue" button while deck is playing ? i want to make a little experiment and try djing for a while with audio 2 & kb covers keyboard only and for safety is better the cue is locked
Macbook White 2008, Behringer NOX 202, Numark TTX, Traktor Pro 2 , Traktor X1, Sennheiser HD 25-1 II
by locked you mean not working?
go into the controller manager, find the cue button mapping and delete it, then maybe map something else there that's more usuful to you
It's better for safety to map this to same button:
Add Modifier 1 / button - inc
Add Modifier 1 / ModCondition M1=1 / button - direct 0
Add cue / ModCondition M1=1
Play track with this cue button (similar to play button) and then eventually press play and disengage cue lock if needed
It's the same stuff, just other thing.
Add Modifier 1 / ModCondition M1=2 / button - direct 1
Add Modifier 1 / ModCondition M1=1 / button - direct 2
lol, battle of the modifiers
in one of my previous vci100 maps i had toggle that relied on another toggle, had sever multi-layer issues due to lack of space
thanks for the replay guys, but is there a simple way to explain it ?
Macbook White 2008, Behringer NOX 202, Numark TTX, Traktor Pro 2 , Traktor X1, Sennheiser HD 25-1 II
Good day Stewe!
Zoo here once again. I've been loving the Hotcue mapping that you helped me configure in my mixtrack pro. I've tried to make another modification, and it's the LED mapping for the Hotcues this time. I had successfully mapped it to light up when I press the Hotcue buttons, however, when I try to delete just one Hotcue button, all the Hotcue LEDs turn off. What could be the problem? Hope you could help me out once again sir.
Here's the map file for your reference..DJZoo Mixtrack Pro Mapping.tsi
Thanks in advance!
no, it was more like
[shift = m1]
[cue mode = m2]
for one button (the one to side of the scratch button on vci100);
copy deck a (m1=0/m2=0)
jump beat back (m1=1/m2=0)
play button [cue mode] (m1=0/m2=1) - transport buttons became cue points, used this as a toggle for play
beatslicer {toggle} [cue mode] (m1=1/m2=1) - used slicer as loop recorder, pre TP2 days
and then the same on the opposite side
Last edited by BradCee; 08-12-2012 at 01:46 PM. Reason: typo
|
Bookmarks