CC mode mismatch between controller and Reaper?

[philcee]

My Xone K1 midi controller is mapped to control parameters in a VSTi synth and the synth responds perfectly fine. But when i want to record it to an automation lane, the little knob on the TCP panel that follows the automation as you turn a control, just jumps around in a jittery erratic fashion, indicating that the CC data is wrongfully interpreted.

Important detail: when i move the knob in the VSTi using my mouse, then the automation gets written correctly to the automation lane. So the issue must somehow originate from a CC mode mismatch between my controller and Reaper. First i had the controls assigned using the VSTi's mapping function, then I looked into using Reaper's learn mode on the FX window and selecting the different CC modes as i re-learned the control. Nothing seems to help, i get useless jitter on the automation lane.

PS i checked with another external midi controller (Edirol PCR 500) and it's the same CC mode mismatch (or what do you call it) problem. So somewhere i must be missing something. I thought recording automation was gonna be a breeze, an afterthought, sheesh...

[philcee]

Ugg, so i figured out that the sliders on the controller must be sending CC data which doesn't translate well to the automation lanes. The rotary knobs seem to jive better

Now if only it would actually record that data onto the automation lane - i see the correct automation lane, and it's active and armed, the little knob in TCP is even following my movements...

[mschnell]

"Automation" (I.e. e.g. paramter modulation). is a completely different thing than Midi CC data communication.
It's just "by chance" (i.e. programming of a specific plugin) if the same sound parameter reacts as well on Midi CC receive as on change of the (envelope) DAW parameter.
In reaper there are lot's of tools that can be used for conversions in appropriate cases.