Originally from etherpad
The Web Audio Editor in Firefox Developer Tools is still a work in progress. A lot of love is needed in its current state, and once the basic features are working, here are some dream features, and future planning.
- Fx31 - Prototype, img
- Fx32 - Release
- Fx33 - Refined Release
- Fx34 - Designer Tools
- Context View (displays meta information about the AudioContext itself) bug 1007321
- Display automation over time (toggle between GRAPH view and AUTOMATION view?) bug 1007876
- Display input/output nodes in a connections panel bug 1007875
- Display feedback when an AudioSourceNode is playing.bug 1006626
- Display time/frequency domain visualization, VU, for overall sound output bug 1019100
- Display AudioNode connected to an AudioParam. bug 986705
- Create AudioNodes bug 1023474
- Connect AudioNodes bug 1023475
- Load an AudioBuffer into an AudioBufferSourceNode via GUI bug 1022250
- Start/stop AudioSourceNodes bug 1006624
- "Tap into" nodes, listen along the way bug 1007887
- Play AudioBufferSourceNode's buffers (use a new AudioContext/audio element) bug 1007889
- "Disable/bypass" AudioNodes in a chain bug 1007778
- Hide unconnected nodes from view bug 1007255
- Hide GC'd nodes from view bug 1023462
- Some way to debug
onaudioprocess
bug 1008741 - Break on action (connect/disconnect/play, etc.) bug 1007901
- Profiling glitches/"audio jank" bug 1008743
- Debugger break on AudioNode connect (or other events) bug 1007901
- Support multiple AudioContext's on a page (low priority IMO) bug 1006624
- Render/save out audio output from an AudioContext bug 1008742
GC-event when node is GC'd (so we can clear up dead-nodes in the graph view) bug 1008497- Bypass/skip node in an audio chain (possible to implement on actor, but may be better to be native) -- for bug 1007778, may be necessary
- Buffer with loop
- Who is going to use this tool? Game developers? Audio hackers?
- Twitter: @jsantell, @firefoxdevtools
- IRC: irc.mozilla.org #devtools
I had another idream! What about being able to analyse the output of the currently selected node? So for example suppose I highlight the context destination-I would get a little panel in the inspector with the FFT + wave display + a saturation level indicator. This kind of visual cues are super useful when I'm doing stuff and you're sort of tired and unsure whether your ears are tricking you!
Then you could select another node and see what was it doing-is it the one which is introducing that annoying high frequency? Etc...