Closed
Bug 1023455
Opened 10 years ago
Closed 10 years ago
Documentation for Web Audio Editor
Categories
(Developer Documentation Graveyard :: Developer Tools, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jsantell, Assigned: jsantell)
Details
Web Audio Editor needs documentation, preferably by June 17th, to coincide with the release hacks post. https://developer.mozilla.org/en-US/docs/Tools
Assignee | ||
Updated•10 years ago
|
Assignee: wbamberg → jsantell
Comment 1•10 years ago
|
||
Jordan: https://developer.mozilla.org/en-US/docs/Tools/Web_Audio_Editor. Let me know if I'm missing anything important or have anything wrong. If you have a screencast I'd love to add it.
Updated•10 years ago
|
Flags: needinfo?(jsantell)
Assignee | ||
Comment 2•10 years ago
|
||
No screencast (yet), but these docs are looking great!
Flags: needinfo?(jsantell)
Assignee | ||
Comment 3•10 years ago
|
||
Added a note on the params that are displayed: "Each node has zero or more AudioParam properties that configure its operation. For example, the GainNode has a single gain property, while the OscillatorNode has frequency and detune properties. Some non-AudioParam properties are sometimes displayed, like an OscillatorNode's type property, and can be configured in the node inspector panel." Most properties that are displayed are AudioParam properties (which modifying, edits their `value` prop), but in some cases, non AudioParam's are displayed, like a BufferAudioSourceNode's `buffer` property or an OscillatorNode's `type` property, which are just primitives, not representations of an AudioParam. For better or worse, the editor normalizes these two different types of props.
Comment 4•10 years ago
|
||
Thanks for the clarification on that. I'm closing this bug, though I might update the page with anything from the blog post that looks tasty.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•