-
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
Bypass / wet-dry #35
Comments
It is a plugin responsibility (for a few reasons, it actually has to be for certain things to work properly). Though it would be possible to implement a fallback in jalv. I am not sure if I think it would be in scope, though. Jalv is meant to be a simple host that just turns a plugin into an application as directly as possible. |
Understood, thanks! I agree it might be out of the scope. If it helps, my use case is to interconnect several jalv instances together and quickly bypass one in the chain. Unfortunately, afaik, not every plug-in implements a bypass mechanism. |
I see. Honestly I'm not sure how I feel about people abusing Jalv to make a sort of modular in Jack in general, it's really not designed for that (and Jack isn't a particularly appropriate thing for it either). Leave the ticket open though, I'll think about it. Bypass would indeed be a lot easier, though it would click. |
FWIW, a set of buttons for On / Bypass / Mute would be useful for my use case. I have been trying out jalv on pipewire, and so far it's been smooth. A pwlv / pwlv-gui (just one version - gtk, gtk3, qt5 must be tricky to keep in sync) would be very useful. Pipewire's ability to have PA and jack co-exist makes your jalv very, very interesting. |
is there a way to bypass or adjust wet-dry levels of a plugin? or that is a per plugin responsibility.
Thanks!
The text was updated successfully, but these errors were encountered: