/ Topics / Audio IO

Hz In Your Browser
Hz System Overview, The Sandbox
Asset-based, Nonlinear Workflow
Authoring Musical Notes . Soundscaping
Audio IO . MIDI IO
Debugging Your Scripts
Comparing Programmable Audio Systems

---

home . Topics . Interface . Reference . Examples

right-click to navigate to page sections

---

info   Most computers have Audio IO devices built in. When recording or producing sound with Hz you must choose which devices to associate with the abstract ADC (Analog to Digital, recording) and DAC (Digital to Analog, playback) nodes in your sound designs.

Since HzWeb runs in your browser, the current audio input and output devices are defined via your computer's system settings.

Audio Output

The Hz.DAC anode is automatically created when you create an audio scene and it is bound to the webaudio destination.

The browser binds AudioContext.destination to what it considers the default audio output device. Typically this means:

• MacOS: the system's current default output device (System Settings → Sound)
• Windows: the default playback device (or the default communications device, depending on browser and context).
• Linux: whatever PulseAudio/PipeWire/ALSA presents as the default output

Audio Input

An Hz.AudioIn anode is only created when your scripts request it. If your system has multiple inputs available, it's possible to create multiple anodes and stream output from different channels.

Currently Hz.AudioIn binds to the default input device presented to the browser. Again, this can be controlled by your computer's system settings. If you've imported our examples, you can find examples of Audio Input here: .../hzplugins/audioIn.js, tuner.js.