17694 2012-07-05 14:17:06 +0000 Per-track and global control 2012-09-20 06:59:06 +0000 1 1 1 Unclassified AudioWG Web Audio Processing: Use Cases and Requirements unspecified PC All CLOSED NEEDSINFO P2 normal TBD 1 olivier.thereaux olivier.thereaux cooper philipj public-audio oldest_to_newest 69647 0 olivier.thereaux 2012-07-05 14:17:06 +0000 From the “Review of Web Audio Processing: Use Cases and Requirements” http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0852.html Need a requirement to allow both per-track and global (with the Web application) control of each audio channel / track / whatever for volume, mute, pause / restart, and autoplay. I think this is implied by the use cases but not spelled out in the requirements. 71368 1 philipj 2012-07-24 10:01:12 +0000 The way the problem is stated, it sounds like it's talking about HTMLMediaElement, which has volume, mute, play/pause and autoplay, whereas the Web Audio API does not. INVALID? 71519 2 olivier.thereaux 2012-07-26 16:17:54 +0000 (In reply to comment #1) > The way the problem is stated, it sounds like it's talking about > HTMLMediaElement, which has volume, mute, play/pause and autoplay, whereas the > Web Audio API does not. INVALID? I agree that the requirement for play/pause is irrelevant in the context of web audio processing. Trying to think about anything else to extract, or maybe the rest is well covered by Bug #17695? 71597 3 philipj 2012-07-27 08:50:34 +0000 Maybe, I'd resolve this as NEEDSINFO if the PFWG want to clarify. 72282 4 olivier.thereaux 2012-08-16 14:22:01 +0000 (In reply to comment #3) > Maybe, I'd resolve this as NEEDSINFO if the PFWG want to clarify. Sounds reasonable. 74115 5 olivier.thereaux 2012-09-20 06:59:06 +0000 Hearing no objection after a few weeks, closing.