Automation enveloppe on Latch/write/touch + ReaLearn = haywire

Haywire might be a big of word ^.^ and I'm not sure if the problems comes from ReaLearn or Reaper itself... or this would be assumed as a normal behavior.

Anyhow : On a midi track, I have 4 instances of Vsts Loaded on the track FX chain which I bypass/activate (through ReaLearn) - with my launchpad.

When the track envelope is set to Trim/read, everything works fine. I can toggle between my vsts - the lights feedback on launchpad + the tick box in the fx chain act accordingly.

Problem arise when I want to record the automation during my Live performance. For example, on track 3 where I've got my piano Vsts, I would like to switch from one vst to another at a certain point in the song and I'd like to get transition recorded.

I've tried setting track envelope to Latch/write/touch mode and they pretty much all react wierdly with ReaLearn & controller (i.e not always consistent in regard to the light feedback when pressing the pads).

Mostly : I've noticed it reacts in a REVERSE way : when pressing the pad, I get a feedback light (in read mode, this would mean VST active, which is what we want) - Yet in latch/write/touch, it means bypass. If i press again, light goes away and now the Vst is active... You can see it's pretty confusing ;)

Now upon playing back my peformance, i've encounter wierd behavior again but this could be due to me forgetting to put the track back to read mode. It seems my controller gets confused as to what to do : Follow the envelope ? or stay in its current state.

In all cases, I noticed the light feedbacks doesnt follow along but the FX chain window does(my realearn mapping for Fx bypass works as expected and follow the envelope points ticking and unticking Vst box.

see screen shot below :

1) -see track 4 has 1 vst Ticked in Reaper : https://ibb.co/k5fTgy

https://ibb.co/nHQpod now see launchpad on track 4 (vertical row) has 4 pads light up as if all activated (in Trim/read mode, the pads would light up perfectly accordingly)

In this scenario, altought the lights weren't matching up, I was able to hear the ticked vst

2) - In this case where i've moved the Play cursor a little bit : https://ibb.co/cJ8LuJ I wasnt able to hear anysound although everything is ticked and it shows "normal" on the envelope. I thought I would hear 4 vsts at the same time like I would on trim/read

3) switching from Point 1) and Point 2) that i've just described (moving the cursor on timeline) don't make the lights follow on the launchpad altough a track goes from bypass to normal.

Finally, at this point, even switching the track back to trim/read mode doesn't really "reset" the launchpad and the track FX chain to act properly, I would need to delete all envelope, reset the track to trim/read and things go back to normal.

What do you think? Can this be adressed?

EDIT : In short, my main concern would be that the light feedbacks acts accordingly when in touch/write/latch mode. I have notice

As always, keep up the good work,

Nelligan

Comments (7)