The Hofff 
I wanted to reassign some of the buttons on the controller. It looks like deck 1 and 2 are controlled by the same mapping. Is there a way to segragate them? I.e. make the 'view' button on deck 1 behave differently than on deck 2? How would I differentiate the button in the mapping section?
Thanks
Thanks
Posté Fri 08 Feb 19 @ 9:19 pm
locoDog
action_deck 1 ? mapping for deck 1 : mapping for deck 2
Posté Fri 08 Feb 19 @ 9:28 pm
The Hofff
Thanks loco
I did the below script, but the playlist_add is happening for both buttons. Am I doing something incorrect?
action_deck 1 ? playlist_add : sidelist_add
I did the below script, but the playlist_add is happening for both buttons. Am I doing something incorrect?
action_deck 1 ? playlist_add : sidelist_add
Posté Fri 08 Feb 19 @ 9:42 pm
locoDog
what buttons are you using?
try
device_side 1 ? mapping for deck 1 : mapping for deck 2
try
device_side 1 ? mapping for deck 1 : mapping for deck 2
Posté Fri 08 Feb 19 @ 10:28 pm
The Hofff
Was trying it using the VIEW and VIEW_LONG buttons. Tried device_side, but no luck.
Posté Sat 09 Feb 19 @ 12:17 am
The Hofff
Update: I tried the action (action_deck 1 ? playlist_add : sidelist_add) on the browse knob when pushed, and it worked as expected. Adding track to automix playlist when pushing the deck 1 browse knob and sidelist playlist when pushing the deck 2 knob.
It seems the issue is related to me using the 'View' button for this script. Any thoughts as to why that might be?
It seems the issue is related to me using the 'View' button for this script. Any thoughts as to why that might be?
Posté Sun 10 Feb 19 @ 11:09 pm
locoDog
Ok final shot try
device_side "left" ? script1 : script2
device_side "left" ? script1 : script2
Posté Sun 10 Feb 19 @ 11:43 pm
locoDog
From looking at Midi Table device_side "left" is my best guess, If I had access to the def file I could be certain (and much quicker for you)
But atomix keep tight control of def files to prevent them being leaked, some hardware makers are decent and provide midi tables but it's still a lot of work to write a def file, some hardware isn't as nice and staff like phantom & djdad have to do a lot to get stuff working.
But atomix keep tight control of def files to prevent them being leaked, some hardware makers are decent and provide midi tables but it's still a lot of work to write a def file, some hardware isn't as nice and staff like phantom & djdad have to do a lot to get stuff working.
Posté Mon 11 Feb 19 @ 12:38 am
PachN
Or.... you do something like this:
holding 1000ms ? sidelist_add : playlist_add
holding 1000ms ? sidelist_add : playlist_add
Posté Mon 11 Feb 19 @ 9:44 am
PhantomDeejay
On some devices buttons like "VIEW" send the same MIDI message from both sides when pressed. In other words they behave as one button with two instances. Therefore it's not possible for VirtualDJ to tell the "deck" or "side" of the controller the button was pressed. That's why your "VIEW" button can't be mapped like that, but other buttons can.
If I remember correctly "BACK" button falls in the same category as well
If I remember correctly "BACK" button falls in the same category as well
Posté Mon 11 Feb 19 @ 12:40 pm
locoDog
I see now, b-2 & b-3, sorry I read the table wrong.
Posté Mon 11 Feb 19 @ 1:01 pm
PhantomDeejay
It's quite common for Pioneer to bind these buttons on all units that have dual browser control sections (like DDJ-SZ, DDJ-SZ2, DDJ-RZ, DDJ-RZX e.t.c.)
The browser knob also falls in the same rule, with the exception of "push" action on some units when it's used to LOAD a song (like DDJ-SZ for instance)
The browser knob also falls in the same rule, with the exception of "push" action on some units when it's used to LOAD a song (like DDJ-SZ for instance)
Posté Mon 11 Feb 19 @ 1:28 pm
The Hofff
Thanks for the additional color. I ended up splitting them up by a press or a long press on the view button.
In the long run that's probably a better solution since I can browse the library from either side.
Thanks again everyone!
In the long run that's probably a better solution since I can browse the library from either side.
Thanks again everyone!
Posté Wed 13 Feb 19 @ 12:16 am
gmedia
I am trying to trigger some lighting controls in SoundSwitch using the pads on the DDJ-1000. I don't know if this is the best place for this or not? Any ideas on how to do this? The SS software is looking for me to press a button on any connected midi controller to map.
Chris
Chris
Posté Sat 29 Jun 19 @ 12:44 pm