I'd recommend using Timbre.js
<a href="http://mohayonao.github.com/timbre.js/" rel="nofollow">http://mohayonao.github.com/timbre.js/</a>
As much as I love audiolet, Timbre.js knocks the socks off of it. It's very much based off of supercollider, which is really THE language to live-code in.<p>Also, it's way more fully developed than audiolet, and seems to work way faster.
Great stuff!<p>See also "livecodelab" and "gibber":
<a href="http://www.sketchpatch.net/livecodelab/index.html" rel="nofollow">http://www.sketchpatch.net/livecodelab/index.html</a>
<a href="http://www.charlie-roberts.com/gibber/" rel="nofollow">http://www.charlie-roberts.com/gibber/</a><p>Gibber is multi-user live coding in the browser.<p>There are many more live coding systems here:
<a href="http://toplap.org/" rel="nofollow">http://toplap.org/</a>
I don't mean to criticize, I'd simply like to clarify something.<p>What exactly makes this "live" coding? As far as I can see, you have to press Esc to run the code. If this is considered live, what would be a non-live equivalent?<p>My understanding of live was that you see/hear changes as soon as you change the code, but I didn't find that to be the case here.
This is pretty awesome. I went to a workshop by ixi lang creator thor magnusson. It is pretty amazing the level of abstraction you get with ixi lang but supercollider has a steep learning curve.<p>I love that live coding music is making its way to javascript / coffeescript. I can't wait to see what people create with it.
This is a great idea – a convenient environment for writing music-generating code. It needs far more helper functions and documentation before it’s generally usable, though.<p>I’ve written some GitHub Issues: <a href="https://github.com/bengl/beatsio/issues" rel="nofollow">https://github.com/bengl/beatsio/issues</a>
Cool! I threw together something similar a few weekends ago:<p><a href="http://roadtolarissa.com/synth-scales/" rel="nofollow">http://roadtolarissa.com/synth-scales/</a>