Reaper Last Touched Parameter Automation Not Working Well?

[Hexspa]

Hi. Trying to do a project. When I use reaper's Show Last Touched Parameter option in the automation menu, Melda doesn't seem to be responding well. I can get it to work but I don't know how. I just start flipping things then it works after a minute. Not sure what's going on.

I also got a click when automating TurboEQ's HPF on the master track down to OFF from a higher value.

EDIT: It's not just Melda. I tried it with a parameter from Sonimus and the lane didn't even show up. For this reason, I've also posted about it in the reaper forum. Restarting reaper reenables the functionality.

Anyone have this issue?

EDIT2: May have been caused by a buggy VST (non-Melda). Will update if the issue returns.

EDIT3: Still happening. Try automating MUtility Gain in reaper. See if it's immediately responsive. It isn't for me.

[Hexspa]

anybody in reaper having automation issues?

[Tyrs]

anybody in reaper having automation issues?

All good here with 6.36.

[Boone777]

TurboEQ HP Works in MXXX Reaper 6.38

[Hexspa]

I think it has something to do with the mousewheel. If I click-drag the parameter, the automation lane works fine. If I mousewheel it, the automation doesn't respond.

Nope that's not it either. Just seemingly randomly, I won't be able to automate the gain parameter in MUtility when using the Last Touched feature in reaper.

Weird. I'll update if I can find a consistently reproducing workflow.

[jan-sandahl]

anybody in reaper having automation issues?

Well, I do. And I wonder if it's a Reaper thing, Melda thing - or both.

In MSF, right-clicking a parameter brings up a Melda menu: Default value, Lock, MIDI Learn etc.
When I touch a parameter, it is not recognized as a last touched parameter n Reaper, and I just find an unhelpful mega-long parameter anonymus list (Param 1, Param 2 etc)

In other Melda plugins outside of MSF, when right-clicking, I get access to Reapers menu with last touched parameter, and all the options to add track envelope etc.

This changed quite recently, in my mind.

I recenly also switched to an AMD RX 7600 graphics card recently, and I am not used to their settings yet. Always used a Nvidia until now. I noticed in one instance it could grab shortcuts for its own app in Windows, but managed to turn that one off at least.

[jan-sandahl]

Hmmm... It seems hooking up a parameter to a multiparameter is necessary?

[Hexspa]

Still having issues? I forgot about this thread. Lately, everything seems to be working, though I might've resorted to MP use before.

[jan-sandahl]

Yes, in separate plugins outside of MSF it's much simpler and intuitive. No no need for going through MPs.

[jan-sandahl]

In Reaper...

Left: Right clicking on MSF Filter Freq.
Right: Right clicking Dry/Wet in MFilter, as a separate track plugin in Reaper.

msf-vs- mfilter.png

[Held]

In Reaper...

Left: Right clicking on MSF Filter Freq.
Right: Right clicking Dry/Wet in MFilter, as a separate track plugin in Reaper.

VSTs have to report their automateable parameters at startup. Since MSF doesn't know in advance what you're going to add, it can't report it. So it reports the multi-parameters and you can then assign something to them.

This is how it works for all modular plugins.

[jan-sandahl]

Ok, I'll try and remember that.