RE: Audio Units - newbie questions
RE: Audio Units - newbie questions
- Subject: RE: Audio Units - newbie questions
- From: "Muon Software Ltd - Dave" <email@hidden>
- Date: Wed, 12 Oct 2005 15:46:21 +0100
- Importance: Normal
> Though that is definitely legitimate! Querying and applying settings
> is not about active DSP.
very much depends on the structure of the synth itself. We would have to
redesign a few things here and there to get a save state to work on a plugin
that hasn't been fully initialised.
> Sure, it will pass, but probably be more inefficient, unfortunately
> (though that depends, some AUs have nothing to do in Initialize).
> But if that's the only feasible solution for your AU, then you've
> gotta do what you've gotta do...
inefficient in what way? it might take a little longer to open, but
certainly no more than the VST version takes.
> You certainly can't depend on that. In fact, I doubt that's even
> common.
OK
> There is SetMaxFramesPerSlice(). This also will by default return an
> error if Uninitialized, I think.
Is there a SetSampleRate as well?
> Mmm, throwing out dialogs with no user interaction is really poor for
> more reasons than that. I hope that others don't think that "full
> initialization" = "throw out dialogs"!
Try running the Kontakt 2 demo in Cubase SX for a bit. That "You have XXX
days" dialog that halts Cubase's entire startup procedure until you click OK
is an excellent example. Or Reaktor 3 bitching about not having its dongle
plugged in, or....the list goes on :-)
> Right, of course: these are set by the host, and there's no way to
> do that until the host has received a reference to an instance of the
> plugin to work with.
Yup.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden