Wow! This is very weird. I'm wondering if it's something that chrome changed recently (and released yesterday)? I remember that FF sounded exactly like this before. So maybe chrome had the incorrect API implementation and now it's "fixed"?

Thanks for pointing it out!

What's even stranger is that I can't find any evidence that Chrome has been updated within the past 6 days - I'm currently on 36.0.1985.125 m, which was released on July 16. It's very odd indeed.

Not sure if this will help, but maybe adding a high-pass filter (or removing any low-pass filters) will do it: http://chimera.labs.oreilly.com/books/1234000001552/ch06.html

Thanks for the report :). Turns out you have to use the string names of oscillators now in Chrome. Probably something I should have done from the very beginning. Oh the fun of working with an ever-changing API :). The cool part is now this works in Firefox!! :)

For reference: http://webaudio.github.io/web-audio-api/#idl-def-OscillatorType

Very nice! Good job fixing it so quickly!