CC Automation Problem with ReaControlMIDI

[SymboliC]

Hi,

On my midi tracks I'm automating MIDI CC11 Expression with ReaControlMIDI.

The problem is, if the automation point shape is square, instead of linear, the value isn't followed by ReaControlMIDI, unless I start the piece from where the first square point is set, which is where the value changes.

This makes it inconvenient since I have to make it start from i.e. 20 bars before(where the value is changed) to hear how it sounds as it reaches at the actual point.

With the linear shape, I don't have such a problem, since it continuously changes the value and sets itself accordingly.

Thanks,

[Tod]

Originally Posted by SymboliC

On my midi tracks I'm automating MIDI CC11 Expression with ReaControlMIDI.

The problem is, if the automation point shape is square, instead of linear, the value isn't followed by ReaControlMIDI, unless I start the piece from where the first square point is set, which is where the value changes.

This makes it inconvenient since I have to make it start from i.e. 20 bars before(where the value is changed) to hear how it sounds as it reaches at the actual point.

With the linear shape, I don't have such a problem, since it continuously changes the value and sets itself accordingly.

Hi SymboliC, I don't use ReaControlMIDI, I use the CC lanes in the midi editor, so I'm not sure about this.

What happens if you add the same CC11 values to the envelope in the places where you'd like to start play. I'm talking
about just ahead of where you want to start play.

It works fine to do that in the midi editor using CC controllers.

[SymboliC]

Originally Posted by Tod

Hi SymboliC, I don't use ReaControlMIDI, I use the CC lanes in the midi editor, so I'm not sure about this.

What happens if you add the same CC11 values to the envelope in the places where you'd like to start play. I'm talking
about just ahead of where you want to start play.

It works fine to do that in the midi editor using CC controllers.

Hi Tod,

With linear points or curves or with linear increase, there isn't such a problem as I've mentioned before. It updates correctly.

I just want to make sure if this is a VST instrument specific problem or a Reaper problem. I found out that regardless of instruments/libraries, it always does the same. Below is the visual description of the problem.



I'll be glad if someone clarifies if this is a ReaControlMIDI or a Reaper issue in general or if there is an option with envelopes that I'm overlooking.

Cheers,

[Time Waster]

It's not a ReaControlMIDI issue, it's just how MIDI works. Each change in value is the result of a single MIDI message. Unless you receive the message, the value will remain the same as whatever the previous message was, which is why you have to scroll back 20 bars. As Tod suggests, add another data point just before the section you are interested in, if possible.

[SymboliC]

Originally Posted by Time Waster

It's not a ReaControlMIDI issue, it's just how MIDI works. Each change in value is the result of a single MIDI message. Unless you receive the message, the value will remain the same as whatever the previous message was, which is why you have to scroll back 20 bars. As Tod suggests, add another data point just before the section you are interested in, if possible.

Thank you for the clarification Time Waster,
I also thought that might logically be the case, just wanted to make sure.

Cheers,

[EvilDragon]

Yeah but this is host automation, not MIDI (it does eventually get sent as MIDI, but yeah). It SHOULD chase it even if you start from somewhere on that square segment.

EDIT: Actually trying this now over here, as I move the edit cursor around, I do see the value chased properly? All square points.