Bug 92768
| Summary: | JavascriptAudioNode with zero output channels should still process any inputs | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Raymond Toy <rtoy> |
| Component: | Web Audio | Assignee: | Raymond Toy <rtoy> |
| Status: | NEW | ||
| Severity: | Normal | CC: | crogers |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Raymond Toy
Currently, a JavaScriptAudioNode with no outputs will not do any processing and never call onaudioprocess().
There are two issues here. First, if the output of the node is connected to another node, no processing is done because the outputBuffer is 0 and the process() method exits early. This needs to updated to continue processing.
Second, if the JavaScriptAudioNode is not connected, processing still needs to be done. This probably needs to be done using the AutomaticPullNode class as used with the RealTimeAnalyzerNode.
See also http://code.google.com/p/chromium/issues/detail?id=137308 for a related issue and discussion.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Chris Rogers
The JavaScriptAudioNode *always* has one output, so the bug title and description should be changed.
What we're talking about is an output which has *zero* channels.