Both Mozilla and Webkit implemented different audio (Audio Data/Web Audio) APIs -- wonder what BlackBerry Dev Alpha uses if any.. needs a better 'not supported' message

I'm not really up to speed on the differences between browsers, but the Dev Alpha does use Webkit. Unsure what build we have, and what audio APIs are actually supported. The fact that I hear the music and see the particles moving is a start at least.

I'll look into more webkit browsers -- I know on my Nexus S webkit browser, it has awful performance, but the audio plays. If the webkitAudioContext/AudioContext isn't found, it falls back to the Mozilla implementation, which is an extension of the non-fancy HTML5 audio, which means it will play audio, just be unable to read the frequency data from it -- and while the glowy balls move around independent of that data, there'll just be no boom and shaking due to absence of the frequency data :)

Now to build Chromium and try on vanilla Webkit..

That's exactly what I observe, so it likely is kicking back to the Mozilla implementation.

If you need me to test/debug, give me a shout. I'd be happy to help.

Great, will let you know :) although I need to do research on when/if/how the Web Audio API is hitting mobile Webkit browsers..

It takes a few seconds to start. The particles should pulse on each kick. You may not be able to hear it very well, its very bass-heavy.

Ok, I just tried it on my desktop, and it works perfectly in Chrome. On the Dev Alpha, like I said, I see rotating fuzzy balls, but not the beat synch'd animation like I see on Chrome.

At the top, I see the spectrum scrolling by, with it averaging about 20 FPS. I cannot click on toggle FFT spectrum, it doesn't recognize my tap. Like a limitation with the WebGL implementation.