Docs Broadcasting

Managing receivers

Receivers on the network appear in the Studio's list. This page covers what can be done from that list.

The list#

Each receiver shows the following.

The latency column does not break sync, because the playback moment is written on the packet itself. That column shows the health of the network, not late sound.

If packet loss sits clearly above zero, look at that point's network link. A few tenths of a percent is normal at wireless points.

Discovery#

Receivers are found by themselves. The Studio sends announcement packets onto the network, running receivers hear them and drop into the list.

A receiver that shuts down leaves the list by itself. Nothing has to be deleted by hand.

Silencing one receiver#

There are two commands and they do different things.

Kick stops a receiver for sixty seconds. It returns to the broadcast by itself when the time is up. It is for a short intervention, for instance while work is being done at that point.

Ban parks a receiver outside the broadcast for fifteen minutes. If a banned receiver reappears within that window the Studio sends the ban to it again, so restarting does not get around it.

Unban lifts a ban before it expires.

Level#

Each receiver's level is set separately. That setting lives on the Studio, not on the receiver, so it survives the receiver being switched off and on.

If one point has a louder speaker, the answer is to lower that point's level, not the whole broadcast.

Headless receivers#

Receivers installed on small boards and machines without a screen run as a service. They start by themselves on boot and restart themselves on error.

On Linux, the log is read like this:

journalctl -u notfm-audio-receiver -f

A headless receiver also appears in the list and takes the same commands.