Subject: Re: [ecasound] update: ECI API
From: janne halttunen (jhalttun@pp.htv.fi)
Date: Fri Dec 01 2000 - 14:56:33 EET
> --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--
>
> Ok, you get the picture. But the important question remains: what kind of
> events are really needed?
One simple case is the position-slider. Using the dump-commands it is not sane to update the visual represention of the audio position (the slider) too often.
ECI will undoubtedly speed things up, but there will still be the overhead of explicitly asking the position-information. In GTK there is this one nice func for
monitoring IO. If I put this listening a pipe feeding position-doubles to a simple reactive func updating the slider, I think we've reached the maximum possible
speed. (in the current context :)
jsh
-- 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 - 15:20:34 EET