-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Suggestion : ease target over time #635
Comments
Hi! It's a little bit hidden but this is already possible to some degree: #593 (comment) |
Ok thanks! I'm trying to simply delay a trigger, and I did this :
But is there a way to return "stop", after returning "x"? I did this, but does'nt seem optimal :
Also, it seems like
|
Mmh, I see the problem and what you would like to do. Unfortunately, the code in the transformation formula doesn't have any concept of a "sequence" ... like do "stop" after returning "x". It simply gets executed repeatedly and has access to the variables, no higher magic there. As you already found out ("doesn't seem optimal"): If you want to fire just once and then stop, it's unreliable to use the I think even with the In your particular case, the following formula might do the trick: For other more complicated cases, it might be cool to be able to do this: |
This is now possible! |
Hi,
First ReaLearn is incredible, and realy powerful! A huge thanks for your work!
Here's my suggestion : it would be awesome if ReaLearn could "ease" a target value over a period of time.
One simple usage of this would be that, on the press on a button, a fade-in or fade-out could be automated. The target value (track volume from x dB to y dB) could be reached in x milliseconds.
I managed to do something similar by activating a mapping that uses the "Reaper: timer" source (at 100 ms) with "Incremental button" mode. One of the downside of this is that there's no easy way to deactivate the mapping once the target value as been reached, and the timer will keep send the max value.
In BrainModular Usine, this is called a Data smoother (transforms abrupt value transition into more progressive transition).
The text was updated successfully, but these errors were encountered: