sebastian.beca
Hi, I'm noticing that the new factory default mapping for the Xone:K2 Midi controller sets it up as 2 (or 4) decks. For my use case I'd like to setup some buttons and knobs differently on each side of the controller, so duplicating functions on a per deck basis doesn't make sense. Is there a way to setup this controller as a generic MIDI controller and map each individual button/knob to ones needs?
Inviato Tue 12 Apr 22 @ 2:03 am
locoDog
see action_deck script description
to work around it or
search settings for
disableBuilt
to work around it or
search settings for
disableBuilt
Inviato Tue 12 Apr 22 @ 3:11 am
PhantomDeejay
DisableBuiltInDefinition is never a good choice. It disables ALL built-in native definitions, not just a single device.
The first (and highly recommended) option is to use action_deck
This code "splits" a "common" button between 4 decks to perform separate actions depending on which deck the button is pressed.
PS: The action can be simplified, depending on somebody's needs.
This code will change only one button, while the rest 3 will perform another action.
The first (and highly recommended) option is to use action_deck
action_deck 1 ? play : action_deck 2 ? stop : action_deck 3 ? loop : action_deck 4 ? dump
This code "splits" a "common" button between 4 decks to perform separate actions depending on which deck the button is pressed.
PS: The action can be simplified, depending on somebody's needs.
action_deck 2 ? loop : play
This code will change only one button, while the rest 3 will perform another action.
Inviato Tue 12 Apr 22 @ 12:49 pm
sebastian.beca
work around is good enough for my needs, thx!
Inviato Tue 12 Apr 22 @ 7:22 pm
I am new to virtual dj, where you write this action commands?
Inviato Wed 01 Feb 23 @ 10:25 am
PhantomDeejay
Inviato Wed 01 Feb 23 @ 1:04 pm
where this commans need to be pasted?
PhantomDeejay wrote :
DisableBuiltInDefinition is never a good choice. It disables ALL built-in native definitions, not just a single device.
The first (and highly recommended) option is to use action_deck
This code "splits" a "common" button between 4 decks to perform separate actions depending on which deck the button is pressed.
PS: The action can be simplified, depending on somebody's needs.
This code will change only one button, while the rest 3 will perform another action.
The first (and highly recommended) option is to use action_deck
action_deck 1 ? play : action_deck 2 ? stop : action_deck 3 ? loop : action_deck 4 ? dump
This code "splits" a "common" button between 4 decks to perform separate actions depending on which deck the button is pressed.
PS: The action can be simplified, depending on somebody's needs.
action_deck 2 ? loop : play
This code will change only one button, while the rest 3 will perform another action.
Inviato Sun 05 Feb 23 @ 11:28 am