Subject: Re: [ecasound] pyeca
From: Kai Vehmanen (k_AT_eca.cx)
Date: Mon Dec 02 2002 - 00:12:19 EET
On Sat, 30 Nov 2002, smoerk wrote:
> 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?
Actually this should not happen. Commands are sent in order to the
ecasound engine and the engine never skips any incoming commands. Also,
the ECI command() function does not return until the command is actually
processed (ie. the return value always matches the last issued command).
If other situations occurs, then it's most probably a bug.
Hmm. I tested your example and it seemed to work ok here.
You could try inserting a "e.command("cop-status"); print e.last_string()"
to the inner loop of ecastest.py to see what is actually happening.
> # ./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
When I ran the tests, all operators had a final amp-% of 0.00...
-- http://www.eca.cx Audio software for Linux!
This archive was generated by hypermail 2b28 : Mon Dec 02 2002 - 00:08:29 EET