[gmpi] Re: Reqs 3.9. Time - opening arguments.1

  • From: "Koen Tanghe" <koen@xxxxxxxxxxxxxxxxxxx>
  • To: <gmpi@xxxxxxxxxxxxx>
  • Date: Fri, 6 Feb 2004 00:20:25 +0100

On Thursday, February 05, 2004 7:45 PM [GMT+1=CET],
David Viens <xxxdavidv@xxxxxxxxxxxxx> wrote:

>> Doesn't this approach effectively limit the resolution of tempo
>> changes sent
>> to a plugin?  I thought in this approach each processing frame had
>> only a single tempo, which means if the real tempo changes occurs
>> somewhere in the middle of the frame you won't render correctly.
> yes you are correct this is a limitation of VST.
> For GMPI the plugin that's "hooked" on a streaming Tempo map,
> should receive a vector of all bpm changes that will occur in each
> timeslice. (and markers on bar/timesig changes too of course)

Yes, that's how I see this too: per block of "samples to be processed" a
vector of timestamped (sample accurate oofset from start of block might be
enough) events. This is also how it's done with MIDI events in VST.

Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules:  Please stay on topic.  You are responsible for your own
words.  Please respect your fellow subscribers.  Please do not
redistribute anyone else's words without their permission.

Archive: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: