Okay, ever since the upgrade to 6.0.3 where the key names with in VDJ changed for the Stealth Control, I have been having an issue getting my mapping to work like it did before. I am currently on 6.0.5.
Background on the issue is this. There are 4 dials and 4 buttons at the top of each deck. On the deck itself they are labeled and arranged as follows: ( ) = Knobb, { } = Buttons
(FX AMT) | (Filter AMT)
{Select} |{Filter ON/OFF}
(PAR) | (Fine Pitch)
{On/Off}|{Tap}
My desired mapping is to have the SELECT and FILTER ON/OFF buttons to map to selected effects. I then want the FX AMT, Filter AMT, PAR, and Fine Pitch to be mapped to the Effect Sliders, 1, 2, 3, & 4 (respectively), and then ON/OFF and TAP are mapped (without issue) to the Wheel Mode and Beat_Tap functions. Before I was able to specific which deck the knobs and buttons controlled, and therefore was not at the mercy of the "selected" deck.
Here are the key names that come up and my mapping syntax. It is not working as I would like and I am at a loss given I used to have this working as desired before.
These are the deck 2 mappings
ENC_SEARCH_PLAY = deck 2 effect slider 2 (Filter AMT)
ENC_SEARCH = deck 2 effect slider 3 (PAR)
ENC_FINE_PITCH = deck 2 effect slider 4 (FINE PITCH)
PREVIEW = deck 2 effect "FLANGER_TexZk" Active (Filter ON/OFF)
These are the deck 1 mappings
ENC_FX_GAIN = Deck 1 effect slider 1 (FX AMT)
ENC_FX1 = deck 1 effect slider 3 (PAR)
ENC_FX2 = deck 1 effect slider 4 (FINE PITCH)
FX_SELECT = deck 1 effect "flanger_TexZK" active (Select Button)
This key seems to be duplicated between both decks
ENC_PAN = Effect slider 1 (Filter AMT on Deck 1 and FX AMT on Deck 2)
SCRATCH = effect "ISOLATOR" active (Filter On/OFF on Deck 1 and SELECT on DECK 2)
So what you may have been able to deduce is that 1) since different keys seem to service the same control on both decks, it does not allow to perfectly mirror each deck. 2) you can not specify which deck the effect or slider should operate. In fact, even when I say deck 1 effect slider, it will still alter the deck 2 knob at the same time the deck 1 knob moves.
There are times I apply effects to a track that I am mixing out of (ie deck 1), but the PFL is on the track I am bring in in (ie deck 2). Given how the PFL works, ie takes the focus of the deck... it becomes very difficult to do this via the controller.
Is this on purpose? Am I missing something? Incorrect syntax? Interpreting it wrong? Is Tracktor causing the Stealth Control to have incorrect key names in VDJ?
Any help would be GREATLY appreciated!
Thank you!
Chad
Background on the issue is this. There are 4 dials and 4 buttons at the top of each deck. On the deck itself they are labeled and arranged as follows: ( ) = Knobb, { } = Buttons
(FX AMT) | (Filter AMT)
{Select} |{Filter ON/OFF}
(PAR) | (Fine Pitch)
{On/Off}|{Tap}
My desired mapping is to have the SELECT and FILTER ON/OFF buttons to map to selected effects. I then want the FX AMT, Filter AMT, PAR, and Fine Pitch to be mapped to the Effect Sliders, 1, 2, 3, & 4 (respectively), and then ON/OFF and TAP are mapped (without issue) to the Wheel Mode and Beat_Tap functions. Before I was able to specific which deck the knobs and buttons controlled, and therefore was not at the mercy of the "selected" deck.
Here are the key names that come up and my mapping syntax. It is not working as I would like and I am at a loss given I used to have this working as desired before.
These are the deck 2 mappings
ENC_SEARCH_PLAY = deck 2 effect slider 2 (Filter AMT)
ENC_SEARCH = deck 2 effect slider 3 (PAR)
ENC_FINE_PITCH = deck 2 effect slider 4 (FINE PITCH)
PREVIEW = deck 2 effect "FLANGER_TexZk" Active (Filter ON/OFF)
These are the deck 1 mappings
ENC_FX_GAIN = Deck 1 effect slider 1 (FX AMT)
ENC_FX1 = deck 1 effect slider 3 (PAR)
ENC_FX2 = deck 1 effect slider 4 (FINE PITCH)
FX_SELECT = deck 1 effect "flanger_TexZK" active (Select Button)
This key seems to be duplicated between both decks
ENC_PAN = Effect slider 1 (Filter AMT on Deck 1 and FX AMT on Deck 2)
SCRATCH = effect "ISOLATOR" active (Filter On/OFF on Deck 1 and SELECT on DECK 2)
So what you may have been able to deduce is that 1) since different keys seem to service the same control on both decks, it does not allow to perfectly mirror each deck. 2) you can not specify which deck the effect or slider should operate. In fact, even when I say deck 1 effect slider, it will still alter the deck 2 knob at the same time the deck 1 knob moves.
There are times I apply effects to a track that I am mixing out of (ie deck 1), but the PFL is on the track I am bring in in (ie deck 2). Given how the PFL works, ie takes the focus of the deck... it becomes very difficult to do this via the controller.
Is this on purpose? Am I missing something? Incorrect syntax? Interpreting it wrong? Is Tracktor causing the Stealth Control to have incorrect key names in VDJ?
Any help would be GREATLY appreciated!
Thank you!
Chad
发表时间 Wed 06 Jan 10 @ 11:27 pm
You can use action_deck 1 ? left_action : right_action to make a knob or button that's present on both sides of a controller perform different functions for each deck.
For further information, please see http://www.virtualdj.com/wiki/VDJScript%20Examples.html
For further information, please see http://www.virtualdj.com/wiki/VDJScript%20Examples.html
发表时间 Thu 07 Jan 10 @ 11:38 am
I will give this a try tonight. I assume this works no matter what if the button on the left or right have different or the same Key that shows up when you "auto learn."
发表时间 Thu 07 Jan 10 @ 5:42 pm
They must both be the same button, i.e: A FX button on both sides of the controller, which just shows up once in mapping list and when learning.
If the buttons are separate, e.g: Named FX on left, and SAMPLER on right in the same location, then you would need to map them separately. You can use deck active to make the action apply to the active deck, e.g: Map the FX button to deck active effect active to activate the effect on the live deck.
If the buttons are separate, e.g: Named FX on left, and SAMPLER on right in the same location, then you would need to map them separately. You can use deck active to make the action apply to the active deck, e.g: Map the FX button to deck active effect active to activate the effect on the live deck.
发表时间 Thu 07 Jan 10 @ 6:34 pm
Thank you! That helped! I scratched everything and started over. I have been testing all night. I submitted the mapper file to share with other users. I submitted one before 6.0.3, but it never made it to the TOOLS section (probably because the key names changed.) Here are the features of the mapper. Hopefully it will pass testing, which is also good validation I have done this properly.
Description:
--- Track Control ---
1. PFL – Set this deck to “cue”
2. Key – Set Key Lock for the selected Deck
3. SYNC – SYNC this deck's tempo with the opposite deck
4. PLAY/Cue/Set Cue – Set to 3 button mode for Play, Cue, Stop (respectively)
5. Pitch – Pitch Slider for the deck
6. Loop in – Smart 4 Loop
7. Loop out – Smart 8 Loop
8. Pitch Bend Minus – Loop 16
9. Pitch Bend Plus – Loop 32
10. On/Off – Changes Jog Wheel model (Search, Jog, and Vinyl)
11. Tap – Beat Tap
--- Effects ---
1. Select – Activates the “Flanger_TexZK”effect (note this effect can be replaced with another effect, just edit the mapping to be whatever effect you want inside the “ “ on the FX_SELECT and SCRATCH mapper keys)
2. Filter ON/OFF – Activates the “Isolator” effect (note this effect can be replaced with another affect, just edit the mapping to be whatever effect you want inside the “ “ on the SCRATCH and PREVIEW mapper keys)
3. FX AMT, FILTER AMT, PAR, and FINE PITCH knobs – Effect Slider 1, 2, 3, and 4 (respectively)
--- Volume Controls ---
1. Gain – Deck Gain Level
2. High, Med, Low – EQ High, Med, and Low levels
3. Press High, Med, Low – Kill High Med Low EQ
4. Master – Master Volume
5. PH MIX – Headphone Mix Control
6. PH VOL – Headphone Volume
7. Channel Faders – Deck Volume Slider Level
8. Crossfader – Crossfader Control
--- Browsing Controls ---
1. Track Dial – Browser Scroll
2. Track Dial Press – Switch between Song and Folder Levels
3. Load Track – Load selected track to the Deck
4. Directory – Changes between Browser, Sampler, Effects, and Record pages
This mapper is great if you need easy access to the smart loop functions (4, 8, 16, and 32), effect sliders and 2 specific effects, the wheel mode, and the beat tap functions. If you do not like the two effects, just change every instance where you see that effect to your desired effect name. You can also browse folders and load tracks with a touch of a button and change between the bottom half pages of VDJ.
Description:
--- Track Control ---
1. PFL – Set this deck to “cue”
2. Key – Set Key Lock for the selected Deck
3. SYNC – SYNC this deck's tempo with the opposite deck
4. PLAY/Cue/Set Cue – Set to 3 button mode for Play, Cue, Stop (respectively)
5. Pitch – Pitch Slider for the deck
6. Loop in – Smart 4 Loop
7. Loop out – Smart 8 Loop
8. Pitch Bend Minus – Loop 16
9. Pitch Bend Plus – Loop 32
10. On/Off – Changes Jog Wheel model (Search, Jog, and Vinyl)
11. Tap – Beat Tap
--- Effects ---
1. Select – Activates the “Flanger_TexZK”effect (note this effect can be replaced with another effect, just edit the mapping to be whatever effect you want inside the “ “ on the FX_SELECT and SCRATCH mapper keys)
2. Filter ON/OFF – Activates the “Isolator” effect (note this effect can be replaced with another affect, just edit the mapping to be whatever effect you want inside the “ “ on the SCRATCH and PREVIEW mapper keys)
3. FX AMT, FILTER AMT, PAR, and FINE PITCH knobs – Effect Slider 1, 2, 3, and 4 (respectively)
--- Volume Controls ---
1. Gain – Deck Gain Level
2. High, Med, Low – EQ High, Med, and Low levels
3. Press High, Med, Low – Kill High Med Low EQ
4. Master – Master Volume
5. PH MIX – Headphone Mix Control
6. PH VOL – Headphone Volume
7. Channel Faders – Deck Volume Slider Level
8. Crossfader – Crossfader Control
--- Browsing Controls ---
1. Track Dial – Browser Scroll
2. Track Dial Press – Switch between Song and Folder Levels
3. Load Track – Load selected track to the Deck
4. Directory – Changes between Browser, Sampler, Effects, and Record pages
This mapper is great if you need easy access to the smart loop functions (4, 8, 16, and 32), effect sliders and 2 specific effects, the wheel mode, and the beat tap functions. If you do not like the two effects, just change every instance where you see that effect to your desired effect name. You can also browse folders and load tracks with a touch of a button and change between the bottom half pages of VDJ.
发表时间 Thu 07 Jan 10 @ 9:20 pm
Okay, I am getting fairly disgruntled. I have been testing this new mapper all night. It was working just fine... i was applying the effects and working the slider, going back and forth between decks and mixing back and forth. It was all working so well. I copied my mapper from VDJ 6.0.5 \mapper file to the Cue 6.0.3 \mapper folder. I then went to test in Cue. I can activate the effect properly, but the slider mapping stops working when the PFL is pressed on the opposite deck you want to apply the effect.
I went back to VDJ 6.0.5 to see if it was doing it there and now it is doing it there. It was working just fine... I am fairly certain I tested applying the effect and slider control when the deck was not the "selected" deck. I am fairly frusterated as you will want to cue up your next track and perhaps even loop and layer the track for a while, meanwhile you are applying effects to the "master" track. I should not have to switch my headphone cue back to the master track JUST so i can control the effect slider.
What am I doing wrong or is this a bug? Here is the mapping from the XML
<map value="ENC_FX_GAIN" action="action_deck 1 ? effect slider 1 : effect slider 1" />
<map value="ENC_PAN" action="action_deck 1 ? effect slider 2 : effect slider 1" />
<map value="ENC_FX1" action="action_deck 1 ? effect slider 3 : effect slider 3" />
<map value="ENC_FX2" action="action_deck 1 ? effect slider 4 : effect slider 4" />
<map value="ENC_SEARCH" action="action_deck 1 ? effect slider 3 : effect slider 3" />
<map value="ENC_FINE_PITCH" action="action_deck 1 ? effect slider 4 : effect slider 4" />
<map value="ENC_SEARCH_PLAY" action="action_deck 1 ? effect slider 2 : effect slider 2" />
I just changed to this mapping and it seems to be working now again. I am trying to find the RIGHT mapping combo here so that is STAYS the same. At one point in time my previous mapping was working perfect and then it stopped working. What is the deal?
<map value="ENC_FX_GAIN" action="action_deck 1 ? effect slider 1 : effect slider 1" />
<map value="ENC_PAN" action="action_deck 1 ? effect slider 2 : effect slider 1" />
<map value="ENC_FX1" action="deck 1 effect slider 3" />
<map value="ENC_FX2" action="action_deck 1 ? effect slider 4 : effect slider 4" />
<map value="ENC_SEARCH" action="deck 2 effect slider 3" />
<map value="ENC_FINE_PITCH" action="action_deck 1 ? effect slider 4 : effect slider 4" />
<map value="ENC_SEARCH_PLAY" action="deck 2 effect slider 2" />
I went back to VDJ 6.0.5 to see if it was doing it there and now it is doing it there. It was working just fine... I am fairly certain I tested applying the effect and slider control when the deck was not the "selected" deck. I am fairly frusterated as you will want to cue up your next track and perhaps even loop and layer the track for a while, meanwhile you are applying effects to the "master" track. I should not have to switch my headphone cue back to the master track JUST so i can control the effect slider.
What am I doing wrong or is this a bug? Here is the mapping from the XML
<map value="ENC_FX_GAIN" action="action_deck 1 ? effect slider 1 : effect slider 1" />
<map value="ENC_PAN" action="action_deck 1 ? effect slider 2 : effect slider 1" />
<map value="ENC_FX1" action="action_deck 1 ? effect slider 3 : effect slider 3" />
<map value="ENC_FX2" action="action_deck 1 ? effect slider 4 : effect slider 4" />
<map value="ENC_SEARCH" action="action_deck 1 ? effect slider 3 : effect slider 3" />
<map value="ENC_FINE_PITCH" action="action_deck 1 ? effect slider 4 : effect slider 4" />
<map value="ENC_SEARCH_PLAY" action="action_deck 1 ? effect slider 2 : effect slider 2" />
I just changed to this mapping and it seems to be working now again. I am trying to find the RIGHT mapping combo here so that is STAYS the same. At one point in time my previous mapping was working perfect and then it stopped working. What is the deal?
<map value="ENC_FX_GAIN" action="action_deck 1 ? effect slider 1 : effect slider 1" />
<map value="ENC_PAN" action="action_deck 1 ? effect slider 2 : effect slider 1" />
<map value="ENC_FX1" action="deck 1 effect slider 3" />
<map value="ENC_FX2" action="action_deck 1 ? effect slider 4 : effect slider 4" />
<map value="ENC_SEARCH" action="deck 2 effect slider 3" />
<map value="ENC_FINE_PITCH" action="action_deck 1 ? effect slider 4 : effect slider 4" />
<map value="ENC_SEARCH_PLAY" action="deck 2 effect slider 2" />
发表时间 Thu 07 Jan 10 @ 11:52 pm
First, action_deck is only needed if you want to perform a DIFFERENT function for the same button or knob that is present on both sides of the controller.
action_deck 1 ? effect slider 3 : effect slider 3 is unnecessary because you have the same action either side of the : - It can just simply be effect slider 3
To ensure that the action is applied to the active deck (The one playing out live), add deck active to the action. Based on what you have posted above, you would need something like the following:
action_deck 1 ? effect slider 3 : effect slider 3 is unnecessary because you have the same action either side of the : - It can just simply be effect slider 3
To ensure that the action is applied to the active deck (The one playing out live), add deck active to the action. Based on what you have posted above, you would need something like the following:
<map value="ENC_FX_GAIN" action="deck active effect slider 1" />
<map value="ENC_PAN" action="action_deck 1 ? deck active effect slider 2 : deck active effect slider 1" />
<map value="ENC_FX1" action="deck active effect slider 3" />
<map value="ENC_FX2" action="deck active effect slider 4" />
<map value="ENC_SEARCH" action="deck active effect slider 3" />
<map value="ENC_FINE_PITCH" action="deck active effect slider 4" />
<map value="ENC_SEARCH_PLAY" action="deck active effect slider 2" />
发表时间 Fri 08 Jan 10 @ 12:20 pm
So was it on purpose the key names are the same for different knobs and buttons on either side of the decks? This makea mapping 1) very confusing and complicated, as well as illogical. Let me know. If you need me to site the specific buttons and knobs.
The above produces the incorrect results. I want the function to apply to the deck the button is pressed or. knob turned. Should not matter if it is live or qued. That is how it works if you use skin controls.
The above produces the incorrect results. I want the function to apply to the deck the button is pressed or. knob turned. Should not matter if it is live or qued. That is how it works if you use skin controls.
发表时间 Fri 08 Jan 10 @ 12:41 pm
If a button/knob is physically labelled the same on both sides of the controller, then it will have one key name that will apply to both decks, which makes the mapping much simpler (I.e: You only need to map PLAY once rather than twice.) If the knob/button is labelled differently, then it will have two separate key names.
You can specify which deck to apply the action to by adding deck N in front, e.g: deck 1 effect slider 1
Try the following:
You can specify which deck to apply the action to by adding deck N in front, e.g: deck 1 effect slider 1
Try the following:
<map value="ENC_FX_GAIN" action="deck 1 effect slider 1" />
<map value="ENC_PAN" action="action_deck 1 ? deck 1 effect slider 2 : deck 2 effect slider 1" />
<map value="ENC_FX1" action="deck 1 effect slider 3" />
<map value="ENC_FX2" action="deck 1 effect slider 4" />
<map value="ENC_SEARCH" action="deck 2 effect slider 3" />
<map value="ENC_FINE_PITCH" action="deck 2 effect slider 4" />
<map value="ENC_SEARCH_PLAY" action="deck 2 effect slider 2" />
发表时间 Sun 10 Jan 10 @ 1:58 pm
I agree if the same button/knob exists on both sides/decks the key should be the same. However the reality with the Stealth Control in 6.0.5 is this is not the case. I would appreciate it if Atomix and/or Numark looked into this. The information below is the result of me going into the mapper tab and clicking new > auto learn > pressing the button > recording the key name that comes up, and then repeating the process on the opposite deck.
Button/Knob Name - Deck A Key / Deck B Key
PFL - PFL / PFL
Key - Key / Key
SYNC - Sync / Sync
Pitch Slider - Pitch / Pitch
Cue - Cue_Pause / Cue_Pause
Set Cue - Set_Cue / Set_Cue
Play - Play / Play
Jog Wheel - Jog
Select - FX_Select / Scratch
Filter On/Off - Scratch / Scratch <------ Notice this key is used on the Deck B for the \"Select\" key
On/Off - FX_ONOFF / RELOOP
Tap - DELAY_TAP / BEATLOCK
Pitch - - PITCHBEND- / PITCHBEND-
Pitch + - PITCHBEND+ / PITCHBEND+
Loop In - LOOP / LOOP
Loop Out - Cue_Play / Cue_Play
Load Track - LOAD / LOAD
Knobs:
FX AMT - ENC_FX_GAIN / FX_PAN
Filter AMT - ENC_PAN / ENC_SEARCH_PLAY <----- Notice this key is used on Deck B FX AMT as well.
PAR - ENC_FX1 / ENC_SEARCH
FINE PITCH - ENC_FX2 / ENC_FINE_PITCH
I noticed there was documentation in the 6.0.3 that the Stealth and Omni Controllers were updated. This is when my mapper broke. The Key Names changes on MANY of my buttons stopped working as I had mapped them. The above shows why, the key names are not the same from deck to deck, button to button, and 1 key on Deck B overlaps with a correctly mapped button.
I will look at the information you provided, but I await your review of the above. I included a pic from the Numark site in case you need to identify where the buttons are.
Button/Knob Name - Deck A Key / Deck B Key
PFL - PFL / PFL
Key - Key / Key
SYNC - Sync / Sync
Pitch Slider - Pitch / Pitch
Cue - Cue_Pause / Cue_Pause
Set Cue - Set_Cue / Set_Cue
Play - Play / Play
Jog Wheel - Jog
Select - FX_Select / Scratch
Filter On/Off - Scratch / Scratch <------ Notice this key is used on the Deck B for the \"Select\" key
On/Off - FX_ONOFF / RELOOP
Tap - DELAY_TAP / BEATLOCK
Pitch - - PITCHBEND- / PITCHBEND-
Pitch + - PITCHBEND+ / PITCHBEND+
Loop In - LOOP / LOOP
Loop Out - Cue_Play / Cue_Play
Load Track - LOAD / LOAD
Knobs:
FX AMT - ENC_FX_GAIN / FX_PAN
Filter AMT - ENC_PAN / ENC_SEARCH_PLAY <----- Notice this key is used on Deck B FX AMT as well.
PAR - ENC_FX1 / ENC_SEARCH
FINE PITCH - ENC_FX2 / ENC_FINE_PITCH
I noticed there was documentation in the 6.0.3 that the Stealth and Omni Controllers were updated. This is when my mapper broke. The Key Names changes on MANY of my buttons stopped working as I had mapped them. The above shows why, the key names are not the same from deck to deck, button to button, and 1 key on Deck B overlaps with a correctly mapped button.
I will look at the information you provided, but I await your review of the above. I included a pic from the Numark site in case you need to identify where the buttons are.

发表时间 Sun 10 Jan 10 @ 7:17 pm
It's been a few days. Do I need to log a ticket with Atomic? Or is my Stealth control defective? I have a friend with one. Have not checked how the keys read on his.
发表时间 Wed 13 Jan 10 @ 8:50 pm
djchad72 wrote :
It's been a few days. Do I need to log a ticket with Atomix? Or is my Stealth control defective? I have a friend with one. Have not checked how the keys read on his.
发表时间 Thu 14 Jan 10 @ 9:35 pm
Last email I got from cstoll was that this was going into a VDJ update. Anyone in Atomix land with an update on this issue? I asked for an update in my ticket but it got closed without a response.
What we found was there are 2 different Stealth Controls in the marketplace with different labels for the hardware buttons. One unit has buttons/knobs that mirror one another, meanwhile the other has some that mirror and others that are unique to the deck. The VDJ MIDI labels/commands map to the one that has the unique labels. Which makes it difficult on the one that mirrors to map identically.
For instance, I can not easily and reliably map a specific effect on/off and slider controls to buttons and knobs without it affecting the wrong deck, even when I specify in the VDJ Script syntax which deck (ie Deck A effect " " active)
An update on this would be great. I got a new computer and can now find the email chain from cstoll to reply and ask.
What we found was there are 2 different Stealth Controls in the marketplace with different labels for the hardware buttons. One unit has buttons/knobs that mirror one another, meanwhile the other has some that mirror and others that are unique to the deck. The VDJ MIDI labels/commands map to the one that has the unique labels. Which makes it difficult on the one that mirrors to map identically.
For instance, I can not easily and reliably map a specific effect on/off and slider controls to buttons and knobs without it affecting the wrong deck, even when I specify in the VDJ Script syntax which deck (ie Deck A effect " " active)
An update on this would be great. I got a new computer and can now find the email chain from cstoll to reply and ask.
发表时间 Sun 28 Mar 10 @ 11:38 pm
The buttons should be separate now in ver 6.0.7 ... so you can independently map them the way you want.
发表时间 Sun 28 Mar 10 @ 11:42 pm
groovy, ill give it a try this week and let you know. Is there anything I should know before I get started? ie should I start my map from scratch or edit existing with new "learns" for the ones we identified that were different?
发表时间 Sun 28 Mar 10 @ 11:49 pm