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

Null target #578

Closed
vonglan opened this issue May 19, 2022 · 1 comment
Closed

Null target #578

vonglan opened this issue May 19, 2022 · 1 comment
Labels
enhancement New feature or request high priority realearn Related to ReaLearn

Comments

@vonglan
Copy link

vonglan commented May 19, 2022

My controller (APC20) sends 8 simulteneous CCs for some pads (no idea why they implemented it like that). I need one for the mapping, but want the other 7 to be "eaten" by ReaLearn so they do not reach the VST. It would be nice if there was a "Null operation" or "/dev/null" target, where the incoming source event would be "matched" and therefore removed from the signal flow, without any other effect.
In the user guide, you have a similar example, where you write:

... just pick a target that does not have any effect, for example an unused internal ReaLearn compartment parameter

@helgoboss helgoboss added enhancement New feature or request high priority labels May 20, 2022
@helgoboss
Copy link
Owner

True, makes sense.

@helgoboss helgoboss added the realearn Related to ReaLearn label Jul 25, 2024
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 realearn Related to ReaLearn
Projects
None yet
Development

No branches or pull requests

2 participants