> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nomn.jp/llms.txt
> Use this file to discover all available pages before exploring further.

# What is NOMN REMOTE?

> Stereo and multichannel audio from a DAW session to a browser tab somewhere else

# NOMN REMOTE

NOMN REMOTE puts the output of a computer-based audio session into a browser tab somewhere else. We built it for people who occasionally need to collaborate remotely, perform remotely, run a sound installation from their own machine for a gallery far away, or otherwise send high-quality audio to another place, and for studios that need many simultaneous listeners and would prefer to pay for what they use.

You insert the plugin on a track or a bus in your DAW, press **START**, and send the link. The person on the other end opens it in a browser and hears the session as you play it, at the channel count you are working in. They install nothing and need no account, and their output device decides the render: 7.1.4 to a twelve-speaker room, stereo to headphones, 9.1.6 to an interface with sixteen or more outputs.[^1]

The stream is IAMF (Immersive Audio Model and Formats, the open, royalty-free format behind Eclipsa Audio). By default it carries lossless 24-bit FLAC; the **LOW BANDWIDTH** switch sends Opus at 64 kbit/s a channel for listeners on slower connections. The listener's browser decodes the stream and renders it to whatever layout their device has.

The plugin passes your track's audio through untouched, and streaming adds no latency to your session. Each session is hosted on the NOMN REMOTE server nearest to you, chosen when you press START, and listeners anywhere join it there.

## Two ways to reach a listener

**Direct** connects the plugin to one listener's browser, peer to peer. It has the lowest latency and is free, since its audio never passes through our server.

**Relay** sends the stream once to our server, which passes a copy to every listener on the link, up to 50 listeners (4 during the free trial). Relay is metered by channels, listeners and time. See [Direct and Relay](/remote/streaming/direct-and-relay) and [Pricing](/remote/reference/pricing).

## Receiving and mixing

The plugin can also play a session. Switched to **RECEIVE**, it takes a listener link and plays that session out of the track it sits on. Several receive tracks in one DAW mix like any other tracks, and a NOMN REMOTE send on the master streams the mix as a new session. The mixing page does the same in a browser. See [Receive mode](/remote/receiving/receive), [Mixing in the DAW](/remote/receiving/mixing-in-the-daw) and [The mixing page](/remote/receiving/mixing-page).

## Key capabilities

* **Layouts** from mono to 9.1.6, first to third order ambisonics (ACN, SN3D), and numbered buses of up to 16 channels, streamed as IAMF
* **ENCODE AS** sends one of IAMF's own downmixes of the bus (7.1.4 to 5.1 or stereo, for example)
* **Lossless FLAC** at 24 bit, or **LOW BANDWIDTH** Opus
* **Direct** to one listener at no cost, or **Relay** to up to 50
* **One link per START**, ended by STOP
* **RECEIVE** plays another session out of a DAW track
* **The mixing page** mixes up to 50 sessions in a browser and streams the mix
* **COST** card with the live rate, the session's cost and the month's included time
* **SESSION** card with listeners, throughput, dropped packets and the dropouts your listeners report
* **Listener page** with layout choice, a routing matrix, output selection and a speaker test
* **VST3, Audio Unit and Standalone** on macOS; **VST3 and Standalone** on Windows

[^1]: Choosing a multichannel interface on the listener page needs Chrome or Edge. Safari and Firefox play through the system output however it is configured.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.