Re: [Jack-Devel] high sample rates cause unknown client xruns

On Tue, Feb 11, 2014 at 3:48 PM, Matt Flax <[hidden]> wrote:

>  On 12/02/14 01:29, Paul Davis wrote:
>
>
>
>
> On Tue, Feb 11, 2014 at 1:38 AM, Matt Flax <[hidden]> wrote:
>
>>  Hi there,
>>
>> I am experiencing problems with high sample rates when using jack.
>>
>> Whilst the driver is more then capable of reading data at high sample
>> rates, it seems that the client falls over when it tries to interact.
>>
>
>  you haven't stated the buffer size you're using (in units of samples and
> msecs). what you're describing seems entirely like what would be expected
> to happen when you require better scheduling latency characteristics than
> either your kernel or apps can deliver.
>
>
> I have tested with various period sizes, number of periods and so on.
> Whilst the driver doesn't indicate any xruns, the client does. What is your
> interpretation ?
>

i don't have one. the only error message I've seen thus far is:


$ jack_rec -f /dev/null -B 2048 -d 1 system:capture_1 system:capture_2
disk thread finished
jackrec failed with 977 overruns.
 try a bigger buffer than -B 2048.

I don't know the insides of jack_rec well enough to know what those
messages mean. Did you try "a bigger buffer than -B 2048" ?

1392154679.6277_0.ltw:2,a <CAFa_cKngWp9zsdR8fZ0xU+_uoo1BecS+MexYnns-322LtPnnNQ at mail dot gmail dot com>