I'm using mod-host headless on a Raspberry Pi. It is started by systemd, and connections between it and other JACK clients are done with a framework of scripts.
During startup, there is a slight chance (maybe one in 20 or so) that jackd will produce xruns as follows:
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = mod-monitor was not finished, state = Triggered
...
These go on forever, hundreds per second. The audio performance of the JACK graph is not affected, though - no audible clicks, just a slighly higher CPU load which may be entirely due to the many log messages.
I have never seen this occur during normal operation, it either happens immediately after initially starting the JACK graph or not at all. I have seen it on Hifiberry soundcards as well as using the built-in PWM sound.
I started seeing this error since mod-monitor is activated by default. What could be the cause?
My particular problem would be solved with command-line option to disable the mod-monitor client...
I'm using mod-host headless on a Raspberry Pi. It is started by systemd, and connections between it and other JACK clients are done with a framework of scripts.
During startup, there is a slight chance (maybe one in 20 or so) that jackd will produce xruns as follows:
These go on forever, hundreds per second. The audio performance of the JACK graph is not affected, though - no audible clicks, just a slighly higher CPU load which may be entirely due to the many log messages.
I have never seen this occur during normal operation, it either happens immediately after initially starting the JACK graph or not at all. I have seen it on Hifiberry soundcards as well as using the built-in PWM sound.
I started seeing this error since mod-monitor is activated by default. What could be the cause?
My particular problem would be solved with command-line option to disable the mod-monitor client...