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
ReaLearn stays active when bypassing it via automation #659
Comments
I maybe 'mis-remembering', but I would like to add the comment that when ReaLearn is in the monitoring FX, bypassing manually leaves it active, while when in a track FX, it behaves as expected. Not an issue for me, just an observation |
I reproduced the issue. ReaLearn doesn't observe changes of its Bypass parameter so far. It only observes explicit enable/disable events. Internally, these are apparently two different things. I will fix this. |
It works with the "Bypass" parameter now, but turns out it doesn't yet work when the "Bypass" parameter is automated via envelope. |
REAPER doesn't call CSURF_EXT_SETFXPARAM for the special BYPASS parameter. I asked Justin if this is intended or not. Let's see. If it's a bug, it should be fixed on REAPER side. If not, I must resort to polling :/ |
Justin confirmed it will be fixed in REAPER itself. |
Manually bypassing ReaLearn works as expected but if it is bypassed via automation, it stays active and connected all the time even if reaper shows its bypassed state.
The text was updated successfully, but these errors were encountered: