Skip to content
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

Closed
jackmau opened this issue Mar 1, 2021 · 6 comments
Closed

Add "<This>" FX selector #186

jackmau opened this issue Mar 1, 2021 · 6 comments
Labels
enhancement New feature or request high priority

Comments

@jackmau
Copy link

jackmau commented Mar 1, 2021

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

@jackmau jackmau changed the title Realearn trying to be _too_ smart when making mappings project-independent Realearn trying to be too smart when making mappings project-independent Mar 1, 2021
@helgoboss
Copy link
Owner

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).

@helgoboss helgoboss added the enhancement New feature or request label Mar 1, 2021
@jackmau
Copy link
Author

jackmau commented Mar 2, 2021

Yes, this workflow enhancement is at the moment pretty much tailored to the "Auto-load preset: Depending on focused FX" use case.

Of course and indeed, I have been experiencing the issue exactly while trying this mode.

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).

Sounds even smarter than I originally envisioned

@helgoboss
Copy link
Owner

Yes, this workflow enhancement is at the moment pretty much tailored to the "Auto-load preset: Depending on focused FX" use case.

Of course and indeed, I have been experiencing the issue exactly while trying this mode.

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.

@jackmau
Copy link
Author

jackmau commented Mar 3, 2021

yes @helgoboss, I was trying to be original with the issue name, but that makes more sense

@helgoboss helgoboss changed the title Realearn trying to be too smart when making mappings project-independent Make it possible to use "Auto-load preset" in combination with conditional activation Mar 3, 2021
@helgoboss
Copy link
Owner

This could also need #241

@helgoboss
Copy link
Owner

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:

  1. Provide a <This> FX selector which automatically refers to this ReaLearn instance (sounds nice because it's analog to the track selector <This>).
  2. 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).

@helgoboss helgoboss changed the title Make it possible to use "Auto-load preset" in combination with conditional activation Add "<This>" FX selector Mar 21, 2021
helgoboss added a commit that referenced this issue Mar 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request high priority
Projects
None yet
Development

No branches or pull requests

2 participants