I'll have to use a slow ScriptProcessorNode.
Here's to hoping for Audio Worker Nodes aye :(
Out of curiosity how are the native nodes different from using the ScriptProcessorNode? For something simple like abs~ or wrap~ is performance *that *drastically worse?
On 26 August 2015 at 09:53, Julian Brooks jbeezez@gmail.com wrote:
Hi Seb,
Thanks for having a go. While absolutely agreeing with IOhannes, is it the same situation with [abs~] and [wrap~]?
Regards,
Julian]
On 26 August 2015 at 09:36, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2015-08-26 10:25, s p wrote:
Hmm ... actually I got carried away. I can't implement [cos~] or [env~] with native web audio API nodes. I'll have to use a slow ScriptProcessorNode. So if performance is not a concern for you I'll do it, but I won't integrate it to the core of
WebPd.
since it's really easy to build [cos~] with writing [cos] values to a table¹, wouldn't it make sense to add [cos] and [until] to the WebPd core?
fgmsdt IOhannes
¹ assuming that table lookups in WebPd are as blindingly fast as anyhwere else.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list