Closed
Bug 1007778
Opened 10 years ago
Closed 10 years ago
Add a devtools API for disabling effect processing AudioNodes
Categories
(Core :: Web Audio, defect)
Tracking
()
RESOLVED
FIXED
mozilla34
People
(Reporter: jsantell, Assigned: ehsan.akhgari)
References
Details
(Keywords: dev-doc-complete)
Attachments
(1 file, 2 obsolete files)
29.73 KB,
patch
|
roc
:
review+
smaug
:
review+
|
Details | Diff | Splinter Review |
AudioNode's should be able to be "circumvented" or disabled, as if all incoming connections routed directly to all of it's outgoing connections.
Reporter | ||
Comment 1•10 years ago
|
||
How possible would it be to have a chrome-only way of disabling an AudioNode, as in the audio stream flows through the node being unaltered?
Flags: needinfo?(paul)
Flags: needinfo?(ehsan)
Assignee | ||
Comment 2•10 years ago
|
||
Shouldn't be that hard. I'll try to write it up during the weekend.
Assignee: nobody → ehsan
Flags: needinfo?(ehsan)
Assignee | ||
Updated•10 years ago
|
Component: Developer Tools: Web Audio Editor → Web Audio
Product: Firefox → Core
Reporter | ||
Comment 3•10 years ago
|
||
Amazing :D
Assignee | ||
Comment 4•10 years ago
|
||
What semantics do you want for ChannelMergerNode and ChannelSplitterNode in this mode? Supporting the other node types should be very easy...
Reporter | ||
Comment 5•10 years ago
|
||
For utility nodes (merge/splitter/analyser/processor), probably nothing happens (processor's onaudioprocess event isn't fired). The main thing that'd be useful is for effect/transformation nodes to not alter the signal. For source nodes, I have another bug (bug 1007776) for "muting" source nodes, so if this is similar to that for source nodes, great! My ad hoc classification of nodes: http://jsantell.github.io/browser-dance-party-slides/#/14
Comment 6•10 years ago
|
||
Clearing NEEDINFO, let me know if you need anything from me.
Flags: needinfo?(paul)
Assignee | ||
Comment 7•10 years ago
|
||
(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #5) > For utility nodes (merge/splitter/analyser/processor), probably nothing > happens (processor's onaudioprocess event isn't fired). The main thing > that'd be useful is for effect/transformation nodes to not alter the signal. OK, firstly, "nothing" is not an option for the merger and splitter nodes. These nodes have more than one input and output ports respectively, and they need to output something sensible. I suggest that we keep them work the way they usually do, by merging or splitting the channels. I'll stop firing the events for the analyser and script processor nodes as well. > For source nodes, I have another bug (bug 1007776) for "muting" source > nodes, so if this is similar to that for source nodes, great! Source nodes probably need to be handled differently, so I'll leave them out of this patch.
Assignee | ||
Comment 8•10 years ago
|
||
Assignee | ||
Comment 9•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8474540 -
Attachment is obsolete: true
Assignee | ||
Comment 10•10 years ago
|
||
Comment on attachment 8474543 [details] [diff] [review] Add a devtools API to make some Web Audio nodes pass through their inputs Jordan, do you mind testing this patch please? It adds a boolean chromeonly passThrough attribute to some of the AudioNodes. Please see the *.webidl changes in the patch to see which ones. Let me know how well this works for you. I will need to write more tests before this is ready for review though.
Attachment #8474543 -
Flags: feedback?(jsantell)
Assignee | ||
Updated•10 years ago
|
Summary: Disabling AudioNode's in web audio editor → Add a devtools API for disabling effect processing AudioNodes
Reporter | ||
Comment 11•10 years ago
|
||
Testing this out now -- For channel splitters/mergers, sorry, I meant "do nothing" as in "no changes to how it normally works", so this sounds great :) Will report back!
Reporter | ||
Comment 12•10 years ago
|
||
Comment on attachment 8474543 [details] [diff] [review] Add a devtools API to make some Web Audio nodes pass through their inputs Review of attachment 8474543 [details] [diff] [review]: ----------------------------------------------------------------- A quick test case of the tools server-side interfacing with this worked great! Will add the DT bug as a dependent
Attachment #8474543 -
Flags: feedback?(jsantell) → feedback+
Assignee | ||
Updated•10 years ago
|
Attachment #8474543 -
Attachment is obsolete: true
Assignee | ||
Comment 13•10 years ago
|
||
Assignee | ||
Comment 14•10 years ago
|
||
Comment on attachment 8474773 [details] [diff] [review] Add a devtools API to make some Web Audio nodes pass through their inputs Requesting review from roc on the patch, and a rubber-stamp from Olli on the *.webidl changes. Note that this patch doesn't expose anything to the Web.
Attachment #8474773 -
Flags: review?(roc)
Attachment #8474773 -
Flags: review?(bugs)
Comment 15•10 years ago
|
||
Comment on attachment 8474773 [details] [diff] [review] Add a devtools API to make some Web Audio nodes pass through their inputs I would have added one [NoInterfaceObject] interface with [ChromeOnly] passThrough, and made the other stuff to implement that, if possible. Would be a bit simpler, less copy-pasting. If possible do that, otherwise the patch is fine too.
Attachment #8474773 -
Flags: review?(bugs) → review+
Attachment #8474773 -
Flags: review?(roc) → review+
Assignee | ||
Comment 16•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/2ad221f9aca9
Comment 17•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/2ad221f9aca9
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
Updated•10 years ago
|
QA Whiteboard: [qa-]
Updated•10 years ago
|
Keywords: dev-doc-needed
Comment 18•8 years ago
|
||
This feature is documented at https://developer.mozilla.org/en-US/docs/Tools/Web_Audio_Editor#Bypassing_nodes
Keywords: dev-doc-needed → dev-doc-complete
You need to log in
before you can comment on or make changes to this bug.
Description
•