Re: [ecasound] Two chains is one too many (do I need bigger iron?)

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [ecasound] Two chains is one too many (do I need bigger iron?)
From: Kai Vehmanen (k_AT_eca.cx)
Date: Fri Jul 11 2003 - 00:18:35 EEST

On Wed, 9 Jul 2003, Joel Roth wrote:

> ecasound -a:1 -i:test.wav -o:alsahw,1,0,0 # no! -o applies to -a:default
> # instead of -a:1

Hmm, this should definitely not be the case. All objects
after "-a:1" should be added to the chain "1" unless another
"-a" option is given. Here's an example:

--cut--
|$ echo fs |ecasound -a:1 -i foo.wav -o alsahw,1,0 -c
****************************************************************************
* ecasound v2.2.4 (C) 1997-2003 Kai Vehmanen
****************************************************************************
- [ Session created ]
------------------------------------------------------
- [ Chainsetup created (cmdline) ]
-----------------------------------------
ecasound ('h' for help)> fs
### Audio input/output status (chainsetup 'command-line-setup') ###
Input (1): "foo.wav," - [DB => RIFF wave file]
 -> connected to chains "1": position (0.000/0.000) seconds.
 -> closed, audio format not available until object is opened.
Output (1): "alsahw,1,0,0" - [ALSA PCM device]
 -> connected to chains "1": realtime-device; position 0, delay 0.
 -> closed, s16_le/2ch/44100Hz, buffer 1024.
ecasound ('h' for help)> ---
ecasound: Exiting...
--cut--

... as you can see above, both the input and output are connected to
chain "1". 

-- 
 http://www.eca.cx
 Audio software for Linux!

New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Fri Jul 11 2003 - 00:17:52 EEST