Nice. Btw I’m probably one of the more prolific user of this API that you are editor of. I read the whole document a number of times too. Nice work.
One feedback is to publicize more about the new Promise().then(afterRenderingBlock) that I’ve seen H. Choi put at the end of process function. Maybe even make it an optional callback hook. Sent from my phone > On Jul 6, 2023, at 4:53 AM, Paul Adenot <p...@paul.cx> wrote: > > > afaik released to the public in a regular update of iOS (and also on > desktop), see the release notes: > > https://developer.apple.com/documentation/safari-release-notes/safari-14_1-release-notes > (scroll a bit, it's near the bottom, search for AudioWorklet). > > Paul. > >> On Thu, Jul 6, 2023, at 13:40, Yisheng Jiang wrote: >> It’s been available as experimental feature, or default safari setting? >> >> Sent from my phone. >> >>>> On Jul 6, 2023, at 4:33 AM, Paul Adenot <p...@paul.cx> wrote: >>> >>>> On Thu, Jul 6, 2023, at 11:58, wrote: >>>> My personal opinion is basically this: >>>> 1. To do any kind of serious audio rendering, you basically must use the >>>> AudioWorkletProcessor class. >>>> 2. Apple has basically refuse to implement this. >>>> 3. Until now? https://yishengjiang99.github.io/fft-64bit/ works on my >>>> iPhone (I’m running the latest iOS everything) >>>> 4. Web audio saved? >>>> >>>> Sent from my phone >>> >>> I'm not entirely sure what you're asking, it has been possible to use it >>> for about 2 years on Safari on iOS (first available on iOS in Safari 14.5, >>> released 2021-04-26). It's been available long before that in other >>> browsers, mobile and desktop. >>> >>> I never heard a thing about Apple refusing to implement it, and I'm the >>> editor of the standard in which AudioWorkletProcess is specified. >>> >>> Sometimes things take time to be implemented correctly, and the priorities >>> of implementers of web browser engine don't always align with what we'd >>> like shipped and available universally. >>> >>> There's an increasing number of commercial products using the Web Audio API >>> (and countless free software and/or academic projects -- enough to warrant >>> a dedicated conference), and even though there's still a lot of work to do, >>> some of those applications are far from being toys. >>> >>> That said, if you feel the API is missing something, I encourage you to >>> browse https://github.com/WebAudio/web-audio-api/issues/ to see the list of >>> open issues and their status (planned, in discussion, specified but not >>> implemented yet, etc.), and possibly create a new issue. Our working group >>> meet every other week to discuss those. >>> >>> Best, >>> Paul. >
