Lovers of experimental sound are finding a new canvas in the Web Browser, thanks to evolving work on standard audio tools. Cory O’Brien sends us his creation: “a real-time vector synth.” The result: crazy sounds. You’ll need Chrome, Chromium, or Safari 6 to try it out, but it’s quite a lot of fun. I especially like the percussive sounds I get just clicking spots. And it’s worth some different tries – and hitting the ‘R’ key to randomize – if at first you don’t like what you hear.

The deeper significance: you’re going to be seeing more things like this. Here’s Cory:

Just wanted to send you my new project TiberSynth, a real-time vector synth for the web browser. Built using the new Web Audio API, with Raphael.js for interface. The synth is a port of a Max/MSP patch I did a few years back, combined with an adapted controller mapping that’s based on work for an installation with Jeff Carey.

So far this is version 0.1, so I can promise nothing in the way of stability or features. And also the Web Audio API itself is barely documented (many project hours were spent extrapolating what features are available!). But so far this thing makes some pretty awesome and crazy digital noise music.

Check it out:


Here’s a question: anyone else think it’d be useful to have a tool that combines WebKit with some stuff useful for combining this with other audio apps, like JACK and JACK transport support? A sort of minimal browser for hosting audio? We may have to start hosting our own hackdays, huh?

  • Richard Eigner


  • Scotty McKinney

    are there any browsers out there that allow you to select your audio output? a browser that could integrate with soundflower could be a really useful production tool

  • AutoStatic

    With the ALSA JACK plug-in ( or the ALSA loopback device ( one can already connect the browser’s output to JACK. But those options are not so straightforward to set up and do not offer JACK transport. So yes, seems useful to me!

  • Greg Miernicki

    I actually filed a feature request with the Chromium team to see if they would implement a jack backend for Chrome instead of ALSA and they didn’t like the idea. The idea I had was to mix and match separate tabs (webapps) as parts of the studio. Who knows, maybe they plan to come up with something like this internally before they output via their backend…?

  • Greg Miernicki

    @c1c01f5abf3888050aa5b897339eff2a:disqus : you can allow Chrome to continue using PulseAudio and then use pulse-jack to route audio from that to other jack apps. This is what I currently do…