Skip to main content

​
Receive mode

In RECEIVE, the plugin plays another NOMN REMOTE session out of the track it sits on. You paste the session’s listener link, press RECEIVE, and the sender’s audio replaces whatever the track was carrying. The plugin joins the session as a listener, exactly as a browser does, so the sender needs to do nothing different.

​
Receive a session

  1. Insert NOMN REMOTE on the track that should play the session, with the track in the layout you want to hear (stereo, 5.1, 7.1.4 and so on).
  2. Click RECEIVE in the switch at the right of the header. SEND is the default.
  3. Paste the listener link into SESSION TO RECEIVE, or press PASTE to take it from the clipboard.
  4. Press RECEIVE. The button becomes STOP, and the status line under it reads, for example, RECEIVING · RELAY · FROM 7.1.4, RENDERED 7.1.4.
The switch and the link are saved with your DAW session. Neither can change while a stream or a receive is running, so press STOP first. In RECEIVE the controls that belong to a sender leave the window (ENCODE AS, LOW BANDWIDTH, RELAY, STREAM GAIN and COST), since the sender has already chosen them. The header shows the incoming layout and codec once the stream arrives, OUTPUT names the track’s own bus, and the RECEIVED meters read that bus. Receiving needs a licence or a trial, as START does. Without one the status line reads RECEIVE REFUSED · A LICENCE OR TRIAL IS NEEDED TO RECEIVE.

​
What reaches the track

The plugin renders the stream to the track’s layout: An ambisonic track cannot receive: give the plugin a speaker layout or stereo, and the listener’s ambisonic stream is decoded to it. The status line names the problem as THE OUTPUT BUS (…) HAS NO IAMF RENDER. Any session sample rate works. Streams are sent at 48 kHz, and the plugin converts them to your session’s rate.

​
Delay and drift

The plugin holds about 300 ms of audio before it plays, which rides out the unevenness of the network, and after each dropout it holds 100 ms more, up to 600 ms. The delay you hear is that buffer plus the network path from the sender. The plugin reports no latency to the DAW, because plugin delay compensation cannot account for a network, and the RECEIVE card says so. To line a received track up with material in your session, offset the track in the DAW. The sender’s audio clock and yours never run at quite the same speed. The plugin follows the sender by resampling the stream by a few parts per million, shown as DRIFT, so the buffer stays level without skipping or repeating audio.

​
The RECEIVE card

A climbing ARRIVAL GAP with DROPOUTS points at the network between the sender and you; see Network.

​
Relay and Direct

A receiving plugin follows the sender’s RELAY setting. On a relayed session it is one of the link’s listeners and counts toward its limit (50, or 4 when the sender is on a trial). On a Direct session it takes the one direct connection, and when no direct path forms within 8 seconds it moves to the relay, as the listener page does.

​
Cost

A receiving plugin is billed as a listener: on a relayed session its channels and time are metered to the sender’s account, as a browser listener’s would be, and Direct is free. Receiving adds nothing to your own bill. See Pricing.

​
Messages