Subject: Re: [ecasound] update: ECI API
From: S. Massy (theanaloguekid@tak.net.dhis.org)
Date: Fri Dec 01 2000 - 07:56:39 EET
On Fri, 01 Dec 2000, Kai Vehmanen wrote:
>
> A short example using (b):
>
> --cut--
> # register a new event - event is produced whenever
> # engine state changes (running -> finished; not running -> running, etc)
> eci_command("event-add-engine-state")
> eci_command("start")
> # start waiting for events
> eci_poll()
> # we get here only if an event has occured
> # the next step is to get number of events available
> a = eci_events()
> while (a > 0)
> # get (and remove) the next available event
> b = eci_pop_event()
> print b
> --cut--
This looks like a simple yet good way to go, at least to me...
>
> Ok, you get the picture. But the important question remains: what kind of
> events are really needed?
Well, I would think mainly things akin to errors (or problems): Underruns,
resynchings, etc. (minor events)....failures, "finish", etc. (major
events)... Things that are not likely to be expected (or at least of which
you can't be sure when they happen, but to which you must react shortly and
efficiently.)
>
> --
> . http://www.eca.cx ... [ audio software for linux ] /\ .
> . http://www.eca.cx/aivastus ... [ aivastus net radio ] /\ .
>
> --
> To unsubscribe send message 'unsubscribe' in the body of the
> message to <ecasound-list-request@wakkanet.fi>.
>
-- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request@wakkanet.fi>.
This archive was generated by hypermail 2b28 : Fri Dec 01 2000 - 08:18:39 EET