http://labs.official.fm/media/vibe@44100.flac, but it shouldn't sound 'choppy'.

We have had some problems on Linux where Chrome(ium) for some reason reports the wrong sample-rate, but that usually just changes the playback speed.

Does it use high amounts of CPU too?

Yep, that sounds normal. It uses about 12% CPU for Pulse and 12% for Chrome (this is a Core 2 Quad).

Could you please add an issue with some more precise information about your browser(s)/sound server at https://github.com/ofmlabs/aurora.js/issues ?

Chrome and Ubuntu have been having both HTML5/Flash audio since early this year unfortunately. It's rare that I have any audio played correctly via Chrome regardless of the source, it sounds corrupt and plays at the wrong speed most of the time. Suspicions are PulseAudio. You can try killing it and reloading the page and trying again (you may also need to restart Chrome).

try adding tsched=0 to one of the lines in /etc/pulse/default.pa so it becomes

load-module module-udev-detect tsched=0

this fixed my chrome ubuntu audio problems. (source: links at bottom of http://code.google.com/p/chromium/issues/detail?id=110375 )