Chris Kiefer

that sounds good. @frantic0 can you add this to the debug window?

this should be accessible through the new DOM command system

possible clue: it's used internally for chorus and flange and these are working fine.

looks like this is a cheerp issue (see #181)

maybe this helps https://developer.chrome.com/apps/offline_storage#asking_more

:l3:{{:m2:}imp,{{0.01}pha,0.1,0.4}ulin}|fbcell; :l4:{{:m3:}imp,{{0.01}pha,0.3,0.9}ulin}|fbcell; :l5:{{:m6:}imp,{{0.01}pha,0.0,0.9}ulin}|pg2; :l6:{{:m5:}imp,{{0.1}pha,0.1,0.8}ulin}|pg1; :l7:{{:m6:}imp,{{0.01}pha,0.1,0.8}ulin}|fence; :l8:{{:m7:}imp,{{0.01}pha,0.1,0.8}ulin}|fence;

the audio actually carries on playing, but you can't evaluate new code

further note: looking at the code, this is complex stuff crossing the js/emscripten boundary. why not export maxiSample using CHEERP instead? Then memory stays within JS scope, no need to...

this is part of the block tracking in the codemirror component

I am getting this bug on Chrome 81 in Ubuntu, using the latest library from github, with the command let svdR = svd(R, "thinU"); I've attached an example of data...