Subject: [ecasound] file and device access (was: Re: A few bugs)
From: Kai Vehmanen (email@example.com)
Date: Thu Apr 26 2001 - 02:26:58 EEST
On Tue, 3 Apr 2001, S. Massy wrote:
> You're right. On a side note, it seems that ecasound allows files to
> be added as input even though they don't exist, is this a bug or
> a feature I cannot tell...
When configuring chainsetups. all audio objects are just _names_. Only
when chainsetup is connected (either implicitly, or explicitly by calling
'cs-disconnect') are files and devices actually accesses. Similarly, when
chainsetup is disconnected, ecasound closes all file and device handles.
This behaviour is especially important when using pipes as inputs and
outputs (multiple open-close cycles break pipe connections).
Only exception to this rule is when ecasound needs to fetch audio format
parameters. For instance to get format of a .wav file, ecasound must
access the audio file.
-- http://www.eca.cx Audio software for Linux!
-- To unsubscribe send message 'unsubscribe' in the body of the message to <firstname.lastname@example.org>.
This archive was generated by hypermail 2b28 : Thu Apr 26 2001 - 03:14:41 EEST