• 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: more AU info and plugins (should be "I need to share data")
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: more AU info and plugins (should be "I need to share data")


  • Subject: Re: more AU info and plugins (should be "I need to share data")
  • From: Chris Rogers <email@hidden>
  • Date: Mon, 23 Jun 2003 13:11:12 -0700

Urs,

I think the idea is to avoid having the UI component talking to the AudioUnit
by directly calling internal C++ objects deep inside the AudioUnit. Instead
private/custom properties can be defined for the AudioUnit which the UI
component calls. Don't take this to mean that we're planning on having
components talking across different address spaces, etc. Remember,
that AudioUnitGet/SetProperty() deal with void* pointers anyway
so this wouldn't be possible.
Calling the C++ objects directly is simply not recommended by us --
that's all we're saying -- use property calls

Chris Rogers
Apple Computer


Am Montag, 23.06.03, um 14:53 Uhr (Europe/Berlin) schrieb Marc Poirier:

I don't know, I think that some people started saying it, and then no one
ever said it was wrong. Despite Chris's post, I have been reading this
list for a long time (since before there were AUCarbonViews) and
definitely don't remember anyone every conclusively saying that this
wasn't the case, but perhaps that just slipped past me. So I'm not sure
how definitively to take Chris' comments, but of course we don't have a
definitive answer for either way.

Well, I've gone through all mails I have on my @work machine (it lacks every Friday and Saturday), and couldn't find it. But I definately remember this having been mentioned twice, something like "direct referencing is highly dis-regarded".

However, Bill says something about using C callbacks instead of C++ object references here:

http://lists.apple.com/archives/coreaudio-api/2002/Oct/11/audiounithowtocommunicat.003.txt

I'll probably find the correct mail when I'm home (or I'll have to exchange the battery of my memory)...

Cheers,

;) Urs
_______________________________________________
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.
_______________________________________________
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: 
 >Re: more AU info and plugins (should be "I need to share data") (From: Urs Heckmann <email@hidden>)

  • Prev by Date: Re: MIDISendSysex?
  • Next by Date: Re: Properties (was: more AU info and plugins (should be "I need to share data"))
  • Previous by thread: Re: more AU info and plugins (should be "I need to share data")
  • Next by thread: compressor/expander AU for evaluation
  • Index(es):
    • Date
    • Thread