• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Garageband 3/audio units odd behaviour
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Garageband 3/audio units odd behaviour


  • Subject: Re: Garageband 3/audio units odd behaviour
  • From: "Sophia Poirier [dfx]" <email@hidden>
  • Date: Thu, 8 Feb 2007 10:04:14 -0500

On Feb 8, 2007, at 10:41 AM, Muon Software Ltd - Dave wrote:

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).

Yes and you already know why, since Stefan Gretscher already explained the architectural difference that allows for that in AU.


Sophia
_______________________________________________
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


  • Follow-Ups:
    • Re: Garageband 3/audio units odd behaviour
      • From: "Angus F. Hewlett" <email@hidden>
  • Prev by Date: Re:vDSP_conv very slow?
  • Next by Date: Re: Garageband 3/audio units odd behaviour
  • Previous by thread: Re: Garageband 3/audio units odd behaviour
  • Next by thread: Re: Garageband 3/audio units odd behaviour
  • Index(es):
    • Date
    • Thread