Looks cool, but I'd be a lot more willing to allow the Twitter integration if I could try the drums out beforehand and see if they're any fun.<p>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!
As someone who spends a lot of his time playing around with drum machines, I couldn't figure out how to use this. I was only able to make lines without laying down any individual notes. Not sure what I'm missing here?<p>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.
Yeeeeaaaah...<p>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.
Update my Twitter profile? Come on, for all the work that obviously went into create a cool product you could have taken an extra minute to properly set the oauth permissions.
I think this is a really neat idea and I really wanted to play with it but the interface isn't really intuitive and then I read that you have to use twitter to be able to use it. I think I'll pass. Neat idea though.
We replaced Twitter oAuth with a simple Tweet intent! <a href="https://github.com/MMODM/mmodm" rel="nofollow">https://github.com/MMODM/mmodm</a>
my firefox (latest beta) says :<p>"The buffer passed to decodeAudioData contains invalid content which cannot be decoded successfully"<p>and produces no sound on win 7 64 bit. chrome works flawlessly.
hope you guys enjoyed my drum solo at about 1:00 PM PST<p>I totally killed it....<p>because nobody else played anything for a while.<p>but seriously, what was used to build this? meteor.js?