3 ms·

This is so weird, it's running well for me but obviously buggy for many. Do you mind telling me which parameters caused issues? and what machine are you runnin

• bchjam 11y ago
  fwiw I got reports of inconsistent/unreproducible performance issues when I was working on a webaudio synth project last year. Never figured if it was down to audio hardware or what but I have seen a couple upgrades of Chrome that performed weird, tho webMIDI API was still shifting a bit
  • ogig 11y ago
    I confirm this. My webaudio project was halted because I couldn't figure out why the cpu usage kept going up. After some chromium lists reading I decided to give them some time to polish the api. Some months later the same project was working as expected.
• ogig 11y ago
  I tested again and seems to be on every knob. It goes like this; i change a parameter, the "led ui" on the synth shows the param name and a value and it freezes for some 40-50secs. During that time ui is totally unresponsive. After the freeze time the ui might come back, maybe burst a note or two, or might hang like that forever. My computer is an old core 2 quad, but i'm working on a webaudio project myself and by my estimation it should be able to handle your synth easy. Also, in case it helps. I've found some hard to debug webaudio issues, like osc hanging in forever and 'cpu leaks', but your issues seems more related to how the ui is updating the audio graph.