Subject: pyeca
From: smoerk (smoerk_AT_gmx.de)
Date: Sat Nov 30 2002 - 18:49:03 EET
I wrote a first short pyeca script and it is not too complicated to
understand how ecasound and pyeca works. :-)
I experienced one problem with pyeca. It seems that ecasound or pyeca is
not fast enough to catch every EIAM command, it just ignores them. Is
there a workaround to make sure that every EIAM command is handled by
ecasound?
### 3channel.ecs
# general
-B:rtlowlatency -n:play_chainsetup -X -z:noxruns -z:nopsr
# audio inputs
-a:1 -f:s16_le,2,48000 -i:1.ewf
-a:2 -f:s16_le,2,48000 -i:2.ewf
-a:3 -f:s16_le,2,48000 -i:3.ewf
# audio outputs
-a:1,2,3 -f:s16_le,2,48000 -o:alsa,default
# chain operators and controllers
-a:1 -ea:1.00
-a:2 -ea:1.00
-a:3 -ea:1.00
### ecastest.py
import time
from pyeca import *
e = ECA_CONTROL_INTERFACE()
e.command("cs-load 3channel.ecs")
e.command("cs-connect")
e.command("start")
for channel in range (1,4):
e.command ("c-select " + str (channel))
e.command ("cop-select 1")
e.command ("copp-select 1")
for volume in range (1,101,4):
e.command ("copp-set " + str (volume))
time.sleep (0.2)
e.command ("copp-set 0")
e.command("stop")
e.command("cs-disconnect")
e.command("cop-status")
print "Chain operator status: ", e.last_string()
# ./ecatest.py
Chain operator status: ### Chain operator status (chainsetup
'play_chainsetup') ###
Chain "1":
1. Amplify: [1] amp-% 97.00
Chain "2":
1. Amplify: [1] amp-% 0.00
Chain "3":
1. Amplify: [1] amp-% 0.00
This archive was generated by hypermail 2b28 : Sat Nov 30 2002 - 18:45:26 EET