Safari 14.5 Support

Hi there! First and foremost would like to thank you for the awesome project. It has been incredibly helpful. As you may know, Apple released major update to Safari a couple of days ago, which enables their experimental AudioWorklets by default. The problem is that they simply… don’t work. I am able to send and receive messages, but no logging is visible from inside the Processor modules, and it’s virtually impossible to debug it. Attempting to write data into a Float32Array and then deliver its .buffer as a Transferable over worklet’s port just returns an empty array.

Was wondering if there are any workaround/fixes or if it’s possible to remove global scope defined by Safari before SAC loads so that its compatibility mode works (which it does if you disable the experimental feature, which we can’t really tell our clients to do, especially on iOS)

TIA!

[chrisguttandin]

It’s possible to configure Babel to not transpile a certain feature. You don’t have to disable all es6 features. Any browser that is supported by standardized-audio-context also supports the module syntax. It’s also a requirement for the ScriptProcessor fallback for browsers without AudioWorklet support.

Maybe I’m missing something but why isn’t it ideal not to transpile something that the browser supports natively?

As mentioned in the README Safari has some limitations when it comes to the sampleRate of an OfflineAudioContext.

⚠️ Safari does not support creating an OfflineAudioContext with more than 10 channels or with a sampleRate below 44100 Hz.

But it looks like v14.5 supports anything until 3000 Hz.

[chrisguttandin]

Thanks for your nice words. I’m happy that it proves to be useful.