cop-status Was: Ecasound and the Vocoder.so LADSPA plugin

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

Subject: cop-status Was: Ecasound and the Vocoder.so LADSPA plugin
From: Mario Lang (mlang_AT_delysid.org)
Date: Thu Oct 31 2002 - 00:09:45 EET


Kai Vehmanen <k_AT_eca.cx> writes:

> On Wed, 30 Oct 2002, Mario Lang wrote:
>
>> I just discovered the vocoder plugin for LADSPA, and am now
>> wondering how I am supposed to use this with ecasound.
> [...]
>> The problem I'm having is the fact that the vocoder plugin needs
>> two audio inputs, the format and the carrier signal.
>
> ecasound -a:1 -i foo_mono.wav -o loop,1 \
> -a:2 -i carrier_mono.wav -o loop,1 -erc:1,2 \
> -a:3 -i loop,1 -o alsa,default -el:vocoder,3,0.5,0.5,0.5
>
> ... I'm not sure if the input files are in the right order,
> but in any case, this is the mechanism to use.
Quoting from a session with the latest cvs version, I noticed
that cop-status is slightly broken:

ecasound ('h' for help)> cs-add vocoder
(eca-controller) Added a new chainsetup with name "vocoder".
ecasound ('h' for help)> c-add formant
(eca-controller) Added chains: formant.
ecasound ('h' for help)> ai-add null
(eca-controller) Added audio input "null".
ecasound ('h' for help)> cop-add -el:analogueOsc,1,440,1,.1
ecasound ('h' for help)> c-add carrier
(eca-controller) Added chains: carrier.
ecasound ('h' for help)> ai-add null
(eca-controller) Added audio input "null".
ecasound ('h' for help)> cop-add -el:analogueOsc,3,880,.1,.1
ecasound ('h' for help)> -erc:1,2
ecasound ('h' for help)> c-select formant,carrier
ecasound ('h' for help)> c-selected
formant,carrier
ecasound ('h' for help)> ao-add loop,1
(eca-controller) Added audio output "loop,1".
ecasound ('h' for help)> c-add work
(eca-controller) Added chains: work.
ecasound ('h' for help)> c-selected
work
ecasound ('h' for help)> ai-add loop,1
(eca-controller) Added audio input "loop,1".
ecasound ('h' for help)> cop-add -el:vocoder,2,0.9,0.5
ecasound ('h' for help)> cop-status
### Chain operator status (chainsetup 'vocoder') ###
Chain "formant":
        1. Analogue Osciallator: [1] Waveform (1=sin 2=tri 3=squ 4=saw) 1.00, [2] Frequency (Hz) 440.00, [3] Warmth 1.00, [4] Instability 0.10Chain "carrier":
        1. Analogue Osciallator: [1] Waveform (1=sin 2=tri 3=squ 4=saw) 3.00, [2] Frequency (Hz) 880.00, [3] Warmth 0.10, [4] Instability 0.10
        2. Channel copy: [1] from-channel 1.00, [2] to-channel 2.00Chain "work":
        1. Vocoder: [1] Number of bands 2.00, [2] Band 1 Level 0.90, [3] Band 2 Level 0.50, [4] Band 3 Level 0.00, [5] Band 4 Level 0.00, [6] Band 5 Level 0.00, [7] Band 6 Level 0.00, [8] Band 7 Level 0.00, [9] Band 8 Level 0.00, [10] Band 9 Level 0.00, [11] Band 10 Level 0.00, [12] Band 11 Level 0.00, [13] Band 12 Level 0.00, [14] Band 13 Level 0.00, [15] Band 14 Level 0.00, [16] Band 15 Level 0.00, [17] Band 16 Level 0.00
ecasound ('h' for help)> ao-add null
(eca-controller) Added audio output "null".
ecasound ('h' for help)> cs-status
### Chainsetup status ###
Chainsetup (1) "command-line-setup"
 -> Objects: 0 inputs, 0 outputs, 1 chains
 -> State: not valid (cannot be connected)
 -> Options: -B:auto -n:command-line-setup -X -z:noxruns -z:nopsr
Chainsetup (2) "vocoder" [selected]
 -> Objects: 3 inputs, 2 outputs, 3 chains
 -> State: valid (can be connected)
 -> Options: -B:auto -n:vocoder -X -z:noxruns -z:nopsr
ecasound ('h' for help)>

i.e., there is a newline missing somewhere.

-- 
CYa,
  Mario


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

This archive was generated by hypermail 2b28 : Thu Oct 31 2002 - 00:06:49 EET