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 17695 - Marking channels/tracks as related
Summary: Marking channels/tracks as related
Status: CLOSED FIXED
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio Processing: Use Cases and Requirements (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: Olivier Thereaux
QA Contact: public-audio
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-05 14:18 UTC by Olivier Thereaux
Modified: 2012-09-10 10:14 UTC (History)
1 user (show)

See Also:


Attachments

Description Olivier Thereaux 2012-07-05 14:18:35 UTC
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.
Comment 1 Olivier Thereaux 2012-07-23 15:47:05 UTC
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.
Comment 2 Olivier Thereaux 2012-08-16 14:36:29 UTC
Done per http://dvcs.w3.org/hg/audio/rev/7f2980a82c34
Comment 3 Olivier Thereaux 2012-09-10 10:14:40 UTC
Seeing no objection to the proposed changeset, closing.