You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @Saintenr, I'm sorry but adding the ScriptProcessorNode is not really in line with the goals of this library. It's deprecated and has been replaced by the AudioWorklet. The goal of standardized-audio-context is to allow you to program against the most recent API.
If you use an AudioWorklet with standardized-audio-context it will automatically use a ScriptProcessorNode under the hood in case the browser doesn't yet support the AudioWorklet. Right now that is only necessary when using Safari.
Hey @Saintenr, just a heads up - if you are trying to get AudioWorklet working similarly to how ScriptPorcessorNode used to, it might be a bit tricky, and you'd have to utilize RingBuffer and memory sharing. Luckily there is an open-source art platform, which has a sound module that does exactly that: https://github.com/processing/p5.js-sound. A bit of digging, and you'll gain a better picture.
Hello Guys great work,
Im creating a project with cross device support and need the method createScriptProcessor().
Is it possible to implement this in a short term.
thanks for your feedback :)
The text was updated successfully, but these errors were encountered: