We even managed to get low latencies on windows with both chrome and FF on
windows 10, but it's a bit of a nightmare... not all sound cards are
compatible with the IAudio3 high definition drivers, windows sometimes
installs by itself the wrong generic driver, low latency worked only at
16bits/44.1K
Just in case you'd be interested, we measured the end to end latency using
Chrome and FF on Mac OSX, with something like 15 different sound cards from
12 euros to 160 euros. Latency from a guitar to speakers is from 14Ms (FF
nightly) to 19ms (Chrome), and the cheapest sound cards are not the ones
w
I just want to add that I measured the latency from button-press to
sound in the Chrome browser (default settings) on my humble old
MacBook, and saw about 10 ms! I was amazed - better than iOS apps!
On Wed, Feb 26, 2020 at 12:37 AM michel buffa wrote:
>
> Hi all, you also use the Faust IDE and g
Hi all, you also use the Faust IDE and generate dirrectly easy to reuse
WebAudio plugins. This is the easiest way to add some AudioWorklet nodes to
a WebAudio graph. You can even design the GUI directly in the IDE (using an
experimental version of the IDE). See my presentation at the PAW 2020 and
Hi Laurent and Casey,
Thanks Casey for the extensive summary.
Laurent, as explained in the
https://github.com/grame-cncm/faust/tree/master-dev/architecture/webaudio page,
you can basically either 1) compile Faust DSP to wasm + WebAaudio in advance
then customise and deploy the result or 2) emb