You are here

qjackctl messages/status conky configuration

I'm trying to configure my Conky build to display some qjackctl info such as set (not supposed) interface, samplerate, buffersize, nperiods as well as system messages and last xrun (which could also just be transport time since i have that set to time since last xrun) and I'm having trouble understanding where to safely and reliably get this from.

I tried jack_samplerate for instance, which works, but every time Conky queries this, qjackctl is pinged as if there is a patch bay change. lots of queries equals lots of patch bay change spam in my qjackctl messages window. Also, jack_* doesn't have all the info I need anyway.

I also tried looking around for various logs, but none really are the proper solution. Everything I do need is in the qjackctl messages/status window, so how can I reach those files to parse them and extract the info I need?

Thanks

Forums: 
rncbc's picture

the messages log file is configured under Setup > Options > Logging, of course you set your own path.

if you run the jack d-bus enabled service you may also look into ~/.log/jack/jackdbus.log (note that this also goes into qjackctl:Messages log too, whether applicable).

byee

Thanks bud.

I was able to integrate the messages log into Conky, looks good. I knew about the Setup>Options>Logging feature, but for some reason when I tested previously, it did not give me the output I wanted. Now it looks good.

I'm still looking for a place to reliably get active sample rate, buffersize, periods as well as time since last xrun. Currently I'm using ~/.config/rncbc.org/QjackCtl.conf and filtering for the desired info in Conky, but I'm still not certain these are reliable system values. I'd like to find the place where the system tells you what these parameters currently ARE, not what they are supposed to be set as, perhaps I'm wrong about that and QjackCtl.conf is just as reliable. Where is the status window getting that parameter info from, or are they straight system calls?

I tried running strace on Qjackctl, but I had a hard time deciphering where any potential filesystem calls were pulling that data from.

rncbc's picture

well, all those stats, as in the qjackctl status tab, are computed by qjackctl itself, no other by having realtime access to the JACK API, programmatically that is, as a regular client.

sorry to tell, you won't have access to any of those but watching (visually with your own eyes:)) over the status pane or the main window; that information is not poured anywhere else but the screen :/

byee

Gotcha, thanks for the info.

Add new comment