To use the pads to control individual decks you just need to specify “deck #” before every command eg
deck 1 effect active
deck 2 effect slider 1
deck left effect button 1 1
deck right effect “someEffect” active
IMO the best way to do it is use “deck left/right” as that is not limited to just two deck skins so requires no modification if you want to use more than two decks.
if you want to activate the effect on both decks you would need to use a conditional variable so you will always have a predictable response. They have a pretty simple syntax that is the same as a “turnary operator” in javascript eg.
query ? action if true : action if false
what you would do in this case is set up a simple variable to toggle when you press the button, “the variable can be called anything you want”. The only other thing that is added in this code is chaining commands to with the ‘&’ operator.
toggle ‘but_1’ & var ‘but_1’ ? blink 300ms & deck left effect “effectName” active on & deck right effect “effectName” active on : off & deck left effect “effectName” active off & deck right effect “effectName” active off
in regard to the pads in CC or note mode that is set in the firmware but with a little scripting you can make the pads act like the ones on the VCI-380 in serato DJ. the syntax you would use is
param_greater 0% ? effect “effectName” active on & effect “effectName” slider 1 : effect “effectName” active off
by using “param_greater 0%” in a condition you are saying if the CC value sent from the control is higher than 0 switch the effect on and control the first slider, else if the CC value is on 0 turn off the effect, there isn’t really a point of resetting the sliders position as it should be there anyway.
I didn’t add the deck # information, I’ll leave it for you to do as the best way to learn is to practice, but as it may not be clear “param_greater|smaller|equal|not_equal” works on the calling control so it doesn’t need to be specified as it’s irrelevant, but you do need to do it before every individual command.
another good use for the pads in CC mode is to control the sampler so you can drum samples on the pads, I’ll let you figure that out as it will use the same syntax as above but instead use “sampler # play”, “sampler # stop” and “sampler # volume”
if you get stuck on commands, I think it’s quickest to type it in the action box, then you will see all commands relevant to what you typed, eg if you type “loop” you will get everything related to looping with a description, or there is a list of every command in the wiki, but it’s pretty long so probably best to familiarize yourself with the commands directly in the mapper before turning to that.
