Sign In:     

Forum: General Discussion

Topic: mapping with my numark stealth control

This topic is old and might contain outdated or incorrect information.

I need help with the following maps
LOOPMINUS - Go down one loop (so if its 4 it goes to 2)
LOOPPLUS - Go up one loop
LOOPIN - to basically click on the number button to activate the loop


thanks!
 
Posted Wed 24 Jun 09 @ 1:50 pm
Don't have a Stealth Control but I believe you will want to use the following for LOOPMINUS and LOOPPLUS:

loop_double : double the size of the loop.
loop_half : halve the size of the loop.

Link to the Wiki VDJScript Verbs

so some sample map code could look like this:

<map value="LOOPPLUS_BUTTON" action="loop_double"/>
<map value="LOOPMINUS_BUTTON" action="loop_half"/>
 
i tried that and it does its job but only changes the value when the loop is playing, im trying to move the values before the loop is activated
 
I have a question concerning mapping with my stealth as well. No need to make a new thread. I would prefer my own mapping instead of the native support included in the update...however, a big problem i've found is that VDJ now groups some buttons together. like for example if i set keylock for deck 1, its also assigned for the same button on deck 2...which is handy...until it comes down to the buttons/knobs i use for individual functions, or setting up my way.
example, i use the effects section for effects, on both decks. and the global section for the sampler. But VDJ "pairs these together. so what i assigned to a knob on the left is also for the knob on the right, but for deck 2...this is getting very irritating since im not finding a way around it.

Point is, the buttons arent single like they used to be, and its making custom mapping harder. If anybody else had this and found a way a round it, please let me know. thank you.
 
This is done for convenience because in most cases the controls on a dual-deck controller will be the same on both sides. This simplifies the mapping considerably (You don't need to map PLAY twice, CUE twice, pitch twice, etc.

You can make a mapping perform different functions for each side by using action_deck, e.g:

action_deck 1 ? sampler play_stop : effect active


This would make a button trigger a sample on the left side and effect on the right.

Of course, the action will be applied to appropriate deck based on which side it's on. You can also get around this by preceeding the action with the following:

deck 1 to apply to left deck.
deck 2 to apply to right deck.
deck active to apply to the active deck (The one playing out live.)
deck default to apply to the default deck (The one being cued up/pre-listened to.)

E.g:

action_deck 1 ? deck active sampler play_stop : deck active effect active
 
alright, i think i understand it now... action_deck 1 ? deck default effect slider 1 : deck 1 sampler volume

to me, this is a crash course in programing.
 


(Old topics and forums are automatically closed)