33 comments

[ 2.1 ms ] story [ 77.7 ms ] thread
"Can't find variable webkitAudioContext" error in chrome, ff, and safari for me.
I got the same thing, but enabling Web Audio in about:flags fixed it.
In Chrome, navigate to "about:flags" and enable Web Audio.

Restart browser and it should work!

Yeah doesn't work in Chrome 11
Yeah, I don't have a Web Audio flag in about:flags in Chrome 11 on Linux.
(comment deleted)
"Turn that off before I hit you," @jaylett
Try putting in 1 and just adding 0's :) Wonderful!
Sounds like birds chirping and a stream. Am I missing something?
change the hz value... the higher you go, the more dangerous it is.
This may seem like a silly question, but is it safe to try at home? [especially if you live alone]

IE, is there a potential that upon activating the demo to become instantly incapacitated and unable to stop it?

I ran it on JSFiddle (http://jsfiddle.net/BGW5u/) a few minutes ago, and everything went fine. Though, I now strangely have a craving of human brains for breakfast.

So, yeah, it's safe.

braaaaaaiiiinnsssss

Tried it in Chrome 13, the tab crashes immediately. Commented out the "new webkitAudioContext()" and the page loaded. :( I did enable the Web Audio in the flags.
(comment deleted)
Tested with Chrome 11.0.696 (couldn't find the Web Audio flag), Opera 11.10, Firefox 6.0a1 and even Internet Explorer 9. No sound at all.

Can someone give a description of what's supposed to happen?

Doesn't work in Firefox, Opera or IE9. It's written with the Web Audio API available in Chrome on OSX (about:flags to enable)

All it does is emits an adjustable frequency sine-tone.

People have said it many times before, but there's no such flag in this version of Chrome (11.0.696). Is it OSX specific?
It's not available in the stable release. You need to use developer channel Chrome, go to about:flags, enable Web Audio there. Then you can restart and begin abusing your eardrums. :)
Hey everyone! I wrote this little toy... I'm glad you're all enjoying it.

NOTE: OSX, Chrome dev channel (12.0.733.0 dev is the version I wrote this in) w/ Web Audio API enabled is the only way this is going to work for you. Everyone else will have to wait until the API is implemented in your OS of choice.

Lastly, there are very _real_ dangers of exposure to high frequencies such as: hearing loss, nausea, dizziness and vertigo (to name a few). Running this code is your choice, so handle with care!

Having done actual experimentation with weaponized acoustics in college I can assure you that no amount of noise generation on a web page is going to cause harm. Annoyance, yes, harm no.

Now if you're on your gaming rig and you have a 300 - 400 watt subwoofer hooked up, I've got a couple of sound files that can give you cramps :-)

You have the "brown note" on sound files? Nice!
works fine on winXP with Chrome 13 (Canary)