Garageband 3/audio units odd behaviour
Garageband 3/audio units odd behaviour
- Subject: Garageband 3/audio units odd behaviour
- From: "Muon Software Ltd - Dave" <email@hidden>
- Date: Tue, 6 Feb 2007 14:40:47 -0000
- Importance: Normal
Dear list,
I'm testing a PPC audio unit we're developing for a client in as many hosts
as possible and have come across something odd specifically in Garageband 3.
The AU in question is built from the same code as the VST and Standalone
versions of our product and assumes that there is a separate audio and GUI
thread in all hosts. Because of this assumption, in some cases when the user
alters certain settings in the GUI we simply make a note of that request and
leave it down to the next render cycle when it would be thread-safe to act
upon that request.
What seems to be happening in GB3 (but not in any other AU host tested) is
that the audio rendering thread doesn't seem to start when the application
is first loaded, which seems to break our plugin in some new and interesting
ways.
So far the only work arounds that I've found to get the the audio thread to
start running are:-
1. run the transport or...
2. open the musical typing keyboard or piano keyboard window and play a note
or...
3. Show editor and click in the vertical piano keyboard on the left side
Is this normal behaviour? Any suggestions?
Regards
Dave Waugh
Muon Software Ltd
www.muon-software.com
_______________________________________________
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