RE: Garageband 3/audio units odd behaviour
RE: Garageband 3/audio units odd behaviour
- Subject: RE: Garageband 3/audio units odd behaviour
- From: "Muon Software Ltd - Dave" <email@hidden>
- Date: Thu, 8 Feb 2007 10:27:32 -0000
- Importance: Normal
> Well, not so much an assumption, but more of a defined role.
> The defined role of the plugin, is to hook into an audio stream and
> do something useful with it. The fact that a plugin can
> exhibit a GUI
> at all, is really just fluff, to make it easier to modify the
> parameters of the processing.
I can take that onboard for an AU effect. But for an AU instrument or
generator I think there should be something in the spec that takes into
account the fact that audio could be generated without MIDI having been sent
to the instrument first by the host.
> It is certainly arguable that your feature of providing
> "browsing and
> previewing" is outside the established role of what an audio plugin
> should do, but let's not! ;-)
No, lets not go there....but I am tempted to add that it wasn't a problem in
Peak when I set up two of your machines on the Bias booth at NAMM to
demonstrate this particular AU for Jason, so at least Peak appears to share
a similar world view to me :-)
> So to get your feature, there is nothing stopping you from launching
> a new thread, and opening your own instance of the chosen audio
> output device, and playing out some sound. With a few tricks, you
> could even run the sound through the processing code of your plugin,
> so that the preview would be modified accordingly. What you
> would not
> be able to do, is to also hear the effect of any plugins that were
> down stream from yours, since their processing is associated to the
> host's thread, not yours.
There's nothing to stop me, no you are absolutely correct. I could easily
access the audio device myself and stream my previews to it.
However, many developers don't have the luxury of coding for one specific
host or even platform. In fact I would say that the vast majority of us
operating at a commercial level have to make the same code work well as VST,
AU, RTAS etc. To have to implement such a heavyweight hack just to get the
AU to work properly in GB3 is a direction I wouldn't want to take the code
in.
> BTW, you mention AU Lab as a host that doesn't exhibit the problem.
> But, if you click on the little waving icon, you can stop the audio
> processing thread, and indeed see the same problem there!
Of course, and you can do the same thing in Sonar on windows IIRC. You do
have to worry though about what the benefit of stopping the audio thread to
the user actually is however...
Kind regards
Dave
_______________________________________________
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