-
Notifications
You must be signed in to change notification settings - Fork 55
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
Cannot unload mod-monitor #72
Comments
mod-host as internal client is not meant to be unloaded, I do not expect that to really work tbqh |
But surely if jack_load and jack_unload can load and unload internal clients then the internal clients should in fact load and unload? I am not too familiar with the behaviour of internal clients. Is it technically challenging to remove the client when it is unloaded? |
the client that remains is not mod-host, but mod-monitor. so you might be able to "jack_unload mod-monitor", not sure. |
I tried unloading mod-monitor but it fails - probably because it wasn't manually loaded. I will try to find time to investigate but... |
the code for this is in src/effects.c, there is a effects_init and effects_destroy(was it cleanup?), the monitor is loaded in the init but I guess issue is that it is not destroyed on the cleanup side |
Usint
jack_load mod-host
creates a jack client called mod-monitor and automatically connects its audio outputs to system playback ports. Whenjack_unload mod-host
is run, the mod-monitor client remains active and connected. There seems no way to unload mod-monitor client.Running on arm-32 OS (Debian based) on Raspberry Pi 4 (aarch64) using mod-host version: v0.10.6-532-g0d1cb54.
The text was updated successfully, but these errors were encountered: