• 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: "Muon Software Ltd - Dave" <email@hidden>
  • Date: Thu, 8 Feb 2007 15:59:45 -0000
  • Importance: Normal

> It's not an architectural difference per se - either architecture
> supports that approach (as does RTAS), it's simply that most
> implementations of VST - and indeed AU - happen not to work that way,
> most of the time.

...and therein is the essence of my point. GB3's behaviour is unusual in the
wider context.

In any case I have done what Stefan suggested and filed an enhancement
request. In the meantime, I'm going to take good note of Angus's suggestion
and put some defence into the code so it can detect if the audio thread
stops polling our render function.

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

  • Follow-Ups:
    • Re: Garageband 3/audio units odd behaviour
      • From: William Stewart <email@hidden>
References: 
 >Re: Garageband 3/audio units odd behaviour (From: "Angus F. Hewlett" <email@hidden>)

  • Prev by Date: Re: Garageband 3/audio units odd behaviour
  • Next by Date: Re: Open audio file from a buffer - not from file
  • Previous by thread: Re: Garageband 3/audio units odd behaviour
  • Next by thread: Re: Garageband 3/audio units odd behaviour
  • Index(es):
    • Date
    • Thread