Thanks Corey, We used the example code to create our v3 AU. And it works fine.
However, the example code uses AVAudioEngine which provides direct access to a v3 AUAudioUnit object. Back in the real world (our existing AUGraph based code...) the v3 AU is found and instantiated, but there is only access to the v2 AudioUnit component instance pointer. I cannot find a way to set a custom named v3 AU property using the v2 API… p. > Op 20 apr. 2016, om 23:54 heeft Corey Walo <[email protected]> het volgende > geschreven: > > I believe this sample code exhibits the bridging mechanism: > > https://developer.apple.com/library/ios/samplecode/AudioUnitV3Example/Introduction/Intro.html > > -Corey > >> On Apr 20, 2016, at 5:40 PM, patrick machielse <[email protected]> wrote: >> >> We have developed a v3 AU for use on iOS 9. >> >> The new AU is managed by AUGraph, and is successfully instantiated. >> >> The problem is this: >> >> - AUGraph uses v2 API which can return AudioUnit pointers to the AU, not >> AUAudioUnit. >> - The v2 API only offers property access using IDs, not kvo (properties) or >> the parameterTree… >> >> I can't find any 'bridging' API that allows me to get the v3 AU from the >> AUGraph, or manipulate the properties and parameters of this v2 AU reference >> (no way to specify property IDs for v3 AUs?) >> >> The WWDC 15 presentations alluded to compatibility between v2 <> v3 hosts >> and AUs. AUGraph can instantiate the v3 AU, but for that to be useful I need >> to find a way to set properties and parameters on it… >> >> patrick _______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
