Open AtmanActive opened 2 years ago
Curiously, this does work for FX parameters.
If I drive an FX parameter with a rotary encoder which was mapped in ReaLearn, then, that FX parameter indeed becomes a Last Touched parameter and the LED-meter-slider is working as expected.
So it seems that only selected track's volume, pan and width are excluded from this (for now, still need to investigate sends).
Sends (Track: Selected. Send #1, 2...) are working as expected.
Even selected track's volume is now working as expected. :-) (how did I miss that previously...)
The only thing not working as expected is selected track's pan and width.
The rabbit hole goes even deeper... When I touch a track's pan with a mouse, Last Touched does get assigned and works as expected. But not when driven via ReaLearn. When I touch a track's width with a mouse, Last Touched does not get assigned at all. Nor when driven via ReaLearn.
Hence, this looks like a bug/oversight.
Quite possible. I haven't touched the "Last touched" target for a long time nor used it.
Will check what can be done about it, but probably has to wait some time.
Hi,
So I have a few rotary encoders which I mapped to selected track vol/pan/width. All working as expected. Now I added a LED-meter slider touch MIDI device which sends CC events and listens to those same events for it's LED-meter (similar to a LED-ring rotary encoder but in the form of a slider). I mapped that one to Last Touched expecting that it will show/control any last touched parameter in Reaper, including the ones I'm driving with rotary encoders.
But that's not how it works. The LED-meter shows/controls only the last touched parameter mouse has touched. Bummer.
Is there a way to include ReaLearn's own touches in Last Touched? If not, would you consider adding such a checkbox for mappings?
Thanks.