Workaround for qlink limitations in o2xl

Dudes, this "only one qlink at a time" limitation is really buggin me.
kind of makes the 2nd qlink redundant....
All i want is pitch on Q1 and filter on Q2, and this o2xl would be all i need
to do my thing on the move.
Please JJ, I need to record those 2 qlinks on the same track, even if i have to do it 1 at a time!!!!

I'm sure this has been discussed??
Anyone come up with a clever workaround??
At the moment i'm having to do my filters in the computer afterwards,
which is less immediate and less creative and means I'm finding
it hard to do stuff with just the mpc if I'm outta the studio or outta town.

This is a bit of a deal breaker for me to be honest.....

ccs controlling vst filter

if you use the midi in capabilities you can record pitch bend instead of using tune, alternatively adding pitch bend in step edit to the track will also bend notes. if you do it this way you can record pitch bend and cut off info to the same track, (by using LPF cutoff realtime/note on for instance)

seems to work the other way around too: set slider to cc74 and record some changes (you wont hear the filter sweep until you play it back) now record some tune changes on the slider. you should have both tune changes and filter sweeps playing back (not resonance though- couldnt get that to work)

note: i cant get it to work if i record the tune sweeps first

nice tips guys, gonna try both mikolo.
what's your latency like when u do that nym?

joeybells wrote:nice tips guys, gonna try both mikolo.
what's your latency like when u do that nym?

hes talking about filters applied to audio thats already been tracked. your latency will be whatever latency your asio sound card is set to. but this implies you are using a computer, so your mpc isnt an all in one solution at this point.

any mpc makes for a very limited all-in-one!!

with the utmost sincerity and mucho respect , what does a VST have to due with MPC?. the DAW is not there to play band-aid. MIDI control of DAW parameters and functions, and integration of hardware into DAW setups is real old news, in fact a booming industry . ..

back on topic..

from OS2 to OS2XL the q-links have been crippled, as well as the mixer automation. we all use our mpcs differently,some of us differently each day. however i feel that crippling q-link is more harmful to [my] workflow than crippling mixer automation, (as the majority of my beats get tracked out into logic and turned into apple loops i dont need the mixer automation as much as if i did live performances with the mpc, or used in instead of a DAW, like the old days, with a bunch o synths hooked up and mpc as master..aka "live" these days ).

using the 2 qlinks on the front panel to have control of 2 parameters is a HUGE workflow accelerator. i cannot imagine being a 2500 owner and using just 1 out of 4 qlinks..?!?!


i think what we're seeing here is a necessity to UNIFY the necessary and possible features of the 2 last jjos's into a final hybrid version that we all pay for one more time.

that brings us(JJOS user) to define necessary, and them(JJOS developer) to define possible .

theres been a lot of rah rah rah about everything here about whats POSSIBLE..
i been seein the quanta for three things underneath everybodys complaints the most:
1qlink,
2automation,
3simult.

lots of other people might see a different quanta based on their own personal feeling.

possible is empirically stated , ie; developer says: "SIMULT causes too many bugs too be possible anymore", or hinted at through perceived information dissemination outlets of the developer, ie, beta users like the one named NYM... [kinda quoted,didnt look the exact post] " JJ's gonna bring back the automation in XL"

i guess SIMULT is dead. is automation dead? is qlink dead? whatever the situation , hiphop is NOT dead.

answer with equal respect and sincerity: contained in your own quote!

what does a VST have to due with MPC?... MIDI control of DAW parameters and functions, and integration of hardware into DAW setups is real old news, in fact a booming industry

ccs allow more power and flexibilty than qlink realtime in all instances, outputs willin - and better yet you even use ccs with qlink NOTE ON stuff in the mpc.

story short, ccs are very very pertinent to this conversation, as they really are the workaround to the qlink dilemma in os2xl, and the qlink scenario in os2/os1/freejj/akai os

i agree with nym. but i also have massive respect for mr murda.

jacky you deserve a bigger and better mpc than the 1k

After a couple of days automating stuff via cc slider,
I can confirm it to be the way forward.
Took alot of messing about to get my latency judggle between midi and audio
working, but it's all good. if i use Logic.... Reaper on my mac is all over the shop, and so is Ableton Live!!
I've said this before but I'll say it again. Logic + Emagic MT4 or AMT8 = supertight midi.

i've never had trouble with latency in reaper, but reaper beta 6 (for mac/pc) announces major midi timing improvements.