audiolib.js

If implementing every effect out there by yourself becomes tedious, you might wanna give audiolib.js a shot: https://github.com/jussi-kalliokoski/audiolib.js , it's an audio effects library I've been building for 2 years now. :)

> There is, as far as I can tell, no way which you can cause a sound to play (programmatically) I suggest you give my audiolib.js ( https://github.com/jussi-kalliokoski/audiolib.js ) and sink.js ( https://github.com/jussi-kalliokoski/sink.js ) a shot, they're designed to abstract away the differences between the "competing" Audio APIs, allowing you programmatic access to as deep as the sample level and providing abstractions such as filters, reverbs, delays, etc. For browsers with no Advanced Audio API, there's an inferior fallback using the <audio> elements. > On the other hand, there are platforms like Java or Flash (or Unity, so I've heard), where you can write once and expect it to work identically everywhere (even on out of date browsers). That must be nice. I've heard good things about Unity, and it seems to be a great toolkit for g

We wrote a little game that should help with pitch recognition. Uses Couch for storing high scores, Redis for cache and Tornado for the server. Makes use of Audiolib.js (https://github.com/jussi-kalliokoski/audiolib.js/) for audio that works in FF/Chrome. Bit weird in FF though, but at least it plays. I did most of the JS and my friend did most of the backend. We were sorta on deadline, so the design isn't quite what I would call perfect (ha) and my JS is super-messy in places. Also, there are bits where I inexplicably use jQuery for stuff I had been doing without a framework and other weird inconsistencies like that, but hey, it works. Anyway, let me know what you think! Thanks.