- From: <bugzilla@jessica.w3.org>
- Date: Sat, 16 Mar 2013 17:58:03 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21311
Bug ID: 21311
Summary: OfflineAudioContext needs a way to handle audio of
arbitrary duration
Classification: Unclassified
Product: AudioWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Web Audio API
Assignee: crogers@google.com
Reporter: joe@noteflight.com
QA Contact: public-audio@w3.org
Reference from mailing list:
post: http://lists.w3.org/Archives/Public/public-audio/2013JanMar/0395.html
author: Russell McClellan <russell@motu.com>
"[OfflineAudioContext] really should provide some way to receive data
block-by-block rather than in a single "oncomplete" callback. Otherwise, the
memory footprint grows quite quickly with the rendering time. I don't think
this would a major burden to implementors, and it would make the API
tremendously more useful. Currently it's just not feasible to mix down even a
minute or so. If this is ever going to be used for musical applications, this
has to change."
Chris Rogers stated in teleconference 14 Mar 2013 that it is in fact feasible
to mix down typical track lengths of several minutes with the single oncomplete
call. A discussion of block size suggested that any breaking of audio rendering
into chunks should be fairly large to avoid overhead of switching threads and
passing data.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 16 March 2013 17:58:04 UTC