Using a modifier as a shift key for ANOTHER midi controller? Help!

[rt24]

Using a modifier as a shift key for ANOTHER midi controller? Help!

I haven’t figured this one out yet. Does traktor allow you to make a shift-key modifier that will apply for another seperate controller?

My example: I want to be able to press an LED button on my xone 1d that will act as a shift-key for a midifighter. When I press the shift key modifier on the xone, buttons on the midifighter change functions (specifically cue points). That way I don’t need to put the shift-key on the midifighter.

Anybody know how to do this? My new set-up that is in progress is kinda reliant on this to be perfect

[M_Elbert_Grant]

you gotta create modifiers that basically act as toggles.
"First create a command that says ” if shift is off (m1= 0) then turn shift on (m1=1)”

Duplicate that modifier and change it to say “if shift is on (m1=1) then turn shift off (m1=0)

Now assign both of these modifier commands to the same button. This is your toggle shift button.

Finally you need to apply that modifier rule to a performance function.

I will first assign what happens when the modifier is zero, play works normally:

and then I assign what happens to that button if I have engaged shift. Play becomes Load loop play:"

[derschaich]

create your mapping (the modifier from your xone, and all the commands on you midi-fighter) for a seperated device (generic midi) apart from the xone.

you need the midi-in on “all ports” to get the signals from the xone and the midi-fighter.

now you map the modifier just as it was on a single controller.

be careful with the the midi note of the modifier-signal not being used on the midi fighter.

[fullenglishpint]

@M_Elbert_Grant

you gotta create modifiers that basically act as toggles…

I don’t think that’s what he was asking.

The answer I believe is no at the moment, there are no global modifiers that affect all controllers and not just the one you’re mapping. I think it’s a much requested but as yet unimplemented feature. Someone please correct me if I’m wrong though!

[fullenglishpint]

@derschaich

create your mapping (the modifier from your xone, and all the commands on you midi-fighter) for a seperated device (generic midi) apart from the xone.

you need the midi-in on “all ports” to get the signals from the xone and the midi-fighter.

now you map the modifier just as it was on a single controller.

be careful with the the midi note of the modifier-signal not being used on the midi fighter.

ah right so it is possible via workaround… I wouldn’t dare do that with my setup though cos there are so many midi notes flying around that using ‘all ports’ for anything is just plain dangerous!

[derschaich]

just keep your devices on different channels (if you don’t use more than 16 ) and everything stays clean!

[fullenglishpint]

Can I be bothered do change the channel of my mappings…

Nop!

Edit: No one need feel obliged to answer that comment, I have no desire for global modifiers!

[rt24]

@M_Elbert_Grant

you gotta create modifiers that basically act as toggles.
"First create a command that says ” if shift is off (m1= 0) then turn shift on (m1=1)”

Duplicate that modifier and change it to say “if shift is on (m1=1) then turn shift off (m1=0)

Now assign both of these modifier commands to the same button. This is your toggle shift button.

Finally you need to apply that modifier rule to a performance function.

I will first assign what happens when the modifier is zero, play works normally:

and then I assign what happens to that button if I have engaged shift. Play becomes Load loop play:"

Yeah I already know how to make one, I was wondering how to make a shift toggle on one midi controller for a different one. Thanks anyway.

@derschaich

create your mapping (the modifier from your xone, and all the commands on you midi-fighter) for a seperated device (generic midi) apart from the xone.

you need the midi-in on “all ports” to get the signals from the xone and the midi-fighter.

now you map the modifier just as it was on a single controller.

be careful with the the midi note of the modifier-signal not being used on the midi fighter.

All ports for the midifighters from the xone is a pretty good idea…but yeah the only concern is if some of the CCs and notes are already being used on another one. If I made the midi-controllers “learn” their functions naturally (just press learn and moving a fader, etc.), how would I change to separate CCs manually? Wouldn’t that make it so that the function would no longer affect the original button? I’m wondering…

@derschaich

just keep your devices on different channels (if you don’t use more than 16 ) and everything stays clean!

Yeah pretty much how do I do this?

Good answers so far guys. For a moment I thought that I wouldn’t get one! Thanks.

[TreTuna]

Doesn’t the midifighter default send everything to channel 3? So it would just be a matter of making sure that the xone and any other midi stuff you have isn’t, which is a matter per midi device. I’m not sure how you set the midi on the xone, but it’s never too hard. Either the controller editor software on the computer or some easy switch on the device. Never used one so I couldn’t tell you on that.

[fullenglishpint]

it’s very easy to change the midi channel on a midifighter, check out the menu mode sticky in the midifighter forum.

[MiL0]

what about using something like a virtual midi input/output program? that way all your controllers can share the same midi port?

[rt24]

@TreTuna

Doesn’t the midifighter default send everything to channel 3? So it would just be a matter of making sure that the xone and any other midi stuff you have isn’t, which is a matter per midi device. I’m not sure how you set the midi on the xone, but it’s never too hard. Either the controller editor software on the computer or some easy switch on the device. Never used one so I couldn’t tell you on that.

If it all goes to channel 3 that should be okay because I don’t think any other midis are using channel 3 at the moment.

@fullenglishpint

it’s very easy to change the midi channel on a midifighter, check out the menu mode sticky in the midifighter forum.

Will check that out. Thanks.

@MiL0

what about using something like a virtual midi input/output program? that way all your controllers can share the same midi port?

I’ve tried one of those before…could not get it going whatsoever. I will be trying the all ports methods once my midifighters get in, sounds pretty good.

[VonCache]

I am having a similar problem. I’ve created the modifier just how everyone has described in this thread, but the toggle I have assigned still doesnt work…I dont get it. Do I litterally have to type in the description box “when M1=0 turn off toggle”?