- From: David Singer <singer@apple.com>
- Date: Thu, 17 Jun 2010 17:19:15 +0300
- To: public-xg-audio@w3.org
My worry tis that audio processing could easily be defined in such a way that it is a synchronous task which has to 'keep up or fail spectacularly'. The trouble is that the CPU available both varies widely by device (as you list) and also, on many devices, varies widely over time (CPU competition). I believe that the tricky task is to design a system that degrades gracefully when not all the desired CPU is available. Events (e.g. mouseMoved) do that by dropping the event frequency. Animations/transitions do that by dropping the frame rate. How will sound processing do that?
Received on Thursday, 17 June 2010 14:19:49 UTC