Target platforms?

Does this group have any kind of characterization of what the intended target platforms are?  If not, do we have a process for determining that?  

I ask because realtime client-side audio synthesis and processing is notoriously sensitive to the available compute resources in the client device.  As a result, web pages/content with more elaborate audio features would seem to be at risk of producing bad user experience when accessed from less powerful client devices.  If JavaScript/ ECMAscript audio DSP code is truly expected, then this factor would seem to be significantly exacerbated.

Not that I endorse the idea, but for information: many previous standards efforts have been forced to resort to complicated and unpleasant mechanisms like profiles, or using an estimation of available compute power to reduce polyphony, to manage such problems.

	-- Chris G.

Received on Tuesday, 15 June 2010 02:29:37 UTC