Subject: Re: [ecasound] cs-option -B:*
From: Jan Weil (Jan.Weil_AT_web.de)
Date: Fri Dec 12 2003 - 08:33:26 EET
Kai, I understand the concept of buffering profiles.
The question remains: If I set the buffering mode explicitly (using
cs-option) why isn't the status of the chainsetup affected immediately?
An example:
jan_AT_pompidou:~$ ecasound -c -i snd/mp3/loop_ifa.mp3
****************************************************************************
* ecasound v2.3.2 (C) 1997-2003 Kai Vehmanen
****************************************************************************
- [ Session created ]
------------------------------------------------------
- [ Chainsetup created (cmdline) ]
-----------------------------------------
ecasound ('h' for help)> cs-status
### Chainsetup status ###
Chainsetup (1) "command-line-setup" [selected]
-> Objects: 1 inputs, 1 outputs, 1 chains
-> State: valid (can be connected)
-> Options: -B:auto -n:command-line-setup -X -z:noxruns -z:nopsr
ecasound ('h' for help)> cs-option -B:rt
(eca-chainsetup-parser) Buffering mode 'rt' selected.
ecasound ('h' for help)> cs-status
### Chainsetup status ###
Chainsetup (1) "command-line-setup" [selected]
-> Objects: 1 inputs, 1 outputs, 1 chains
-> State: valid (can be connected)
-> Options: -B:auto -n:command-line-setup -X -z:noxruns -z:nopsr
^^^^^^^
I would expect either '-B:rt' here or the corresponding buffering
options instead.
Jan
Am Fre, den 12.12.2003 schrieb Kai Vehmanen um 02:07:
> On Wed, 10 Dec 2003, Jan Weil wrote:
>
> > interactively fine-tuning a chainsetup most options (e. g. 'cs-option
> > -b:64') are applied immediately (as 'cs-status' tells me).
> > A 'cs-option -B:rt|nonrt|rtlowlatency' does not take effect immediately
> > but after the chainsetup has been connected.
> [...]
> > Is there any valid reason for this behaviour and could this be changed?
>
> The '-B' option is a special case as it does not set the buffering
> parameters, but instead the buffering profile.
>
> The buffering profile (/mode) is separate from the actual chainsetup
> parameters. It is used when Ecasound has to determine optimal parameters
> for a given chainsetup. Normally Ecasound makes the selection itself, but
> this can be overridden by using '-B' (i.e. '-B:rt' -> use real-time
> settings even if there are no real-time inputs/outputs).
>
> Another option is to explicitly set all parameters and bypass all the
> above. You then need to set: 1) buffersize (number,-b), 2) raised
> priority (true/false,-r), 3) sched_priority (number,-r:X), 4) double
> buffering (true/false,-z:db), 5) db-bufsize (number,-z:db,X), and 6) max
> intbuf (true/false,-z:intbuf).
This archive was generated by hypermail 2b28 : Fri Dec 12 2003 - 08:28:35 EET