登录:     

Forum: General Discussion

Topic: Remapping Assigning Idea?

由于该帖子已年深日久，可能包含陈旧过时或描述错误的信息。

I have a Hercules 4MX
and I am just using the regular VDJ 7 4 deck skin.
Last night i was adding my effects and what not to my FX buttons.

I have 2 things I want to map somewhere on this console- The Filter knob and Key Knob.
You can't assign these to a buttons right? Faders?


I don't have any ideas where to assign them or how I can utlize them on this console.

I was up to 3 Am trying to figure this out...total pain!
Feeling like two old turntables and a mixer are easier then this midi stuff.
 
发表时间 Thu 17 Mar 11 @ 11:41 am
Well I don't have one of those but I have a RMX so what I did was use the pitch faders for the filter. In my opinion there to short and to sensitive to be used as actual pitch fades. Plus if your using turntables or cdjs they have there own pitch fade. As for the key I don't really mess with the keys that much so I never mapped that.

Just an idea
Huey
 
That is an interesting idea.
I feel like I use the pitch faders a lot.

On the 4MX there is a knob that changes the PF1 or something on the effects.
In loops the knob gives you the loop beat options- 4, 8, 12, etc...

I just really need the filter knob mapped somewhere.
I wonder if I can get this PF1 knob to give loop beat options for loops
and Filter for effects?

Or maybe there is away I can assign a kill button or even the microphone volume knob to Filter which I never use.

The touch wheel would be good to but I do things with those as well.
 
I suppose if you have a " shift" button mapped you could give these knobs dual actions. Also for the buttons they don't have to be mapped to the unit itself to work. I'm no good when it comes to scripting but there are others who can help you out if you choose to go down that route.

Good Day
Huey
 
in virtual dj pro 7 you can go into mappers and change the function of just about any button. there are plenty of examples in the forums.
 
mapping is actually pretty easy when doing the basic stuff and not that much more complicated to use a shift function. To start with I suggest going to the mapper tab in the config menu. to start with you just need to select 'new' then turn the knob you want to use. After that press action learn and you will have the command you will need.

Now that you have your command (I'm guessing it will just say 'key') you need to decide if you want this to be a global effect (all decks at once) or what I would suggest... having 4 knobs controlling the decks individually or having 4 shift buttons to have the same knob control the parameter depending on what shift is pressed.

The distinction for individual control is deck 1, deck 2 etc... Supposing that you want four individual knobs you already have your code:
'deck 1 key' just repeat that for decks 1 through 4.

Now if you want to try the second option of using a shift button you have a couple of different options...

Option A 'cycle' - with this mode you use a button that is designated as a shift button, eg. press the button once to be in mode 1, twice to be in mode 2 all the way to whatever number you put after the word cycle... the disadvantage of this is you need a visual reference to tell you what mode your in. If you choose this someone in the hardware forum can probably help with leds.

eg cycle 'my_var' 4 ('my_var' can be anything you like to describe what the variable is)


Option B 'set' - with this option you will require four individual buttons to set the different variables, the benefit of this is you always know what mode you in, but it's at the expense of more buttons.

Another fantastic feature of vdj script is you can have other commands such as 'while_pressed' which does what it's called... as in the action will only happen if the button is being pressed, if you combine that with 'set' you have the best of both worlds for this type of action as you will not always be using it, so there's no need to have it permanently set to a knob. eg

set 'my_var' while_pressed


Now that you have your shift button set up you need to assign the knobs and buttons depending on which mode your in...
there are only two commands you are required to know... ?, : below is an example of how its used, after I will explain in more detail

Action 1 ? Action 2 : Action 3

? - means (if true)
: - means (if false, or)"not sure if that is the real meaning but if works for me..."
so from the above example..

Action 1 ( if Action 1 is true then) do action 2 (if Action 1 is false) do action 3


The last thing you need is to be able to select which var mode you are in I, always use var_equal, but there is commands like var_greater, var_smaller etc... but like I said i use var_equal... eg

var_equal 'my_var' 1


From here if you understand the above concept it is pretty much up to your imagination and patience (not everything works the first time LOL). The other command you can use is '&' this will string commands together to be performed at the same time eg.

deck 1 Action 1 & deck 1 Action 2

So to finish I will give you an example of the code I think you should use for a 'set' shift button and an endless encoder (bear in mind I have no way to test it)


for the shift buttons (left/right):

deck 1 play ? set 'deck_1_shift' while_pressed : deck 3 play ? set 'deck_3_shift' while_pressed : (whatever the button already does)

deck 2 play ? set 'deck_2_shift' while_pressed : deck 4 play ? set 'deck_4_shift' while_pressed : (whatever the button already does)

(maybe that wont work for four decks as it might get confused if decks 1 and 3 are playing at the same time... The joys of mapping LOL)


If that doesn't work I think you will need to set up four individual buttons... thats just

deck 1 play ? set 'deck_1_shift' while_pressed : (whatever the button already does)

for the encoder

var_equal 'deck_1_shift' ? deck 1 key : var_equal 'deck_2_shift' ? deck 2 key : var_equal 'deck_3_shift' ? deck 3 key : var_equal 'deck_4_shift' ? deck 4 key : (whatever the knob already does)

Wow I must be really bored to write all that LOL, anyway hope it helps you to understand mapping and its possibilities.

=========EDIT==============================

Actually I just read your post again... can you paste the pfl knob code an I'll see if it can be modified to include this...
 
Sorry i wrote the encoder wrong and it wouldn't let me edit it...

var_equal 'deck_1_shift' ? param_greater 0% ? deck 1 key +0.01 : deck 1 key -0.01 : var_equal 'deck_2_shift' ? param_greater 0% ? deck 2 key +0.01 : deck 2 key -0.01 : var_equal 'deck_3_shift' ? param_greater 0% ? deck 3 key +0.01 : deck 3 key -0.01 :var_equal 'deck_4_shift' ? param_greater 0% ? deck 4 key +0.01 : deck 4 key -0.01 : (whatever the knob already does)

note that you can change the sensitivity of the knob by changing the decimal eg 0.05 until you find what works best
 
wow...you did write a lot.
Thanks...I decided against the PFL button.

Instead will just map something out on the keyboard and of course have issues with that.
I designated - < and > key for moving the filter knob up and down.
My issue is getting this to work on all the decks.
So far I load up deck one with a track and those keys will only
work with that deck. I want it to be able to work on deck 2, 3, 4, etc.

I used 'Deck Active' but it won't allow you to jump to other active decks.
Not sure how to map this.
 
If your using the four deck skin that comes with vdj 7 you can use "deck default" it will only work on the highlighted deck (little buttons on each deck at the top right).

If you want you could use 4 individual buttons to select the decks eg
"deck 1 active"

or you could have one button to scroll through the active decks eg
"deck 1 active ? deck 2 active : deck 2 active ? deck 3 active : deck 3 active ? deck 4 active : deck 4 active ? deck 1 active"
 


(陈旧帖子或论坛版块会自动关闭)