un.ku's Recent Posts
Hi there,
I'm using the CM version of Aalto, but I have also tested this in the most recent demo too. The MOD function doesn't seem to work for me unless the CC#1 data is recorded/non real-time.
My mod wheel is sending on CC#1 and the corresponding mod CC# in Aalto is also set to 1. It doesn't seem to work for live tweaks, but if I record that same mod wheel movement into my event editor (using FL Studio, btw), the recorded movement does modulate as expected.
It doesn't make much sense to me. I also saw this thread, where it seems like the guy had to arm his track to record too:
http://www.madronalabs.com/topics/2413-pitch-mod-1-2-not-working-in-live-9-02
So is real time mod wheel control not possible? Thanks for any advice.
Hi Randy,
Thanks for the reply. I wanted to give you an update in case anyone else asks.
I tried loading Aalto CM and Aalto Demo in FL Studio's Patcher and link the mod wheel that way and you are right it works fine although I have no idea why it would work one way but not the other. There must be a bug in FL's remote control settings or wrapper. I'll let them know.
EDIT: Scratch that. It's not FL.
It was the latency on my soundcard (M-Audio FastTrack C400). As soon as I reduced the buffer length/streamed buffer size to 128smp the mod wheel worked fine in real time. I guess FL's Patcher also circumvented this need somehow (maybe internal delay compensation).
Previously I always set it at 256smp since that is normally fast enough latency for me, but slightly better on CPU. Not like I get buffer underruns with 128smps, so I suppose it's silly I'm not using to lower latency setting anyway.
I'm surprised that such a small setting change should behave so much differently with just the mod wheel. It doesn't make a lot of sense to me because it's not like the other external modulators like key tracking or velocity behaved differently with the 256smp setting. But I guess it does. Problem solved.