Re: AUGraph deprecation

Interesting, seems the post Greg quotes got pulled. I wonder why. I'd have deleted the lot. Anyway, AQ, I remember you, you're always pulling stunts like this and it just clutters up the board.  My only question is (and I suggest you go away and think long and hard about this) is **why**?

Re: AUGraph deprecation

> *I'm* out of line? Yes. Very much so. Take it to a Usenet advocacy group, where ignorant and useless arguments are the norm. > (And again, why doesn't this *ever* happen in Microsoft's ecosystem?) Speaking as someone who has been a Windows developer for 25 years, it absolutely *does*

Re: AUGraph deprecation

Let us please watch language an tone! On Jul 13, 2018, at 4:25 PM, Admiral Quality mailto:a...@admiralquality.com>> wrote: And you should strongly consider not being planned obsolescence flogging asshole hypocrites. - AQ On Fri, Jul 13, 2018 at 4:22 PM, Doug Wyatt mailto:dwy...@apple.com>>

Re: AUGraph deprecation

Thanks for the info, Doug. That takes the pressure off a bit. The general feeling seems to be that AVAudioEngine is on a good way but „not quite there“ yet. Therefore more feature parity sounds exactly right. Could you guys put some more info up about real time manual rendering mode? Unless

Re: AUGraph deprecation

*I'm* out of line? Just... wow. And oh no, I might get removed from this list and (maybe, if I care to bother) have to sign up again from a different email? Horror of horrors! We don't all play the forced upgrade game, there are some honest business left out here and we don't make any money from

Re: AUGraph deprecation

Dude, seriously, chill. You’re way, way out of line with the Terms of Use, and basic professional behavior. https://discussions.apple.com/docs/DOC-5952 > Be polite. Everyone should feel comfortable reading Submissions and > participating in

Re: AUGraph deprecation

And you should strongly consider not being planned obsolescence flogging asshole hypocrites. - AQ On Fri, Jul 13, 2018 at 4:22 PM, Doug Wyatt wrote: > > >> On Jul 13, 2018, at 13:17 , Admiral Quality wrote: >> >> Meanwhile we can still run Windows software written in 1995 on their latest >>

Re: AUGraph deprecation

> On Jul 13, 2018, at 13:17 , Admiral Quality wrote: > > Meanwhile we can still run Windows software written in 1995 on their latest > OS. > > I can't wait to see you people go out of business. > > - AQ Deprecation doesn't mean removal. Carbon components have been deprecated for many

Re: AUGraph deprecation

Meanwhile we can still run Windows software written in 1995 on their latest OS. I can't wait to see you people go out of business. - AQ On Fri, Jul 13, 2018 at 4:15 PM, Doug Wyatt wrote: > I don't think we ever really knew when the deprecation be official. There are > yet a few things we want

Re: AUGraph deprecation

I don't think we ever really knew when the deprecation be official. There are yet a few things we want to add to AVAudioEngine for more feature parity, and we don't want folks to be seeing warnings until that's done. I can say that there is now an availability mechanism so that we can mark

Re: AUGraph deprecation

Arshia, Laurent, have you seen this WWDC session video which demonstrates AVAudioEngine's real time manual rendering mode? https://developer.apple.com/videos/play/wwdc2017-501/?time=942 Unfortunately the resources only provide

Re: AUGraph deprecation

Arshia, Thank you for clearing that up. On Wed, Jul 11, 2018 at 4:10 PM, Arshia Cont wrote: > Bartosz, > > Laurent was mentioning the installTapOnBus. Your published code would not > need that. You are just playing MIDI. You would be concerned if you had to > do custom real-time audio

Re: AUGraph deprecation

Bartosz, Laurent was mentioning the installTapOnBus. Your published code would not need that. You are just playing MIDI. You would be concerned if you had to do custom real-time audio processing on the audio output of your MIDI device (such as FFT analysis). Arshia > On 11 Jul 2018, at

Re: AUGraph deprecation

Thanks Benjamin for the precision. I thought that `installTapOnBus` was the successor of `RenderCallback`. For me it was not natural to mix old api like `kAudioUnitProperty_SetRenderCallback` in AVAudioEngine. So as Arshia said, I'm also looking for a way to use real-time processing with

Re: AUGraph deprecation

Interesting thread here! Anyone has achieved low-latency processing on AVAudioEngine? The RenderCallback seems natural to me (which is the good “old” way of doing it with AUGraph). But I’m curious to hear if anyone has done/achieved real stuff here with AVAudioEngine real-time processing and

Re: AUGraph deprecation

Laurent, `installTapOnBus` is not intended for realtime processing as a tap only provides the current frame buffer but does not pass it back into the signal chain. The documentation reads `Installs an audio tap on the bus to record. monitor, and observe the output of the node`. Although I

Re: AUGraph deprecation

Hi all, I'm interested in this topic since I've not found any information about it yet. Correct me if I'm wrong but AVAudioEngine is not able to lower than 100ms latency. It's what I see in the header file of `AVAudioNode` with its method `installTapOnBus`: @param bufferSize the requested size

Re: AUGraph deprecation

Benjamin and list, I double Benjamin’s request. It would be great if someone from the CoreAudio Team could respond to the question. Two years ago, after basic tests I realised that AVAudioEngine was not ready for Low Latency Audio analysis on iOS. So we used AUGraph. I have a feeling that

Re: AUGraph deprecation

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