Re: [Jack-Devel] jackd2+ardour3 - tracking down "JackActivationCount::Signal value = 0 ref = INT"

Le 15 juil. 2011 à 23:58, Robin Gareus a écrit :

> On 07/15/2011 06:38 PM, Stéphane Letz wrote:
> [..]
> 
>> But basically you are going to get *real* XRun error message in this
>> case right?
> 
> Yes. (BTW. Could one disable those as well? Does jack have a "quiet"
> mode that only logs fatal errors?)
> 

Jack2 has 3 kinds of messages printed by : 

- jack_error (real important ones..)

- jack_info : informative purpose

- jack_log: for debugging purposes...


BTW, how does jack1 displays XRun ? (or any  fatal errors) 



>>> This is only really relevant when DSP load is ~ 85-95%.
>> 
>> So I can make "JackActivationCount" report in verbose mode only, but
>> we agree that there still will be  XRun error message  right?
> 
> Yes; usually those x-runs are just a transient condition.
> 
> AFAIK, logging of Xruns by jackdbus is done in the non-RT thread which
> does not add to DSP load.
> 
> One could view this change as a workaround for apps that catch and print
> "JackActivationCount" messages (I guess even from the RT thread). Known
> susceptible apps are pure-data and ardour2/3 and there are possibly a
> few more.
> 
> It makes me wonder: Why are the Xrun messages exclusively in jack.log
> and the "JackActivationCount" messages exclusively in the application
> log? Here the latter do not show up in jack.log.
> 
> 
> Thanks,
> robin


This is in jackdbus right? How the info/log/error message are handled can be configurated with the jack_set_error_function/jack_set_info_function from jack.h API. You should look in how jackdbus configure them. And/or ask Nedko...

Stephane 

1310794152.12773_0.ltw:2,a <DDA39A97-E0A1-40F7-B3C5-E5C4DA8B9C5E at grame dot fr>