Subject: Re: [ecasound] Buffersize 256 differs from JACK server's buffersize of 1024
From: Kai Vehmanen (k_AT_eca.cx)
Date: Mon Dec 02 2002 - 01:57:39 EET
On Mon, 2 Dec 2002, smoerk wrote:
> why do I sometimes get this ERROR and sometimes not? not really a
> problem, because -b:256 helps, but I couldn't figure out why ecasound
> sometimes uses 1024 and sometimes 256.
That's caused by the different profiles:
bmode-defaults-nonrt = 1024,false,50,false,100000,true
bmode-defaults-rt = 1024,true,50,true,100000,true
bmode-defaults-rtlowlatency = 256,true,50,true,100000,false
These are the defaults (can be overriden in ~/.ecasound/ecasoundrc).
If not explicitly specified with -B:profile, ecasound will select
the profile that best fits the current chainsetup.
The aim is to deliver the best possible out-of-the-box experience. For
example, the 'rtlowlatency' is only selected if a) the chainsetup benefits
from low-latency settings, and b) ecasound is run with sufficient
privileges. This is one of the big new features of 2.2.x.
> ecasound: ERROR: [ECA-CHAINSETUP] : "Enabling chainsetup: AUDIOIO-JACK:
> Cannot connect open connection! Buffersize 256 differs from JACK
> server's buffersize of 1024."
With JACK, the profile approach doesn't work as well, as JACK only allows
one buffersize to be used. This will be fixed by edi-31 - 'Support for
dynamic sampling rate and buffersize changes'. It will make possible to
change the buffersize on-the-fly (profile mechanism is still used to
select the defaults).
PS And in all circumstance you can still use -b, -z, etc options
to override any profile-based defaults (this keeps the ecasound
command-line interface backward compatible with older
-- http://www.eca.cx Audio software for Linux!
This archive was generated by hypermail 2b28 : Mon Dec 02 2002 - 01:53:44 EET