New issue
Advanced search Search tips

Issue 633795 link

Starred by 4 users
Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: 2019-09-06
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Number of outputs for an AudioDestinationNode is 1.

Project Member Reported by rtoy@chromium.org, Aug 3 2016 
WebAudio issue https://github.com/WebAudio/web-audio-api/issues/349 says the number of outputs for an AudioDestinationNode is 1 (instead of 0).

Update implementation to make it so.  

Not exactly sure how to test this, though.  Perhaps we can take the output of the destination node (from an offline context) and feed it to a delay node and then back to the destination node.  Maybe on a second channel.
Project Member

Comment 1 by sheriffbot@chromium.org, Aug 3 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by rtoy@chromium.org, Sep 5 2017

Status: Available (was: Untriaged)
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 6

Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by rtoy@chromium.org, Sep 6

NextAction: 2019-09-06
Status: Available (was: Untriaged)
This needs to be fixed to conform to the spec.  Priority is pretty low.

Comment 5 by hongchan@chromium.org, Sep 6

Status: Assigned (was: Available)

Comment 6 by hongchan@google.com, Dec 3

Status: Available (was: Assigned)
The comment #5 was a mistake. Making this issue to available.
►

Sign in to add a comment