Bitfocus AS
logo
logo
Bitfocus AS
logo
logo
Sign upSign in

Loading...

Bitfocus

Subscribe to our newsletter

The latest news, articles, and resources, sent to your inbox.

FacebookInstagramGitHubYouTubeLinkedIn

Products

  • Buttons
  • Companion

Integrations

  • Supported Devices
  • Developer Community
  • Connection Development

Support

  • Support Overview
  • Documentation
  • Video Tutorials
  • Community Forum

Sales

  • Resellers & Integrators
  • Buttons Pricing

Updates

  • Case Studies
  • Events & Trade Shows
  • Press Releases
  • Product Updates
  • Webinars

Legal

  • Legal Overview
  • Privacy Policy
  • Buttons EULA
  • Terms & Cookie Policy

Company

  • About us
  • Press kit
  • Careers

© 2026 Bitfocus AS. All rights reserved.

Take a physical route
Docs for
Overview
Getting started
What is Bitfocus Buttons?
Install Buttons and get started
Manage your Buttons license
Activate Buttons offline
Find your way around Buttons
Create your first backup
Add an ATEM connection
Choose a control method
Choose an installation path
Install Buttons on Debian or Ubuntu
Understand HA clustering
Kubernetes HA
Update or remove Buttons
Positions
Understand positions
Create a position
Add controls and sections to a position
Create your first button
Use a connection's presets
Build more capable button actions
Add more feedback to a button
Organize controls in a section
Shift Section
Organize controls with a Folder Section
Add a Popover Section
Build and reuse a Shared Section
Build a Router Section
Understand Custom Routers
Custom Router panel
Surfaces
Surface compatibility
Add and attach a surface
Device orientation
Connections
Update a connection's module safely
Monitor and troubleshoot a connection
Router integrations
VideoHub and AJA KUMO
Utah Scientific BPS
Generic SW-P-08
Nevion VideoIPath
Arkona BLADE//runner
Routing
Physical routing
Configure ports and labels
Take a physical route
Understand route status
Topology graph
Routing Presets
Get started with virtual routing
Configure Nested Shapes
Reverse routing
Tielines
Routing Projects
Routing settings
Troubleshoot a route
Tally
Understand the Tally system
Send ATEM tally and labels to a UMD
Interpret Active Tally state
TSL/UMD connections
Diagnose tally problems
NMOS
Understand NMOS in Buttons
Connect Buttons to an NMOS Registry
Built-in Registry Server
Configure NMOS connections
Discover and adopt
Browse the NMOS inventory
Manage NMOS multicast addresses
Diagnose NMOS problems
Understand Cuelists
Build a Cuelist
Read and advance a running Cuelist
Control a Cuelist from a Position
Workflows
Understand workflows
Build your first workflow
Reuse a group of workflow nodes safely
Troubleshoot a workflow
Recipes
Sequence a timed automation
Call an HTTP endpoint from a workflow
REST endpoint
Use variables
Understand variable scope
Understand nested variables
Update expressions for v1.8
Plan and use Tags
Access
Create and manage users
Create roles and assign permissions
Grant access to specific resources
Show different controls by role
Sessions
Set up PIN and NFC sign-in
SSO
Get started with SSO
Connect a generic OIDC provider
Connect LDAP or Active Directory
Map identity claims to roles
Secure a Buttons deployment
Integrations
External control
Connect to Bitfocus Listener
USB Relay
Install USB Relay on Windows
Install USB Relay on macOS
Install USB Relay on Linux
Install USB Relay on a Raspberry Pi
Get started with the Control API
Secure and monitor the Control API
Control API reference
API reference
Administration
Enable and manage installable features
Services and health
Configure and monitor scheduled backups
Restore a backup and verify it
Export or import Buttons configuration
Store and rotate connection secrets
Replace the HTTPS certificate
HA backup and recovery
Settings
Collect support information
Reference
Glossary
Button Inspector reference
Network ports reference
Expressions
Internal actions reference
Routing Presets panel reference
Startup configuration reference
Workflow nodes
Connection workflow nodes
Workflow workflow nodes
Internal workflow nodes
Position workflow nodes
API workflow nodes
Utility workflow nodes

Loading...

Previous
← Configure ports and labels
Next
Understand route status →
Contact support →
You are viewing documentation for Buttons 1.8.See the docs for Buttons 1.6
Buttons/Routing/Take a physical route

Take a physical route

Select a source and destination in the Routing view, inspect the staged mapping, then use Take to send the route to the connected system. This example routes a non-production ATEM input to an M/E program destination.

Warning

Taking a route can immediately change an output used on air, in a recording, or on a display. Use a destination that is not carrying a production signal while following this guide.

Before you begin#

  • Add a working router-aware connection. To follow the example, use an ATEM connection with M/E routing resources enabled.
  • Make sure the source and destination appear in Buttons and have useful display labels.
  • Choose an ATEM M/E or output that is not in production.
  • Confirm that your account can execute routes.
See Understand physical routing for the difference between sources, destinations, ports, and bundles.

Open the connection's routing resources#

  1. Open Routing.
  2. Above Sources, choose Connections, then select the ATEM connection.
  3. Above Destinations, choose Connections, then select the same connection.
  4. Leave Bundles selected.
The source bundles appear on the left and destination bundles on the right. For this example, identify Input 2 and ME 1 Program, or the equivalent labels supplied by your ATEM.
This toggle actually has three modes: Bundles groups active links per bundle with rows collapsed, Ports lists individual ports with rows still collapsed, and Expanded does the same as Ports but with every bundle row already expanded to its port rows, so you don't need to expand each one by hand. The wire, routing-rule, and tally quick-setup dialogs elsewhere in Buttons keep a simpler two-way Bundles/Ports toggle, where Ports there behaves like Expanded here.

Stage the route#

  1. Select the Input 2 source bundle.
  2. Select the ME 1 Program destination bundle.
Buttons expands the bundle selection into compatible source-port-to-destination-port mappings. These mappings are staged: the connected ATEM does not change until you select Take.
The button at the bottom shows how many port routes are staged, such as Take 1 routes. A bundle selection can stage more than one route when both bundles contain several compatible ports.

Tip

Before taking a bundle route, switch to Ports (or Expanded, to see every bundle row already opened up) and inspect the staged port mappings. This reveals every endpoint that the bundle selection will change.

Take the route#

  1. Confirm that the staged source, destination, and route count match the intended change.
  2. Select Take.
While Buttons sends the request, a progress message appears. A successful result reports Routes executed successfully and the number of routes executed.
The destination's active-source display then updates from the state reported by the ATEM. For this example, ME 1 Program should report Input 2 as its active source. The success message describes the execution result; the active-source display shows the resulting state received from the controlled system.

Route only one part of a bundle#

Selecting a whole physical bundle includes its compatible ports. Use individual ports when only one level should change.
For example, if a source and destination bundle both contain video and audio ports, you can change the video while preserving the destination's current audio:
  1. Switch from Bundles to Ports.
  2. In the filter control, leave Video on and turn off Audio, Data, and any other roles that are not part of the change.
  3. Select the source's video port.
  4. Select the destination's video port.
  5. Confirm that the Take count includes only the intended video mapping.
  6. Select Take.
Because the audio ports were not selected, they are not part of the route request. This is a video breakaway rather than a route of the complete bundle.

Inspect the result#

Buttons reports one of these outcomes:
  • Routes executed successfully: every requested port route succeeded.
  • Route execution failed: none of the requested routes succeeded. Select View Details for the routing report when available.
  • Routes executed with errors: some routes succeeded and others failed. Buttons opens the report so you can identify the affected mappings.
For a partial result, check the report and the active source shown for each destination port before deciding which mappings to retry.

Change what remains selected#

Under Options → After Take, choose what the Routing view should retain after execution:
  • Clear selection after take
  • Clear destinations after take
  • Clear sources after take
  • Keep selection
This setting changes the next selection shown in the Routing view; it does not change the route that was already executed.

Where to go next#

  • Save and execute a set of routes as a routing Preset.
  • Add a Router Section to a position for operational routing.

Was this helpful?

Was this helpful?

0 of 0 users found this page helpful