Disable Midi CC and only use envelopes/automation

[keaton]

Hello,

Have been some reading up on Midi CC vs envelopes to control VST instrument parameters recently (This thread and this thread have been helpful) and I am thinking i'd just like to keep instrument controls to Reaper's automation envelopes and ditch CC completely. What's the best way to have it so that by default all VST instruments' CC mappings go to envelopes instead but then don't record duplicate data in midi items as CC lanes?

Eg: I have some Spitfire Audio labs that have the VST's 'Dynamics' fader mapped to the modulation wheel by default. Though I can map the mod wheel to that parameter as a Reaper envelope, it is also recording the same input as midi CC data which is causing conflicts. Hope this makes sense, it is quite complicated stuff to express!

Thanks for help.

[mschnell]

Why ????

The ModulationWheel does send Midi CC so same can be easily recorded in a track together with the note events.

You should disable "Control" in the midi device setting (that is the default), as supposedly this creates the "conflict" you talked about. ("Control" send data to the global "ReaperControlPath" which is a rather complex issue.)

????
-Michael

[keaton]

Originally Posted by mschnell

Why ????

The ModulationWheel does send Midi CC so same can be easily recorded in a track together with the note events.

You should disable "Control" in the midi device setting (that is the default), as supposedly this creates the "conflict" you talked about. ("Control" send data to the global "ReaperControlPath" which is a rather complex issue.)

????
-Michael

Thanks for the reply. Not seeing that option I'm afraid.

[mschnell]

Preferences -> Audio -> Midi Devices -> your appropriate device

uncheck "enable Input for Control Messages".

(The text is very misleading. It should read "Enable Input to Reaper Control Path". )

-Michael

[mccrabney]

Originally Posted by mschnell

Why ????

because editing CCs across multiple adjacent MIDI items is inferior to using razer edits to sculpt Arrange-screen automation.

What's the best way to have it so that by default all VST instruments' CC mappings go to envelopes instead but then don't record duplicate data in midi items as CC lanes?

use JS, VST, or some other MIDI pre-processing to route your MIDI so that CCs don't end up getting recorded onto your VST tracks. instead, they should be routed to a MIDI input that REAPER has enabled for control messages. then, instead of using "record" to record automation, you'll have to use REAPER's automation record modes.

don't forget to trim off the unrecorded "return" content that REAPER addends to every automation recording, which brings your automation recording back to its "default" value without asking

[keaton]

Originally Posted by mschnell

Preferences -> Audio -> Midi Devices -> your appropriate device

uncheck "enable Input for Control Messages".

(The text is very misleading. It should read "Enable Input to Reaper Control Path". )

-Michael

Thanks for the reply but this doesn't seem to do anything. Mod wheel still affecting VST paramenters.

Originally Posted by mccrabney

because editing CCs across multiple adjacent MIDI items is inferior to using razer edits to sculpt Arrange-screen automation.



use JS, VST, or some other MIDI pre-processing to route your MIDI so that CCs don't end up getting recorded onto your VST tracks. instead, they should be routed to a MIDI input that REAPER has enabled for control messages. then, instead of using "record" to record automation, you'll have to use REAPER's automation record modes.

don't forget to trim off the unrecorded "return" content that REAPER addends to every automation recording, which brings your automation recording back to its "default" value without asking

Thanks. "use JS, VST, or some other MIDI pre-processing to route your MIDI so that CCs don't end up getting recorded onto your VST tracks" is something I'll have to look into. Am still learning the many intricacies of Reaper so hopefully will get there in time. Thanks again.

[mschnell]

Originally Posted by keaton

Mod wheel still affecting VST paramenters.

So the Midi messages are coming in via the track, and the VST directly receives them and the parameters internally are affected by that and not by "DAW Parameter Modulation". Thus Reaper is not involved at all.

There are lots of "Midi Filter" plugins (in the Reaper stock Plugins and in ReaPack) that can be used to modify the Midi stream if you want to do that.

-Michael

[keaton]

Originally Posted by mschnell

So the Midi messages are coming in via the track, and the VST directly receives them and the parameters internally are affected by that and not by "DAW Parameter Modulation". Thus Reaper is not involved at all.

There are lots of "Midi Filter" plugins (in the Reaper stock Plugins and in ReaPack) that can be used to modify the Midi stream if you want to do that.

-Michael

Ok thanks will check that out.