AU Host problem
AU Host problem
- Subject: AU Host problem
- From: Dominic Mazzoni <email@hidden>
- Date: Wed, 29 Sep 2004 02:43:03 -0700
Hello all,
I've written an Audio Unit host app, and I'm testing various Carbon
GUIs. All of them seem to work well except for the five plug-ins from
Wave Arts (free trials available from http://wavearts.com/). With
those plug-ins, the GUI has some strange issues. At first nothing
happens when you click (and drag) on any of their knobs. But clicking
in their edit boxes does work. Then, after clicking in an edit box,
the next item you click on (including a knob that previously didn't
work) will work fine, but after that it will stop working again (until
you click in an edit box again).
Note that all other Audio Unit GUIs I've tried work fine - all of the
effects from Apple, and several other free and commercial demo AUs with
custom GUIs.
I'm hoping that someone will have a clue what's going on just by my
description of the behavior.
I suspect the problem may be that my application is using WaitNextEvent
instead of the new Carbon events. It appears that Wave Arts has
installed their own mouse event handlers. (I admit I'm a little weak
in this area - I programmed Mac OS 9 for years, but haven't written an
OS X app using Carbon Events yet, so I'm only vaguely familiar with how
they work...)
The complication is that my app is based on wxWidgets, so I'm stuck
with their event loop. To investigate this, I tried creating my own
event loop to see what's going on. Immediately after showing the
window containing the AudioUnitCarbonView, I tried going into an
endless loop, calling WaitNextEvent but ignoring the result. With
every other plug-in, the GUI is completely unresponsive. But with the
Wave Arts plug-ins, the GUI has exactly the same behavior as before
(although obviously the rest of my program stops responding).
Alternatively, if I handle mouseDown events in my loop, FindControl
returns 0. With every other plug-in, it returns a valid part code, and
I can call HandleControlClick on it to make it respond.
Is it possible that these plug-ins are only compatible with apps that
use the new-style Carbon events and RunApplicationEventLoop (as opposed
to WaitNextEvent)? wxWidgets is in the process of switching over, I
think, but in the meantime the stable version uses WaitNextEvent, so
I'm stuck with that for now. If that was the case, can anyone think of
a workaround?
Note that these plug-ins work fine with the sample AU host and other
commercial host apps that I've tried.
Thanks in advance for any help you can offer.
- Dominic
_______________________________________________
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