• 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: Audio Unit Properties that are CFStringRef
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Audio Unit Properties that are CFStringRef


  • Subject: Re: Audio Unit Properties that are CFStringRef
  • From: David Duncan <email@hidden>
  • Date: Sun, 04 Mar 2012 19:27:49 -0800

Your assumption is that because you receive a pointer type, that the pointer must be valid in both address spaces. If you were dealing with a plugin that exists in a foreign address space, then part of the communication would involve serializing and deserializing data to pass between the address spaces.

The warning is really more to do with passing a pointer from one plugin to another and to then use that pointer as further communication between plugins, as doing that assumes that both plugins are in the same address space. The key to the distinction is if you would expect changes in one plugin to appear immediately in the other without another API call - if you do, you've violated the rule.

On Mar 4, 2012, at 5:58 PM, Per Bull Holmen wrote:

> Hi
>
> The Audio Unit Programming Guide states that an audio unit and its
> view (GUI) is supposed to be able to work in separate address spaces.
> As it says: "For example, you pass data between the audio unit
> executable code and its view only by value, never by reference". But
> all string standard properties are supposed to be passed as
> CFStringRef. Doesn't this mean to pass the values by reference?
> Wouldn't this violate those same laws? Am I incredibly stupid for not
> understanding this.... isn't CFStringRef a pointer to a CFString? Is
> the AU view not allowed to read these values, maybe? But properties
> like kAudioUnitProperty_ParameterValueStrings sounds like the type of
> properties made for a view. Or, perhaps they are only there for the
> host to provide generic views? I'm sure I will feel incredibly stupid
> as you tell me the obvious explanation for this... :)
>
> Per
> _______________________________________________
> 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

--
Reality is what, when you stop believing in it, doesn't go away.
Failure is not an option. It is a privilege reserved for those who try.

David Duncan

 _______________________________________________
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


  • Follow-Ups:
    • Re: Audio Unit Properties that are CFStringRef
      • From: Per Bull Holmen <email@hidden>
References: 
 >Audio Unit Properties that are CFStringRef (From: Per Bull Holmen <email@hidden>)

  • Prev by Date: Re: Changing the way the OS responds to a USB DAC
  • Next by Date: Re: Audio Unit Properties that are CFStringRef
  • Previous by thread: Audio Unit Properties that are CFStringRef
  • Next by thread: Re: Audio Unit Properties that are CFStringRef
  • Index(es):
    • Date
    • Thread