search

sebpiq / WebPd

Run your Pure Data patches on the web.
GNU Lesser General Public License v3.0
932 stars 89 forks source link

WebPd broken in chrome 53 to 57 #109

Closed kristoferhagbard closed 6 years ago

kristoferhagbard commented 7 years ago

I have found that lop~ in some situations creates a very loud noise in chrome Version 56.0.2924.87 (64-bit) on OSX

Here is an example patch: (don't test with headphones!! :-) )

Archive.zip

sebpiq commented 7 years ago

Yes ... basically WebPd is completely broken with chrome between versions 53 and 57. This is because of this chrome bug which they took ages to fix : https://bugs.chromium.org/p/chromium/issues/detail?id=647974

But I am preparing a completely new version on WebPd getting rid completely of Web Audio :)

sergiogranadamoreno commented 7 years ago

@sebpiq :O

Can't wait for you to do that!

sebpiq commented 7 years ago

@sergiogranadamoreno it's well on its way already ;) https://github.com/sebpiq/WebPd/tree/refactor-js

kristoferhagbard commented 7 years ago

Looking forward to testing it! keep up the awsome work! (For now I got it working with the Heavy compiler from Enzien)

mattdiamond commented 7 years ago

But I am preparing a completely new version on WebPd getting rid completely of Web Audio

Did you mean getting rid of it just for DSP stuff? I'm checking out that branch and it seems like you're still using a ScriptProcessorNode to handle audio output (which makes sense). That part of the Web Audio API is staying in, right?

sebpiq commented 7 years ago

@mattdiamond of course I can't get completely rid of Web Audio :) for now the ScriptProcessorNode will have to stay, and in the future, AudioWorklet. For now, WebPd is working again with master branch in Chrome, as now most devices have version 57 or more.