17695 2012-07-05 14:18:35 +0000 Marking channels/tracks as related 2012-09-10 10:14:40 +0000 1 1 1 Unclassified AudioWG Web Audio Processing: Use Cases and Requirements unspecified PC All CLOSED FIXED P2 normal TBD 1 olivier.thereaux olivier.thereaux cooper public-audio oldest_to_newest 69648 0 olivier.thereaux 2012-07-05 14:18:35 +0000 From the “Review of Web Audio Processing: Use Cases and Requirements” http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0852.html Suggest a requirement to allow audio channels to be designated as related to each other (e.g., a voice and instrumental overlay) so a volume change or pause of one of them affects all of the related ones, to allow them to stay in sync, yet allowing "unrelated" tracks (e.g., sound effects) to be treated independently. 71322 1 olivier.thereaux 2012-07-23 15:47:05 +0000 I think the underlying requirement is to be able to apply any kind of processing to several sources at the same time - designating sources or nodes or channels or tracks as related is really just one way to fullfil such a requirement. The Web Audio API - by virtue of being graph-based, does this naturally - you can mix several sources and apply any processing (including gain control) only to that group. Mentioning this requirement with accessibility in mind would very much fit our Use Case 4 - Radio Broadcast. A typical complaint about radio (or indeed TV) sound mixes is that one source of sound (say, background music and sound effects) is too loud and covers too much of another (say, dialogue). Giving people control over the mix (bombastic vs subdued music and effects) would be an interesting application of a web-based audio processing API. 72283 2 olivier.thereaux 2012-08-16 14:36:29 +0000 Done per http://dvcs.w3.org/hg/audio/rev/7f2980a82c34 73531 3 olivier.thereaux 2012-09-10 10:14:40 +0000 Seeing no objection to the proposed changeset, closing.