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

Cannot unload mod-monitor #72

Open
riban-bw opened this issue Dec 21, 2023 · 5 comments
Open

Cannot unload mod-monitor #72

riban-bw opened this issue Dec 21, 2023 · 5 comments

Comments

@riban-bw
Copy link

Usint jack_load mod-host creates a jack client called mod-monitor and automatically connects its audio outputs to system playback ports. When jack_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.

@falkTX
Copy link
Member

falkTX commented Dec 21, 2023

mod-host as internal client is not meant to be unloaded, I do not expect that to really work tbqh

@riban-bw
Copy link
Author

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?

@falkTX
Copy link
Member

falkTX commented Dec 21, 2023

the client that remains is not mod-host, but mod-monitor. so you might be able to "jack_unload mod-monitor", not sure.
mod-host is surely not being nice and leave some stuff behind on cleanup. PRs welcome :)

@riban-bw
Copy link
Author

I tried unloading mod-monitor but it fails - probably because it wasn't manually loaded. I will try to find time to investigate but...

@falkTX
Copy link
Member

falkTX commented Dec 21, 2023

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
monitor client code is in its own subfolder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants