micbuffa

This warning disappeared in my chrome. Or maybe I added the fix I suggested. I'll check and keep you informed...

Hi Jari Kleimola demoed this as a proof of concept at the WebAudio Conference 2018. Look at his paper(https://www.researchgate.net/profile/Jari_Kleimola/publication/331990070_Native_Web_Audio_API_Plugins/links/5c9a16d1a6fdccd4603b85a5/Native-Web-Audio-API-Plugins.pdf) + video presentation (https://www.youtube.com/watch?v=Kpv6_EU9YmE&list=PLQ9S5oqvpyWm2-HDGnQWWlX30pqYlb_Rz&index=22) The idea was to compile Chrome Embedded...

This is a bit old, but it presents this idea back in 2018. See the slides near the end... https://docs.google.com/presentation/d/1BCvYXa57Zcc9jtKfGmEwyd9-e8jvunvDcNrg8nWGQmY/edit?usp=sharing

Ah, Jari Kleimola has the source code, it's not publically available. I'll do a visio with him and ask. Can you tell us who you are / what are your...

When we designed the WAP standard, we had in mind the separation of dsp processing and GUI. HTML imports were the future in that time, that is the reason why...

For the SDK V2 we will rely on ES modules for sure. HTML imports are dead, I had to include a polyfill for html imports in all examples. I did...

No Jari, no news....

Thanks, go on... thanks for all your comments/suggestions, we will look after them next week. I'm in Morroco right now....

Indeed. For the V2 of the SDK this would be a good addition to be able to specify the name of the main js file in the main.json descriptor.

Can we discuss that. How to rely on this (indeed this would be cool) and make plugins having a URL and being dynamically loadable?