Q Link LFO parameters??

somebody please tell me there's a way i can assign one q link to lfo wave type and the other to lfo frequency. how hot would that be?? though i doubt it's possible...
when will we be able to just highlight the function we want the slider to control, like fully midi-mapped...that would be incredible

apart from aftertouch to lfo depth in OS2 , this is currently not possible im afraid.
in the future who knows, would be cool though for sure... that and a gazillion other things that JJ could do!

that would be so beautiful

i gues that before having that feature, the os would need to be dotted with true lfos, not envelope lfos which are actualy trigger each time you hit a pad.

mkl... wrote:i gues that before having that feature, the os would need to be dotted with true lfos, not envelope lfos which are actualy trigger each time you hit a pad.

cosign on this. would be very useful.

hopefully, this qlink control over lfos will be possible at some point when JJ starts implementing the midi cc stuff.

Sooty_G wrote:

mkl... wrote:i gues that before having that feature, the os would need to be dotted with true lfos, not envelope lfos which are actualy trigger each time you hit a pad.

cosign on this. would be very useful.

hopefully, this qlink control over lfos will be possible at some point when JJ starts implementing the midi cc stuff.

yeah i'd love a 'free' oscillating LFO [option of not re-triggering on note on], but its probably too hard for JJ/MPC1k...

still - having control over depth and rate would be very welcome here.
i've even been desperate for VEL>LFO RATE/DEPTH for years, cos then each pad/trig would have effect on its own LFO values - a much more sensible/achievable solution.

as for the above requests, it would be a mammoth task to tie controllers to any/all LFO's in each PROG - count them! - in fact its an insane request based on the way the LFO's are orientated in this OS.

there needs to be a bit more forethought before bleating on about such ideas.

no wonder JJ only does about 2-3 fixes a month, they're probably swamped with ridiculous proposals

arebee wrote:

Sooty_G wrote:

mkl... wrote:i gues that before having that feature, the os would need to be dotted with true lfos, not envelope lfos which are actualy trigger each time you hit a pad.

cosign on this. would be very useful.

hopefully, this qlink control over lfos will be possible at some point when JJ starts implementing the midi cc stuff.

yeah i'd love a 'free' oscillating LFO [option of not re-triggering on note on], but its probably too hard for JJ/MPC1k...

still - having control over depth and rate would be very welcome here.

wasn't there a midi controller that had a built in lfo that would output it's value to any MIDI CC? if jj implements MIDI CCs to q-link, that may be possible, albeit in a round-a-bout sort of a way.

Mr modnaR wrote:

arebee wrote:

Sooty_G wrote:

mkl... wrote:i gues that before having that feature, the os would need to be dotted with true lfos, not envelope lfos which are actualy trigger each time you hit a pad.

cosign on this. would be very useful.

hopefully, this qlink control over lfos will be possible at some point when JJ starts implementing the midi cc stuff.

yeah i'd love a 'free' oscillating LFO [option of not re-triggering on note on], but its probably too hard for JJ/MPC1k...

still - having control over depth and rate would be very welcome here.

wasn't there a midi controller that had a built in lfo that would output it's value to any MIDI CC? if jj implements MIDI CCs to q-link, that may be possible, albeit in a round-a-bout sort of a way.

i have a BITSTREAM BS3X midi controller - it has a well programmable LFO, and can be assigned to virtually any CC#....is this the device u refer to?

yeah that rings a bell, well there you go, it's just a matter of waiting for jj to implement midi cc-> q-link!

so much of the things i am doing today involves waiting for jj to implement
midi cc => qreal data
midi cc => qlink note on data

even playing 'elliot takes E.T. for a bike ride' with your PT-01 as E.T.?

hahahahahahhaha

ouuuuch