4 ms·
Strict timing is the #1 problem you need to solve if you want people to take your tool seriously. Check out ChucK and Impromptu if you haven't seen them. Both a
by bingaman 16y ago
Strict timing is the #1 problem you need to solve if you want people to take your tool seriously. Check out ChucK and Impromptu if you haven't seen them. Both are 'strongly-timed'.
- mambodog 16y agoThis problem is exactly why I feel that browsers need to implement some kind of 'Audio Canvas' API if there are going to be any serious audio apps developed in browser using JS. Currently only plugins like Flash offer the necessary timing control. Also, the current method for playing realtime-generated audio from JS involves packaging it up as a PCM Wave file and sending it to an <audio> tag. This is an ugly hack. An example of a strongly-timed audio app in Flash: http://www.audiotool.com/app http://www.audiotool.com/app
- sergimansilla 16y agoMozilla is working on an Audio Data API, and hopefully it will become the standard in the future. Take a look: https://wiki.mozilla.org/Audio_Data_API https://wiki.mozilla.org/Audio_Data_API