• 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: Ongoing AU View issues
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Ongoing AU View issues


  • Subject: Re: Ongoing AU View issues
  • From: Robert Grant <email@hidden>
  • Date: Tue, 15 Jun 2004 13:55:12 -0400

Sadly I've decided to alternate the years of my attendance and this is an off year. :-(

Hopefully all things will become clear in time....

But seriously - does this mean that things currently are hopeless? Or that users will have to upgrade to Tiger for things to work?

I'm sure you can't answer these questions... yet...

Robert.

On Jun 15, 2004, at 1:25 PM, William Stewart wrote:

(At the risk of repeating myself with an inane answer...) Come to WWDC :-)

Bill

On 15/06/2004, at 7:33 AM, Robert Grant wrote:

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.


--
mailto:email@hidden
tel: +1 408 974 4056

_______________________________________________________________________ ___
Culture Ship Names:
Ravished By The Sheer Implausibility Of That Last Statement [GSV]
I said, I've Got A Big Stick [OU]
Inappropiate Response [OU]
Far Over The Borders Of Insanity And Still Accelerating [Eccentric]
_______________________________________________________________________ ___
_______________________________________________
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.


References: 
 >Ongoing AU View issues (From: Robert Grant <email@hidden>)
 >Re: Ongoing AU View issues (From: William Stewart <email@hidden>)

  • Prev by Date: Re: Re: CarbonView newbie
  • Next by Date: Re: Re: CarbonView newbie
  • Previous by thread: Re: Ongoing AU View issues
  • Next by thread: CarbonView newbie
  • Index(es):
    • Date
    • Thread