Posting something to my Twitter is essentially a recommendation of it, which they're asking me to do without letting me try the thing I'm recommending. Too high of barrier to entry for me, sorry!
Also another thing to note, is that setting up the key triggers in alphabetical order like that is odd and really unintuitive. The standard for most digital audio workstations is to line up the top two rows of qwerty keys like they are piano keys (qwerty row = black piano keys, home row = white piano keys), and use 'z' and 'x' to change the octave.
Interesting idea though...
I agree with other people who complain about this. I shouldn't have to tweet something in order to see the results.
Why does your music toy need to be able "see who I follow and follow new people", "update my profile", or "post tweets for me"? That's just not happening. It's unnecessary.
I like to think I'm not the average clueless user, but this site really confuses me :) Looks like with a little polish and user testing, it could be fun, though!
I'll pass.
"The buffer passed to decodeAudioData contains invalid content which cannot be decoded successfully"
and produces no sound on win 7 64 bit. chrome works flawlessly.
I totally killed it....
because nobody else played anything for a while.
but seriously, what was used to build this? meteor.js?
We used Node.js, Express, socket.io, cluster, redis and MongoDB! Please fork us! https://github.com/MMODM/mmodm
You can checkout the code on Github here: https://github.com/mmodm/mmodm
We used a mixture of stuff, but mostly just node.js and jquery
