[gmpi] Re: GMPI req's draft 1 for review.
- From: "Koen Tanghe" <koen@xxxxxxxxxxxxxxxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Tue, 7 Dec 2004 21:54:14 +0100
On Tuesday, December 07, 2004 10:12 AM [GMT+1=CET],
Tim Hockin <xxxthockin@xxxxxxxxxxxxx> wrote:
>> Req 64: "Plugins must be able to change their latency, when allowed by
>> the host"
>> I guess it is really needed to not allow the plugin to change its latency
>> whenever it wants, right? I can live with it, but there are cases where I
>> would really like it to be different. I currently have a VST plugin that
>> detects peak hights over the last x ms, and the "peak scan time" is a
>> parameter the user can set. This parameter influences the latency of the
>> plugin, and in VST, I can change that latency when the parameter is
>> changed (using setInitialDelay and then calling ioChanged). I can
>> understand though that this is must be a rather heavy burden on the host
>> side...
>
> How many hosts get your plugin right? :)
Yeah... Good question (and I'm not even 100% sure if the way I dod it is
"correct")
Of course, the reason why it is so, is that it's nowhere specified in the
spec how a host should handle it (or not at all). Let's make sure we do
better in the GMPI specs ;-)
>> Hope this helps,
>
> Nice work. Thanks. Changes made.
My pleasure!
Koen
----------------------------------------------------------------------
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: