Ongoing AU View issues
Ongoing AU View issues
- Subject: Ongoing AU View issues
- From: Robert Grant <email@hidden>
- Date: Tue, 15 Jun 2004 10:33:08 -0400
I'm concerned that there are a bunch of AU Carbon views out there that
don't seem to function in the expected manner. The AUValidation suite
is excellent for reigning in wayward AU engines but there's nothing to
check on the view side of things.
Now perhaps this is a Carbon in Cocoa issue - but there are a bunch of
plug editors out there that give GarageBand, Numerology, Rax and
SynthTest trouble.
The CocoaAUHost doesn't help in this case because it only hosts Cocoa
UIs and presenting Carbon UIs is left as an exercise for the developer
- and I quote:
" if (!viewBundlePath || !viewClassName) {
// If we get here, the audio unit does not have Cocoa UI,
and we don't have a default UI.
// An ambitious app would display the (potential) Carbon UI
in a separate window.
// See "Integrating Carbon and Cocoa in your application"
--
<
http://developer.apple.com/documentation/Cocoa/Conceptual/
CarbonCocoaDoc/index.html>
"
We're trying to be "ambitious" and we are succeeding most of the time.
But it seems that the high value AUs (and typically the ones that don't
have a demo to test with) are making our apps look bad.
So what's going to happen?
Thanks for listening,
Robert.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.