Buttons lets you rename what you see, not what the connection sends: give every port a clear label for the people who'll actually use it, without touching the underlying source. This page covers reading the Ports Config table, applying labels, and understanding why a port might not be usable yet.
Ports and Labels in the left navigation open the same Ports Config table in two different views: Ports shows type, direction, tags, and warnings; Labels shows the label columns instead. Switch between them from the nav; nothing about the underlying data changes.
Rows are grouped by connection. Each group (for example, an ATEM's Input 1) can expand to show its individual ports underneath. Tags apply to a whole group, not to the individual ports inside it.
An ATEM's native input names ("Input 1", "Input 2"...) don't mean anything to the people building positions or routing panels.
Open Routing → Labels.
Select the row (or rows) you want to relabel. Selecting several rows at once lets you label them together in the next step.
Right-click the selection, then choose Labels → Edit User Label....
Enter a name in Label. If you selected multiple rows, use % in the text to auto-number them: for example, Camera % becomes Camera 1, Camera 2, and so on across the selected rows. Optionally set an Icon and Color.
Select Apply.
Buttons has three separate label types, each shown in its own column in the Labels view:
User: the name people see day to day when building positions and routing panels.
Setup: a name meaningful during installation or configuration, kept separate so it doesn't clutter the operator-facing User label.
Installation: a site-specific name, useful when the same connection type is deployed identically across multiple venues.
A port or group can have one label of each type at once. None of them change the connection's own name for that port: only what Buttons displays.
The Ports view's columns tell you what a port is and whether it's ready to use:
Direction: Source or Destination. This is fixed by the connection; it isn't something you configure.
Type: whether the port comes from a Connection, NMOS, or is Custom.
The pill next to the port count shows its signal type (video, audio, data, or a mux of more than one) as reported by the connection module: also read-only.
Warnings: a warning badge appears when a port can't currently be used, such as when its connection isn't in an OK state or an expected SDP couldn't be fetched.
A Wired badge means the port is already used by a wire and might not be directly routable as a result.
A Disabled badge means the owning connection itself is disabled.
Large connections can expose far more ports than you'll ever route. Select the rows you don't need, right-click, and choose Visibility → Hide. Hidden ports stay hidden until you select them again (via search or a filter) and choose Unhide: hiding doesn't delete anything.
