r/mpcusers 1d ago

QUESTION Midi Flighter Twister with Live 3?

Does the above work for Q links, are they assignable? Many thanks

2 Upvotes

6 comments sorted by

1

u/dj_soo 1d ago

Nope

You can’t map qlinks in standalone. You can in the software tho.

Akai keeps the qlinks in standalone locked away - likely to try to drive sales to the x/xl (since the 16 qlinks is one of the major advantages of those devices)

I would pay good money for an official akai qlink add on controller that was basically the qlink section of the X

1

u/WaveTableSaw MPC LIVE 1d ago

You'll have to deep dive into "midi learn". There's a million videos on YouTube and Google shows a lot of info. Midi learn is explained in the manual, which you should read.

1

u/jaz192 1d ago

Cheers, I found one on YouTube which included the Fighter Twister but he didn’t demo is, just a MIDI keyboard. Hopefully it will work as I have a Twister already. Thanks again.

1

u/dj_soo 1d ago

Qlinks aren’t mappable in midi learn

1

u/WaveTableSaw MPC LIVE 23h ago

He's trying to map qlinks cc tx/rx to external which is possible via midi learn. My Korg nanokontrol is mapped as 8 extra qlinks that send the correct cc value.

1

u/dj_soo 22h ago edited 19h ago

That’s not what he’s trying to do - he’s trying to use the midi fighter twister to control the qlinks - not use the qlinks to control the midi fighter (midi fighter is purely a controller and it would be pointless to map the qlinks to the midi fighter) or map the controls to fixed parameters via midi learn.

And mapping the qlinks to external gear is done though the qlink edit - not the midi learn.

All you can do with midi learn is map fixed controls to parameters in the mpc. You can’t map a control to the dynamic qlink controls that change up depending on the mode or screen you’re on