Learn CC in FX Midi Stream

[mschnell]

IMHO it's very confusing that "Learn" in the [Param] menu of a loaded plugin always and exclusively sees the Reaper Control Path, while [Param] -> "FX parameter List" -> "Parameter modulation / Midi Link" always and exclusively sees the CC messages in the FX Midi Channel. You might be trying to "learn" a CC message from the Track itself (recorded or routed there), or you might want to explicitly assign a Reaper Control Path message to a parameter without a "learn" action.

Hence at least an additional option [Param] -> "learn local Midi CC" would be extremely appropriate and handy.

Additionally a way to select "Control Path" instead of a Midi Bus in the appropriate menu reached voa "Parameter modulation / Midi Link" would helpful, as well.

-Michael

[mschnell]

Anybody ?!?!
I think this is a very basic, tiny, and obviously missing feature.
-Michael

[Masi]

So if learning from track is enabled the first CC played from wherever the play cursor is will be linked to the parameter. Right?

And the point is use a pre-existing track with CCs to control a new plugin?

Masi

[mschnell]

1)Yep
2) this could be an example. Another would be to assign a CC coming from wherever to a parameter saving the pain to do [Parameter] -> "Parameter modulation Midi Link" -> ,,,,

I understand
- "Lean" assigns the next event in the Reaper Control Path onto the latest touched parameter
- "FX Parameter List" -> "Learn" assigns the next event in the Reaper Control Path onto a dedicated parameter

I'd like to also have
- "Learn CC in FX Midi Stream" assigns the next CC message (whatever Channel and Bus, but saving those together with the CC#) reaching this point in the FX chain onto the latest touched parameter
- "FX Parameter List" -> "Learn CC in FX Midi Stream" assigns the next CC message (whatever Channel and Bus but saving those together with the CC#) reaching this point in the FX chain onto a dedicated parameter

Obviously with that the naked "Learn" should be renamed to "Learn From Control Channel"

-Michael

[mpl]

I imagine a script, which:
See selected item
See edit cursor on that item
See what closer CC going after/before cursor
Note last touched parameter
Attach aka learn CC to that parameter

[mschnell]

I don't see how a script could detect a Midi messages at a dedicated location in the FX chain, which could be originated anywhere - by a plugin, routed from another track, track input ... (but I might be just ignorant).

-Michael