New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "<This>" FX selector #186
Comments
Yes, this workflow enhancement is at the moment pretty much tailored to the "Auto-load preset: Depending on focused FX" use case. Good point. It should detect that it itself is the target and be able to find itself even if it's at another position or has another ID or name (which it wouldn't at the moment). |
Of course and indeed, I have been experiencing the issue exactly while trying this mode.
Sounds even smarter than I originally envisioned |
Okay, sounds like your use case is to employ conditional activation in a preset that's auto-loaded. Is that correct? If yes, I will rename this issue accordingly. |
yes @helgoboss, I was trying to be original with the issue name, but that makes more sense |
This could also need #241 |
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:
|
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: