Skip to main content

​
Troubleshooting

​
DAW settings

Large DAW buffers are fine. The plugin copies the stream into a buffer of its own, two seconds long, and a separate thread encodes and sends it at a steady pace, so a DAW buffer of 1024 or 2048 samples (or more) changes nothing for listeners. Any sample rate works. The stream is sent at 48 kHz; at another session rate the plugin resamples the streamed copy, and the header shows HOST, SENT AT 48 kHz. The DAW has to keep processing. The plugin streams what the DAW gives it. A DAW that stops processing plugins when its window is in the background, when the transport stops, or when a track is not armed or selected will stop the stream with it, and listeners see sender stopped or no audio for N s, which the page does not count as a dropout. Set the DAW to keep its audio engine running in the background, and keep the track the plugin sits on active. The computer should not sleep. A computer that sleeps or throttles the DAW ends the stream until it wakes. For a long session, set it to stay awake while the display is off.

​
Listeners hear interruptions

Hold the pointer over LISTENER DROPOUTS in the plugin to see each listener’s count and reason (see COST and SESSION).

​
The plugin’s status line

Each START makes a new link, and STOP ends it. A listener holding an old link sees This session has ended. or This link is not live; send them the current link from REMOTE LISTENER LINK. When the plugin loses its connection (a network drop, a DAW that pauses), it reconnects into the same session and the link keeps working. If the plugin stays away for 30 minutes (the DAW was closed without STOP, for example), the session ends, and the next START makes a new link.

​
Receiving

The messages a plugin in RECEIVE shows, and what they mean, are listed in Receive mode. A received track that keeps counting DROPOUTS while ARRIVAL GAP climbs is on an unsteady path from the sender; wired Ethernet at both ends helps, and the sender’s LOW BANDWIDTH lowers what has to arrive.

​
The listener hears stereo from a multichannel stream

  • The listener is on Safari or Firefox, which play through the system output. Chrome or Edge can choose the interface with device.
  • The system output is set to two channels. On a Mac, set the interface’s output format to its full channel count in Audio MIDI Setup; on Windows, set its speaker configuration in the Sound control panel.
  • The layout is fixed to 2.0. layout auto returns to choosing by device.
  • On a phone or tablet the page renders binaural by default.