Since it was mentioned in another email (thread) I’m giving this topic a bump. Would be great if someone at Apple, or anyone else in the know, could take the time to respond. The documentation at the link cited below still has no indication of deprecation. Will it come with one of the next Xcode Beta releases?
On another note I am really interested in how transitioning over to AVAudioEngine is working out for everyone. I know AVAudioEngine on iOS. What I am interested in is any macOS specifics or hardships. From my experience AVAudioEngine is relatively robust in handling multiple graphs, i.e. separate chains of audio units. I had some issues with the AVAudioPlayerNode connecting to multiple destinations in that scenario. Also connect:toConnectionPoints:fromBus:format: did not work for me as it only connected to one of the destination points. Anyone else experienced problems in that regard? Thanks Benjamin > Am 08.06.2018 um 16:59 schrieb Benjamin Federer <[email protected]>: > > Last year at WWDC it was announced that AUGraph would be deprecated in 2018. > I just browsed the documentation > (https://developer.apple.com/documentation/audiotoolbox?changes=latest_major > <https://developer.apple.com/documentation/audiotoolbox?changes=latest_major>) > but found > Audio Unit Processing Graph Services not marked for deprecation. The AUGraph > header files rolled out with Xcode 10 beta also have no mention of a > deprecation in 10.14. I searched for audio-specific sessions at this year’s > WWDC but wasn’t able to find anything relevant. Has anyone come across new > information regarding this? > > Judging by how much changes and features Apple seems to be holding back until > next year I dare ask: Has AUGraph API deprecation been moved to a later time? > > Benjamin
_______________________________________________ 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]
