Re: [Jamin] ardour export + jamin

[Kees v. V. <kee...@gm...>]

Hi Jack,

Thanks for the quick reply and instructions. I'll try to do that later 
tonight.

My .jackrc contains: /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p64 -n4. 
So indeed 64. I minimized that to get a minimum latency without xruns 
(but without thinking about it).

I did some stderr logs of the cnt that the ring buffer write did and the 
nbytes, and most of the time it was 1 byte short, so cnt=255 and nbytes=256.

Thanks,
Kees

-------- Original Message --------
Subject: Re: [Jamin] ardour export + jamin
From: Jack O'Quin <jac...@gm...>
To: Kees van Veen <kee...@gm...>
Date: Wed Jan 13 2010 17:53:55 GMT+0100 (CET)
> On Wed, Jan 13, 2010 at 10:32 AM, Jack O'Quin <jac...@gm...> wrote:
>   
>> On Wed, Jan 13, 2010 at 2:40 AM, Kees van Veen <kee...@gm...> wrote:
>>     
>
>   
>> If you can reproduce this error, please configure your system to take
>> a core dump (ulimit -c unlimited), trigger the failure, then print the
>> gdb stack traceback for all the jamin threads:
>>
>> gdb> thread all apply bt
>>
>> Then, please send the output to this list, along with your JACK
>> parameters (period, etc) and any other interesting facts you can think
>> of.
>>     
>
> Kees,
>
> I just read the long thread about this from the Ardour site.  The
> process thread aborts exactly where I expected from your description.
> But, I'd still like to know where the other threads were at that time.
>
> Is your JACK period less than 256 frames?  What happens if you use a
> larger frame size (at least 256)?  Does the problem go away then?
>
> Depending on what we discover, I may ask you to try some different patches.
>
> Regards,
>