Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By Sooty_G Wed Oct 01, 2008 8:55 am
arebee wrote:
legs mechanical wrote: more lfo routing options are a must.



this has got to be my most wanted new feature, a modulation table, where lots of sources can be assigned to lots of destinations.


cosign. what we also need is some more lfos. master lfos both synced to the sequencer (not just triggered by the pad hits) and also free running (not synced) that we can assign to a bunch of stuff.

would be nice to be able to 'draw' an lfo curve or whatever with the qlinks (qreal data) and then be able to assign that recorded qreal track to control more internal stuff other than what we can currently (which is tune, cutoff, resonance, level, and pan)

also, lfo to effects parameters!
User avatar
By arebee Thu Oct 02, 2008 3:24 pm
Sooty_G wrote:
arebee wrote:
legs mechanical wrote: more lfo routing options are a must.



this has got to be my most wanted new feature, a modulation table, where lots of sources can be assigned to lots of destinations.


cosign. what we also need is some more lfos. master lfos both synced to the sequencer (not just triggered by the pad hits) and also free running (not synced) that we can assign to a bunch of stuff.

would be nice to be able to 'draw' an lfo curve or whatever with the qlinks (qreal data) and then be able to assign that recorded qreal track to control more internal stuff other than what we can currently (which is tune, cutoff, resonance, level, and pan)

also, lfo to effects parameters!


thats what i reckon too - yeah - effect params as destinations & more lfo's as sources.

also note event definitions like those that are Q-link assignable - it would be good to have those as destinations too, ie: attack, decay, velocity, pitch etc, fx send, output route etc.

the list could really get silly but if JJ even tries a few big hitting favourites - id be most pleased