Subject: Re: [linux-audio-dev] LAAGA restrictions
From: Paul Davis (pbd_AT_Op.Net)
Date: Fri May 18 2001 - 16:18:53 EEST
>> The events that matter here are at the level of the engine. It can't
>> allow a plugin to process frames "beyond" an event's time until it
>> processes the event (possibly changing parameters, etc.) I don't see
>> how timestamping would help.
>
>I don't think I understand what you mean by event, I was thinking of
>something like MIDI clock count, or SMPTE sync.
An event would be anything that changed the state of the system.
>Why is it critical to prevent an app from responding to an event before
>its time?
Sorry, I wasn't very clear. You can't allow the plugins to do their
thing before the *engine* has processed the event. If you did, they
would be processing data using the old state of the system, which
should have been altered before they got busy.
Plugins can have their own event handling that only affects their own
state; its up to them to subdivide their process() call as they see
fit. Hmm, something tells me I just made a mistake.
--p
This archive was generated by hypermail 2b28 : Fri May 18 2001 - 16:53:01 EEST