NMOS discovery and adoption can help you bring senders and receivers into Buttons and start routing them within seconds. Select the nodes you want to control, adopt them as connections, and their routing resources become available alongside other sources and destinations.
This guide follows the shortest path: adopt peer-to-peer nodes discovered directly through mDNS, inspect their resources, and take a route.
Before you begin#
You need:
- The NMOS feature enabled.
- Access to create NMOS connections and execute routes.
- NMOS peer-to-peer nodes visible through mDNS.
- At least one sender and one compatible receiver. They can belong to the same node or different nodes.
Adopt discovered nodes#
- Open Connection → NMOS.
- Select Discovered nodes at the bottom of the connection list.
- Find the node that supplies the sender or receiver you want to use. The discovery list shows its type, label, UUID, address, when it was last seen, and how it was discovered.
- Select the node. Select both the sending and receiving nodes when they are separate.
- Select Adopt selected.
The discovery panel closes and the adopted node appears in the NMOS connection list. A newly adopted peer-to-peer node may briefly show Fetching Initial State while its NMOS resources are loaded.
If several records describe the same node, the discovery view combines them so you can adopt the node once.
Confirm the senders and receivers#
- Select the adopted node in the NMOS connection list.
- Open Ports and Bundles.
- Look under Sources for bundles available to route from the node.
- Look under Destinations for bundles available to route to the node.
For a simple example, identify a source such as Camera 1 and a destination such as Engineering Monitor. If the source and destination belong to separate nodes, inspect Ports and Bundles on each connection.
The resource counts and cards come from the adopted node's NMOS data. You do not need to create each sender and receiver as a routing port manually.
Take the first NMOS route#
Selecting Take changes the signal received by the chosen destination.
- Open Routing → Execute.
- Above Sources, use the NMOS node filter to select the adopted node that contains
Camera 1. - Above Destinations, use the same filter to select the adopted node that contains
Engineering Monitor. - Leave Bundles selected.
- Select
Camera 1 under Sources. - Select
Engineering Monitor under Destinations. - Review the staged route and select Take.
A successful request reports Routes executed successfully. The destination's active-source display updates from the state reported by the NMOS receiver.
Adopt a node from a Registry#
When the node is available through an adopted NMOS Registry connection:
- Open Connection → NMOS and select the Registry connection.
- Open All Nodes.
- Find the node and select Adopt.
The node changes to Adopted and appears under Adopted Nodes and in the NMOS connection list. Open the node's Ports and Bundles to inspect its routing resources, then follow the same routing steps above.
Add a node manually#
Use manual setup when a peer-to-peer node cannot be discovered through mDNS, such as a node on another subnet.
- Open Connection → NMOS.
- Select Manual Add.
- Select Node.
- Enter a Label and one or more Node endpoints.
- Leave IS-04 set to automatic selection unless the node requires a specific supported version.
- Select Create.
Endpoints are tried in the order shown. After the connection loads its NMOS data, open Ports and Bundles to inspect the generated resources.
If you get stuck#
What you see | What to try |
|---|
The peer-to-peer discovery list is empty. | Confirm that mDNS discovery is enabled under Settings → NMOS and that the node is announcing on a reachable network. DNS-SD discovers Registries, not peer-to-peer nodes. |
The node remains on Fetching Initial State. | Open the node and check its endpoint and connection status. Use Retry if the page shows No NMOS Data found. |
Ports and Bundles shows no sources or destinations. | Confirm that the node exposes senders or receivers through IS-04 and that its connection is enabled. |
The sender and receiver do not appear together in Routing. | Check the Connections filter above both lists and confirm that the intended connections are selected. |
The route fails. | Open the route details and check the sender, receiver, compatibility, and IS-05 connection state before retrying. |
Where to go next#
