Out of curiousity - why "best on latest Safari, but Chrome is OK too?" Web Audio is done by Chrome team.
cwilso opened this issue · comments
I know :) thanks for all the efforts. Try sample 5, the sound pops because of the convolution pedal. Turn it off and the pop goes away. Somehow Safari handles it cleanly, without a pop.
Hmm, interesting. I'm guessing that's just an artifact of the input being overdriven.
With a very far-fetched guess, I might say it causes a buffer overflow somewhere.
On testing again - are you hearing a DRASTIC pop, or just a boominess in the bass? I had it load once and be pretty messed up, and once it was fine except there was a hard boom in the bass that went away if I turned down the input (OD) volume.
Actually, I hear a DRASTIC stutter, it stops playing now and then, and yes, it's tied to the level of overdrive pedal, turn it down and it goes away.
Yeah, you're overdriving the output badly (since WA is floating point, it can be overdriven during processing without clipping - but the final outputs need to be held to a nominal -1.0 - +1.0 range. Not sure why this is behaving differently on Safari - I can't get any sound out at all on Safari 6.0 or a nightly. I'll ask Chris.