You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I very much appreciate the fact that realearn is enough smart to suggest you to relativise its assignments when saving a preset...but I found myself unable to use it as it does also apply to assignments which have the very same realearn instance as a target (typically to modify realearn internal parameters for paging/shifting behaviour). In my opinion it shouldn't change those, maybe identifying them as in #159 . An easy workaround is to have two separate realearn session, one that manages realearn parameters and another for the focused plugin, but that will force the user to lose a part of the benefit of controller projection.
Forgot to add I am on latest Realearn 2.4 and reaper 5.99
The text was updated successfully, but these errors were encountered:
changed the title
Realearn trying to be _too_ smart when making mappings project-independentMar 1, 2021
Summary so far: The todo in this ticket is to somehow make it possible to refer to this ReaLearn instance - no matter where it is. Because that's the precondition for conditional activation to be used in universally reusable presets. Ideas how to achieve that:
Provide a <This> FX selector which automatically refers to this ReaLearn instance (sounds nice because it's analog to the track selector <This>).
Maybe in addition provide a dedicated target for controlling the parameters of this ReaLearn instance (but I consider this as a nice-to-have convenience feature on top of this).