Bitfocus AS
logo
logo
Bitfocus AS
logo
logo

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
Co-funded by the European Union

Our Bitfocus Workflow 2.0 project is co-funded by the European Union’s Creative Europe programme. About the project

© 2026 Bitfocus AS. All rights reserved.

  1. Home
  2. Academy
  3. Buttons Foundations
  4. Routing basics

Section 4 of 710 min

Routing basics

Sources, destinations, ports and bundles, why routing changes real signals, and how a route request differs from the state the device reports.

After this section you can:

  • Define source, destination, port and bundle with an example.
  • Explain why taking a route is different from editing a button design.
  • Tell a route request apart from the state the device reports back.
  • Stage a route without taking it.
Routing decides which signal goes where: which camera feeds which output, which audio reaches which destination. In this section you'll learn the words Buttons uses for routing, and why routing deserves more care than anything else you've seen so far.

Sources and destinations#

A source provides a signal: a camera input, a playback output, a router input.
A destination receives a signal: a switcher's program bus, an auxiliary output, a monitor feed, a router output.
A route connects a source to a destination:
Camera 1 → Program
 source    destination

Ports and bundles#

A port is one routable endpoint. For an ATEM, Camera 1 Video can be a source port and Program Video a destination port.
A bundle groups the ports that belong together as one source or destination. An ATEM's Camera 1 bundle can hold a video port and audio ports:
Camera 1 source bundle
├── Video port
├── Audio 1/2 port
└── Audio 3/4 port
Routing Camera 1 to Program as bundles can route every matching port inside them: video to video, audio to audio. Routing only the Camera 1 Video port changes the video and leaves the audio alone.
Bundles and their ports on Routing → Ports: each bundle, such as Oliver, holds a video port and audio ports.
Connections supply their ports and bundles to Buttons. An ATEM connection, for example, offers its inputs as sources, and its program buses, preview buses, auxiliary outputs, multiviewer windows and audio outputs as destinations.

Routing changes real signals#

Everything you've done so far changed configuration. Routing is different: taking a route can change a real output straight away, whether that output goes to air, to a recording or to a screen.
Buttons makes you stage a route first. You select a source and a destination, Buttons shows you which port routes it will make, and nothing changes on the device until you select Take.
While you're learning, only route to a destination that doesn't go to air. On an ATEM, an M/E Preview bus is a good choice: it changes what the switcher shows on Preview, not what goes out.

A request is not the result#

When you select Take, Buttons sends a request and reports the result, such as Routes executed successfully. The device then reports which source is actually active on each destination.
These are two different pieces of information. A request can fail, be blocked, or change only some of the ports in a bundle. The active source the device reports is the truth. If the two disagree, trust what the device reports and investigate.

The Routing area#

The Routing area in the main navigation has four basic pages:
  • Route: select, stage and take routes.
  • Presets: save and recall sets of routes.
  • Labels: give routing resources clear names.
  • Ports: inspect ports and their settings.
More pages can appear, depending on your license and the routing features you use.
Read more in the docs:What is Bitfocus Buttons?,Physical routing,Take a physical route

Try it

In your own Buttons installation.

Stage a route, look at it, and leave without taking it.
  1. Open Connect → Connection, select Practice ATEM and open Ports and Bundles. Find the input bundles and the M/E bundles the module offers, even though no switcher is connected.
Ports and Bundles: sources at the top, destinations below. This switcher was connected, so its names differ from yours.
  1. Open Routing.
The Routing view: source filters (1) and destination filters (2), the Bundles, Ports and Expanded controls (3), sources (4) and destinations (7), and Take at the bottom (8).
  1. Above Sources, choose Connections, then select Practice ATEM. Do the same above Destinations.
  2. Select Bundles. Select an input as the source, such as Input 2, and an M/E Preview as the destination, such as ME 1 Preview.
  3. Look at the button at the bottom. It shows how many port routes are staged: Take 1 route. Switch to Expanded to see the port route the bundles would make: the Input 2 video port to the ME 1 Preview video port.
Staged routes show as green pills, and the button at the bottom counts them. This example has nine staged; yours shows Take 1 route.
  1. Don't select Take. Select the clear button at the bottom right to clear the staged route.
On this ATEM, each input bundle holds only a video port, so one bundle selection stages one route. A bundle with video and audio ports would stage one route for each matching port, and the button would count them all.

Tip

With a test ATEM that isn't used for production, you can select Take in step 6 and watch ME 1 Preview report its new active source. Never do this on a switcher that's on air.

Quiz

Answer the questions for this section. You need 80% to move on.

  1. Question 1
    1.

    In the route Camera 1 → Program, which part is the destination?

  2. Question 2
    2.

    What is a bundle?

  3. Question 3
    3.

    You select the Camera 1 bundle as the source and the Program bundle as the destination. The button reads Take 3 routes. Why three?

  4. Question 4
    4.

    Buttons reports Routes executed successfully, but the destination still shows the old source as active. What should you trust?

  5. Question 5
    5.

    You're learning on an ATEM. Which destination is the safest to route to?

  6. Question 6
    6.

    Which of these changes a live signal the moment you do it?

0 of 6 answered

PreviousVariables and feedbacksNextFinding your way around
Buttons Foundations
  1. 1What Buttons is
  2. 2Positions and surfaces
  3. 3Variables and feedbacks
  4. 4Routing basics
  5. 5Finding your way around
  6. 6Choosing a control method
  7. 7Wrap-up and final quiz

In this section

  • Sources and destinations
  • Ports and bundles
  • Routing changes real signals
  • A request is not the result
  • The Routing area
  • Try it
  • Quiz