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:41:10 -0000
- Importance: Normal
> 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 :-)
The snow here in London has frozen my brain - that was the VST version. But
it sort of illustrates the point: I can't think of a VST host that doesn't
run the audio thread continuously, with the exception of Sonar (which only
stops the audio thread if there's an overload, and even then only if the
user has specifically set that option). When you're using the same code base
for VST and AU, these assumptions get carried over - and for the most part,
most AU hosts operate in the same way.
Once GB3 does actually start the audio thread, it appears to run it
continuously anyway. So you have to wonder what the logic of not running it
when the app first initialises might be :-)
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