Just wondering if you need to specify the deck that will be effected if you are using "device_side 'left' ? action for button on left deck : action for button on right deck"
I am trying to use a large code but basically it is
device_side 'left' ? deck 1 effect "granular" active : deck 2 effect "granular" active
Can it be shortened to
device_side 'left' ? effect "granular" active : effect "granular" active
but still effect only the deck on the side the button is on?
Cheers,
Andrew
I am trying to use a large code but basically it is
device_side 'left' ? deck 1 effect "granular" active : deck 2 effect "granular" active
Can it be shortened to
device_side 'left' ? effect "granular" active : effect "granular" active
but still effect only the deck on the side the button is on?
Cheers,
Andrew
geposted Sat 04 Jun 11 @ 11:16 am
You shouldn't need to add the deck number because the software already knows this from which side you pressed the button on.
geposted Sat 04 Jun 11 @ 12:54 pm
That's good to know, now that part will fit but... I have been thinking of other possibilities and now I kind of want to use
device_side 'left' ? deck 2 effect "looproll" active : deck 1 effect "looproll" active
Its the other way around now so I can increase the amount of available buttons for the dj2go, is this still possible? Sorry I don't have the device yet I'm just trying to get the mapping sorted while I wait for it.
Cheers for the reply
device_side 'left' ? deck 2 effect "looproll" active : deck 1 effect "looproll" active
Its the other way around now so I can increase the amount of available buttons for the dj2go, is this still possible? Sorry I don't have the device yet I'm just trying to get the mapping sorted while I wait for it.
Cheers for the reply
geposted Sat 04 Jun 11 @ 1:06 pm
That would simply activate the effect on the opposite deck to what you pressed, which would be very confusing.
If you want to increase the number of buttons, try assigning a button you don't use to be a SHIFT button, e.g:
set $shift 1 while_pressed
Then map buttons as follows:
var $shift ? shifted action : non-shifted action
If you want to increase the number of buttons, try assigning a button you don't use to be a SHIFT button, e.g:
set $shift 1 while_pressed
Then map buttons as follows:
var $shift ? shifted action : non-shifted action
geposted Sat 04 Jun 11 @ 1:26 pm
I Already have 1 main one (shifts the whole device) 2 deck specific ones and about 4 little ones for single action shifts, plus hundreds of variables LOL, can I make a definition file so I use each button separately so It will do what I want?
Also I think I need a definition file anyway so I can map the leds is this true, or are they available to control with the default mapping?
Sorry I have never mapped a 2 deck controller before... :)
Also I think I need a definition file anyway so I can map the leds is this true, or are they available to control with the default mapping?
Sorry I have never mapped a 2 deck controller before... :)
geposted Sat 04 Jun 11 @ 1:39 pm
You could make your own definition if you wish, however its much easier and less time consuming to just use device_side 'left' ? left action : right action to split the left and right button functions.
You can also use this in combination with shift, e.g:
device_side 'left' ? var $shift ? shifted left action : unshifted left action : var $shift ? shifted right action : unshifted right action
You can also use this in combination with shift, e.g:
device_side 'left' ? var $shift ? shifted left action : unshifted left action : var $shift ? shifted right action : unshifted right action
geposted Sat 04 Jun 11 @ 1:42 pm
Yeah, I have another shift on top of that so I think I will need to make a definition file and start separating my mapping so I can use them on individual buttons, the granulizer thing won't need to be shorter because it will fit in the script area if not using device_side.
I think the controller will need a couple of extra buttons on the right side when deck 1 shift is activated and visca versa, as there is only 6 buttons per side not including the browser buttons.
Thanks for your help.
I think the controller will need a couple of extra buttons on the right side when deck 1 shift is activated and visca versa, as there is only 6 buttons per side not including the browser buttons.
Thanks for your help.
geposted Sat 04 Jun 11 @ 1:57 pm