This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17372 - (HardwareScalability): Hardware Scalability section is vague and incomplete
Summary: (HardwareScalability): Hardware Scalability section is vague and incomplete
Status: CLOSED WONTFIX
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: This bug has no owner yet - up for the taking
QA Contact: This bug has no owner yet - up for the taking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-05 11:56 UTC by Philip Jägenstedt
Modified: 2014-10-28 17:17 UTC (History)
1 user (show)

See Also:


Attachments

Description Philip Jägenstedt 2012-06-05 11:56:34 UTC
Audio-ISSUE-87 (HardwareScalability): Hardware Scalability section is vague and incomplete [Web Audio API]

http://www.w3.org/2011/audio/track/issues/87

Raised by: Philip Jägenstedt
On product: Web Audio API

https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#hardware-scalability

This section contains normative (RFC2119) language but looks like it's design requirements that were input to creating the spec and or implementation. A number of different approaches are mentioned, but none are required. There are a few particularly strange statements:

"The system should gracefully degrade to allow audio processing under resource constrained conditions without dropping audio frames."

"First of all, it should be clear that regardless of the platform, the audio processing load should never be enough to completely lock up the machine."

"The system should be able to run on a range of hardware, from mobile phones and tablet devices to laptop and desktop computers."

What is the system? Are these really intended to be normative requirements?

"In order to avoid audio breakup, CPU usage must remain below 100%."

This certainly doesn't look like a normative requirement, it's just "must" used in a non-RFC2119 way.

These may-level requirements are worrying:

"It may also be exposed through a cpuUsage attribute of AudioNode for use by JavaScript."

"An AudioNode can have a priority attribute to help determine the relative importance of the voices."

Either AudioNode expose the attributes, or it does not.

There are more issues, but we recommend to drop the section entirely. If any of it should remain, we will have to go over it in more detail.
Comment 1 Olivier Thereaux 2014-10-28 17:14:28 UTC
Web Audio API issues have been migrated to Github. 
See https://github.com/WebAudio/web-audio-api/issues
Comment 2 Olivier Thereaux 2014-10-28 17:17:22 UTC
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.