Thanks, Steven!

I did some testing and remote debugging from Google Chrome on my android to see the javascript console output and as you suggested, the quality depends wheter AudioWorklet or   ScriptProcessorNode is used.

The results are somewhat strange:

When I load
https://instruments.kunstmusik.com/vt/index.html
or
https://vlazzarini.github.io/paw/examples/canvas.html
either on desktop  or Android, the AudioWorklet is found and used:
CsoundObj.js:49 Using WASM + AudioWorklet Csound implementation

If I load the same (or probably the same) canvas.html that I had downloaded from Csound webpage (csound-web-6.12.0) on local server then
- on Chrome desktop AudioWorklet is used
- on Chorme/Android ScriptProcessor:
js/CsoundObj.js:53 Using WASM + ScriptProcessorNode Csound implementation

May this have something to do with the actual Csound-web version? The same with Csound-web-6.13.0 -  loading canvas.html to Android/Chrome uses ScriptProcessorNode.
Can you guess what is different on kunstmusik.com or vlazzarini.github.io  ? Earlier Csound version? https?

greetings,
tarmo



On Sep 11 2019, at 5:58 pm, Steven Yi <stevenyi@gmail.com> wrote:
I tried and also got crackles on the flute page. Sliders worked
alright here, canvas did not make sound. This is with Android Chrome
on Pixel 3.

Running https://instruments.kunstmusik.com/ (these were made a couple
of years ago, code at https://github.com/kunstmusik/instruments) on my
browser was very smooth with little latency.

I have not tested on iOS in a while, but last I checked Safari had a
not very good WebAudio experience. I think it does not support
AudioWorklets and shares issues that happen with ScriptProcessorNode
running on the main thread. On desktop and mobile though, I've found
Firefox's SPN implementation to be quite good compared to Chrome-based
browsers. The instruments site ran here on Android and did not hiccup
even when using multitouch input.

I checked and the instruments site is using Csound 6.11. I don't know
if that is a factor, or if Victor's csound.js wrapper is a factor, or
canvas, or what. I suppose it might be good to check the instruments
site on your devices to see how that responds and maybe we can figure
out more information from there.

On Wed, Sep 11, 2019 at 10:01 AM Tarmo Johannes <trmjhnns@gmail.com> wrote:

Hi,

I tried out a web application with WebAudio Csound:
http://tarmo.uuu.ee/wasm/flute/flute.html

On desktop it works fine but my experience with handheld devices is:

on Android/Chrome there is huge latency (but this might be something to do with the KineticJS used for canvas)
on Android/Samsung internet browser and iOs/Safari the audio is crackling (I think they both are based on Webkit?). Also
https://vlazzarini.github.io/paw/examples/sliders.html
https://vlazzarini.github.io/paw/examples/canvas.html
crackle with these browsers.

What is your experience? Can someone comment?

Thanks!
tarmo


Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here