[qjackctl-devel] Re: Fwd: qjackctl and the Xrun between brackets ()

[Rui N. C. <rn...@rn...>]

Alex,

>
> i send the below question about qjackctl to linux_audio_users
> mailinglist, but never got any response. since you're the author of
> Qjackctl and i'm still interested in the question, i send it to you
> personally. i hope you don't mind!
>

Of course not. I'm not subscribed to LAU so maybe that's why no one ever
responded to you ;)

>
>  --- Alex Timmer <mij...@ya...> wrote: > Date: Tue, 24 Feb 2004
> 13:15:22 +0000 (GMT)
>> From: Alex Timmer <mij...@ya...>
>> Subject: qjackctl and the Xrun between brackets ()
>> To: LAU <lin...@mu...>
>>
>> all,
>>
>> ever since i use qjackctl i wonder what is the difference between the
>> reported Xrun count and the count between brackets ().
>>
>> i.e. on its homepage http://qjackctl.sourceforge.net/ you can see a
>> screenshot where the Xruns are reported as 1(2). now, how many Xruns
>> have really occurred? 1? 2?
>>
>> i usually have no Xruns, but sometimes 0(1) and this is reported in
>> the
>> messages window, so i come to believe this is real(?)
>>
>> can someone please epxlain me the secret of qjackctl's Xrun
>> reporting.
>> thx, ALEX
>>
>

OK. There's really two XRUN counters:

1) The first number, without parentesis, is the number of XRUNs detected
by direct inspection of the server output messages (check on
Setup...|Options|Capture standard output). This detection is made by
regular expression matching on the captured output messages. It only
applies if you start the jackd server within qjackctl.

2) The second number, the one between the brackets, are the count of XRUNs
as reported from JACK API callbacks, since the moment qjackctl client
thread has started, which is always a bit later than the server. It
measures the same XRUN occurrence as every JACK client out there. This
counter is available even if jackd is started outside of qjackctl, which
then will be run as on client-only mode.

IMHO it doesn't really matter if these numbers may differ. If either one
increases, you probably had a XRUN. Period. Check on the Messages window
which one accured if not both. If the XRUN message line text it's colored
and timestamped you may be sure it was reported by the client callback way
(2).

Just pick the greater, and you'll be fine :)

Hope is it clear now.
-- 
rncbc aka Rui Nuno Capela
rn...@rn...