61–68 of 68 posts
It's nice you can do something in HTML5 that you could have done in Flash 10 years ago. (Of course, I know, this is all according to standards and all. But still.)
The sad part is you really still can't do this in HTML5, not if you want it to run on the most popular smartphone platform (Android).
Earlier quoted context omitted.
The old physical interfaces aren’t surpassed yet. Physical interfaces have the advantage of sending feedback through touch. Piano keys that push up harder when you press harder help you notice how hard you’re playing, and keys that depress discretely help you aim your fingers away from the lines between keys so you are less likely to miss. Of course, the ideal situation is a mix of electronic devices’ flexibility and…
The other idea is to put more sensors on the physical keys. Turns out, there is a kickstarter for that (just stumbled on it, don't know how legit it is): http://www.kickstarter.com/projects/instrumentslab/touchkeys...
Earlier quoted context omitted.
The sad part is you really still can't do this in HTML5, not if you want it to run on the most popular smartphone platform (Android).
Give it about a month and Chrome for Android will provide web audio API support. It's currently in chrome for android beta Our web app that plays audio in sync on multiple devices works in iOS, Chrome (non mobile) & Firefox Aurora. Were eagerly awaiting for the newest Chrome for Android to drop.
Earlier quoted context omitted.
The sad part is you really still can't do this in HTML5, not if you want it to run on the most popular smartphone platform (Android).
Give it about a month and Chrome for Android will provide web audio API support. It's currently in chrome for android beta Our web app that plays audio in sync on multiple devices works in iOS, Chrome (non mobile) & Firefox Aurora. Were eagerly awaiting for the newest Chrome for Android to drop.
Earlier quoted context omitted.
The sad part is you really still can't do this in HTML5, not if you want it to run on the most popular smartphone platform (Android).
Wouldn't it work on firefox for android?
I understand the sound data are generated by JavaScript. How many distinct sounds are generated? How much space is required to store this data? Are the notes of a chord combined by JavaScript or the browser?
Each note is generated as a separate sound file when the piano first loads. They're all short wave files. So when you hit a bunch of notes at once, it's just playing several sound files at once. If you click the square in the upper right, you'll get options to change the waveform and volume response. There are some other options too, like shifting by an octave or changing the color of the piano :) Better things could…