Re: [Jack-Devel] Debugging Jack Clients

Howdy,

On 09/06/2011 09:49 PM, ccrome wrote:
>         time to re-configure, and it seems to enter a continuous loop
>         where it
>         tries to configure the codec, then it gets an xrun, so it tries
>         again.
>
>
>     If this loop is happening... it's a side-effect of the Real Problem.
>     This is OMAP3, right?
>
>
> Why yes.  Yes it is.  What do you suspect the Real Problem is ?

*shrug*  Just gathering information.

>     Try setting larger buffers.  E.g. -p 4096 -n 4
>
>
> Will do when I get back to work.
> We're trying to keep latency very low though.

Low-latency debugging??  :-p

>     Even though you set the timeout at 50 seconds... it appears that
>     this error came because you didn't respond to an EVENT NOTIFICATION
>     within 2 seconds.  (The 2secs is not configurable.)  Event type 8 is
>     an xrun. Did you perhaps set an xrun callback?  If you did, I
>     recommend that you disable it while debugging.
>
>
> No, I didn't intentionally set an xrun callback. I do recall that I'm
> using a deprecated jack_init api (will take a look when I get back to
> work).  I don't recall the exact function call that was deprecated.

Probably using jack_client_new() instead of jack_client_open().  It's 
pretty easy to switch that over.

-gabriel

1315394788.10402_0.ltw:2,a <4E6754D1.5080908 at gmail dot com>