> Le 17 mars 2017 à 14:36, Victor Lazzarini a écrit :
>
> yep, a three-year wait.
Yep )-;
>
> It would have been good if NaCl's Pepper
> API had been made available through
> wasm and we could just ignore web audio.
I don’t think this is the role of wasm which is just a better designed asm.j
yep, a three-year wait.
It would have been good if NaCl's Pepper
API had been made available through
wasm and we could just ignore web audio.
Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland
> On 17 Mar 2017, at 13:06, Stéphane Letz wrote:
>
> Yes : t
Yes : the generated wasm module is wrapped with basically the same code we
used in asm.js case, to become a WebAudio/ScriptProcessor node.
We are sill waiting for the AudioWorklet proposal to become official (see
https://github.com/WebAudio/web-audio-api/wiki/AudioWorklet-IDL-Proposal)
Stéphan
Interesting. Does the wasm code still depend on the webaudio for IO and the
scriptprocessor node?
Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland
> On 17 Mar 2017, at 12:30, Stéphane Letz wrote:
>
> Hi All,
>
> WebAssembly (http://webassembly.org) is
Hi All,
WebAssembly (http://webassembly.org) is now officially activated in Chrome and
Firefox
(https://lists.w3.org/Archives/Public/public-webassembly/2017Feb/0002.html).
The Faust WebAssembly backend emitted binary format has been raised to match
the official 0x01 number.
Statically genera
