Web Audio Editor
Note
Notice: This tool has been deprecated and will soon be removed from Firefox. For details, seeDeprecated tools.
With theWeb Audio API, developers create anaudio context Within that context they then construct a number ofaudio nodes, including:
nodes providing theaudio source, such as an oscillator or a data buffer source
nodes performingtransformations such as delay and gain
nodes representing thedestination of the audio stream, such as the speakers
Each node has zero or moreAudioParam properties that configure its operation. For example, theGainNode has a singlegain property, while theOscillatorNode hasfrequency anddetune properties.
The developer connects the nodes in a graph, and the complete graph defines the behavior of the audio stream.
The Web Audio Editor examines an audio context constructed in the page and provides a visualization of its graph. This gives you a high-level view of its operation, and enables you to ensure that all the nodes are connected in the way you expect. You can then examine and edit theAudioParam properties for each node in the graph. Some non-AudioParam properties, like anOscillatorNode’stype property, are displayed, and you can edit these as well.
This tool is still experimental. If you find bugs, we’d love it if youfiled them in Bugzilla. If you have feedback or suggestions for new features,dev-developer-tools orTwitter are great places to register them.
Opening the Web Audio Editor
The Web Audio Editor is not enabled by default in Firefox 32. To enable it, open theDeveloper Tool Settings and check “Web Audio”. Now there should be an extra tab in theToolbox toolbar labeled “Web Audio”. Click the tab and load a page that constructs an audio context. Two good demos are:
theVoice-change-O-Matic, which can apply various effects to the microphone input and also provides a visualisation of the result
theViolent Theremin, which changes the pitch and volume of a sine wave as you move the mouse pointer
Visualizing the graph
The Web Audio Editor will now display the graph for the loaded audio context. Here’s the graph for the Violent Theremin demo:
You can see that it uses three nodes: anOscillatorNode as the source, aGainNode to control the volume, and anGainNode as the destination.
Connections to AudioParams
Displaying connections to AudioParams is new in Firefox 34.
Connections between nodes are displayed as solid lines. If, instead, you’ve connected a node to an AudioParam in another node, then the connection is shown as a dashed line between the nodes, and is labeled with the name of theAudioParam:
Inspecting and modifying AudioNodes
If you click on a node, it’s highlighted and you get a node inspector on the right hand side. This list the values of that node’sAudioParam properties. For example, here’s what the OscillatorNode looks like:
With the Violent Theremin demo, the frequency parameter is modified as the user moves the mouse left and right, and you can see this reflected in the node inspector. However, the value isn’t updated in real time: you have to click the node again to see the updated value.
If you click on a value in the node inspector you can modify it: pressEnter orTab and the new value takes effect immediately.
Bypassing nodes
New in Firefox 38.
In the pane that shows you the node’s details, there’s an on/off button:
Click it, and the graph will be modified to bypass this node, so it will no longer have any effect. Nodes that are bypassed are shown with a hatched background:
