Niels (cph)
I would like to use the FX ASSIGN buttons on my MC7000 for a different purpose than the default mapping.
But when I look in the mapper it seems the 4 buttons all map to the same key. On the left side it is 'FX1_ASSIGN' and on the right side it is 'FX2_ASSIGN'. And there is no parameter according to the debug verb.
I can see with a midi sniffer that the buttons send unique notes, so it should be possible to map each button individually -- or?
Here are the midi notes sent by the device:
FX1 ASSIGN (left side)
FX2 ASSIGN (right side)
Is there a way to attach different scripts/actions to each of these buttons?
Thanks!
But when I look in the mapper it seems the 4 buttons all map to the same key. On the left side it is 'FX1_ASSIGN' and on the right side it is 'FX2_ASSIGN'. And there is no parameter according to the debug verb.
I can see with a midi sniffer that the buttons send unique notes, so it should be possible to map each button individually -- or?
Here are the midi notes sent by the device:
FX1 ASSIGN (left side)
NOTE ON NOTE OFF
1 98 05 7F 98 05 00
2 98 06 7F 98 06 00
3 98 07 7F 98 07 00
4 98 08 7F 98 08 00
FX2 ASSIGN (right side)
NOTE ON NOTE OFF
1 99 05 7F 99 05 00
2 99 06 7F 99 06 00
3 99 07 7F 99 07 00
4 99 08 7F 99 08 00
Is there a way to attach different scripts/actions to each of these buttons?
Thanks!
Posté Sun 03 Dec 23 @ 11:56 am
locoDog
device_side left ? script for left : script for right
Posté Sun 03 Dec 23 @ 11:59 am
Niels (cph)
The problem is that each of the 4 buttons map to the same key.
On, say left side, ‘FX1_ASSIGN’ is triggered no matter which button I press, so I can’t attach actions to each individual button.
On, say left side, ‘FX1_ASSIGN’ is triggered no matter which button I press, so I can’t attach actions to each individual button.
Posté Sun 03 Dec 23 @ 12:27 pm
Niels (cph)
There would need to be these keys defined:
FX1_ASSIGN_1
FX1_ASSIGN_2
FX1_ASSIGN_3
FX1_ASSIGN_4
..and
FX2_ASSIGN_1
FX2_ASSIGN_2
FX2_ASSIGN_3
FX2_ASSIGN_4
FX1_ASSIGN_1
FX1_ASSIGN_2
FX1_ASSIGN_3
FX1_ASSIGN_4
..and
FX2_ASSIGN_1
FX2_ASSIGN_2
FX2_ASSIGN_3
FX2_ASSIGN_4
Posté Sun 03 Dec 23 @ 12:39 pm
locoDog
then they're not side specified, they're deck specified
use
action_deck 1 ?
use
action_deck 1 ?
Posté Sun 03 Dec 23 @ 12:41 pm
Niels (cph)
Hmm — am I missing something, or you are you..? 😊
I’ll rephrase: When I press the button labeled ‘1’ on the left side, the ‘FX1_ASSIGN’ key is triggered. The same happens when I press buttons ‘2’, ‘3’, and ‘4’. They all trigger ‘FX1_ASSIGN’. Therefore, I can’t specify different script actions for each button.
The same happens on the right side, where the key triggered is ‘FX2_ASSIGN’.
I’ll rephrase: When I press the button labeled ‘1’ on the left side, the ‘FX1_ASSIGN’ key is triggered. The same happens when I press buttons ‘2’, ‘3’, and ‘4’. They all trigger ‘FX1_ASSIGN’. Therefore, I can’t specify different script actions for each button.
The same happens on the right side, where the key triggered is ‘FX2_ASSIGN’.
Posté Sun 03 Dec 23 @ 1:00 pm
locoDog
I think it's you.
If a button has a common definition name it must either be side assigned or deck assigned, that's how it works.
I don't have the gear in front of me, but if I did I'd try this
set a +1 & var_list
try the 4 buttons on one side, see if the variables are deck specific.
you've got 2 definition names, 4 buttons common to each, but each button is deck specified
action_deck 1 ? set someVar +1 & var_list : action_deck 2 ? set anotherVar +1 & var_list : action_deck 3 ? set someVar +1 & var_list : action_deck 4 ? set someVar +1 & var_list :
If a button has a common definition name it must either be side assigned or deck assigned, that's how it works.
I don't have the gear in front of me, but if I did I'd try this
set a +1 & var_list
try the 4 buttons on one side, see if the variables are deck specific.
you've got 2 definition names, 4 buttons common to each, but each button is deck specified
action_deck 1 ? set someVar +1 & var_list : action_deck 2 ? set anotherVar +1 & var_list : action_deck 3 ? set someVar +1 & var_list : action_deck 4 ? set someVar +1 & var_list :
Posté Sun 03 Dec 23 @ 1:33 pm
IIDEEJAYII
I can confirm... since I have the MC7000 FX1_ASSIGN buttons remapped.
Use Locodogs suggestion:
action_deck 1 ? SCRIPT FOR BUTTON 1 : action_deck 2 ? SCRIPT FOR BUTTON 2 : action_deck 3 ? SCRIPT FOR BUTTON 3 : action_deck 4 ? SCRIPT FOR BUTTON 4
to map each of the 4 buttons.
And of course similar for the FX2_ASSIGN buttons
------------------
Think I have remapped (or added scripting) to every button (those w midi) on the MC7000 :P
(each button/knob has a min of 3 functions and currently a max of 6 functions, now its just..remembering it all lol)
And maybe the dream controller of the future will have O-LED displays for all knobs and buttons, truly making the platform of buttons/knobs even for useful:
https://www.virtualdj.com/forums/255282/Wishes_and_new_features/Hardware_-_Dreams___Wishes.html
Use Locodogs suggestion:
action_deck 1 ? SCRIPT FOR BUTTON 1 : action_deck 2 ? SCRIPT FOR BUTTON 2 : action_deck 3 ? SCRIPT FOR BUTTON 3 : action_deck 4 ? SCRIPT FOR BUTTON 4
to map each of the 4 buttons.
And of course similar for the FX2_ASSIGN buttons
------------------
Think I have remapped (or added scripting) to every button (those w midi) on the MC7000 :P
(each button/knob has a min of 3 functions and currently a max of 6 functions, now its just..remembering it all lol)
And maybe the dream controller of the future will have O-LED displays for all knobs and buttons, truly making the platform of buttons/knobs even for useful:
https://www.virtualdj.com/forums/255282/Wishes_and_new_features/Hardware_-_Dreams___Wishes.html
Posté Sun 03 Dec 23 @ 2:09 pm
Niels (cph)
Thank you guys! And I apologize for not getting it. I will try these latest suggestions once I get near the gear again.
👍🏻
👍🏻
Posté Sun 03 Dec 23 @ 2:14 pm
IIDEEJAYII
Additional Note:
the same use of action_deck X is needed for addressing the PFL button mappings individually on the MC7000.
the same use of action_deck X is needed for addressing the PFL button mappings individually on the MC7000.
Posté Sun 03 Dec 23 @ 2:33 pm
Niels (cph)
Thanks again guys for pointing me in the right direction. This way of “multiplexing” several buttons on one mapper key was new to me. I learned something — thanks!
I managed to pull off most of what I set out to, except for controlling LED blinking. Enough for today, though.
I managed to pull off most of what I set out to, except for controlling LED blinking. Enough for today, though.
Posté Sun 03 Dec 23 @ 6:01 pm