SuperKonquer wrote:I'm using it to turn block chords into strums so I can strum in chord progression mode. And I'm using rescales for the CCs so I can map the qlinks and have them make visual sense on the Oled screens. In addition I have CC's working like the Force's macros where I can adjust\trigger multiple parameters with one Qlink and\or have parameters trigger from different values of one CC.
I have 3 preset strum "spreads" where I can slow or speed up the strum in real time sorta like the keystep 37. I can increase or reduce the polyphony in a chord just like the Keystep 37. And then I have delays and arps and repeats mapped so I can adjust different settings of a strum. With a repeat on any particular note, it can strum the chord followed by plucking 1 or more notes.
I have LFOs mapped on certain notes so I can map a pitch bend to one or more notes in the strum. I also played around with polyphonic pitch bend but that is complicated and I'm not proficient enough to use that musically. I also like to map aftertouch to subtle pitch bends to create more expressiveness. At the end of the chain I have LFOs that modulate the midi eq. It creates very expressive volume modulations and it works incredible for humanizing output.
One thing that I have done that I've found really cool is transforming CC values to notes so I can play a glissando just from twisting a Qlink. And of course we have the infinitely configurable arps to play with. What's really eating up my pipes is reloops for mapping. Hopefully one day soon we will get an update that maps internally.
As you can see it has turned my MPC into a powerhouse of creativity. I haven't even really scratched the surface. I've been meaning to experiment with an " groovy auto-drummer" of sorts. Where I can turn on off preset drum patterns and make them tweakable with the Qlinks. I'll definitely need a dedicated MidiHub for that set up because that's definitely a 255 pipe patch.
That’s give me plenty to think about, thanks .
