> For the complete documentation index, see [llms.txt](https://dynamicshelp.broadstream.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dynamicshelp.broadstream.com/solution-recipes/chapter-index/atem-integration.md).

# Preparing your Blackmagic ATEM switcher to communicate with Dynamic Graphics

Connect Dynamic Graphics to a Blackmagic Design ATEM switcher and route graphics into it via one of four workflows. Dynamic Graphics talks to the ATEM through Blackmagic’s switcher SDK directly; ATEM Software Control is only needed at install time for its drivers, and for a few diagnostics.

## Before you begin

1. Install **ATEM Switchers** (also called **ATEM Control Software**) from [Blackmagic Design’s support page](https://www.blackmagicdesign.com/support/family/atem-live-production-switchers). The installer drops the driver components Dynamic Graphics uses to discover and command the switcher. You do not need to run ATEM Software Control during the show; you only need it installed.
2. Cable the ATEM to the Dynamic Graphics machine. The integration accepts any of:
   * **USB** — connect the ATEM’s USB Control port to the Dynamic Graphics machine. The same cable that carries ATEM Software Control’s connection is what Dynamic Graphics uses.
   * **Network** — connect the ATEM’s **ATEM Control** port to the same LAN as the Dynamic Graphics machine. The ATEM and the Dynamic Graphics machine must be on the same subnet; if you connect them direct with a crossover or short patch, assign both NICs static IPs in the same subnet (not the same address).
3. Decide which workflow you will use — see [Pick a workflow](#pick-a-workflow) below. The cabling above the switcher (Program Out, key/fill lines, ATEM-to-Dynamic Graphics return feed) is workflow-specific.

## Pick a workflow

Open **Settings** > **Blackmagic Design ATEM...**. The **ATEM Settings** dialog opens. The **ATEM Workflow** dropdown picks how Dynamic Graphics talks to the switcher. Four workflows are supported:

| ATEM Workflow             | What it does                                                                                                                                                                                                                                                 |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Downstream Keying**     | Dynamic Graphics periodically sends still images to the ATEM, which overlays them onto the ATEM’s final output. Graphics live in the ATEM’s media pool and the ATEM is the final compositor. Best when the ATEM is your show’s master.                       |
| **Upstream Chromakeying** | Dynamic Graphics sends video to the ATEM via HDMI or SDI, and the ATEM runs upstream keying on that input. Dynamic Graphics delivers a fill feed; the ATEM keys it. Use this when the ATEM has spare HDMI/SDI inputs and you want the ATEM to do the keying. |
| **Media Capture**         | The ATEM’s Program output appears inside Dynamic Graphics as a media input source. In this workflow, Dynamic Graphics is the final compositor — the ATEM’s mix becomes a layer underneath Dynamic Graphics’s graphics.                                       |
| **Key and Fill**          | Dynamic Graphics sends SDI Key and Fill to the ATEM for downstream keying. The actual keyer-to-fill assignment lives inside ATEM Software Control; configure it there, then point Dynamic Graphics at the matching ATEM input here.                          |

## Connect the ATEM

In the same **ATEM Settings** dialog, set **Connection Method**:

| Connection Method               | When to use                                                                                                                                                                                                                                  |
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Auto Connect**                | Recommended. Dynamic Graphics tries USB, then any saved IP, then mDNS discovery on the local network. Picks up most cabling automatically.                                                                                                   |
| **Network - Manual IP Address** | Use when you have multiple ATEMs on the network, when discovery is unreliable, or when the ATEM lives behind a router/VLAN where mDNS won’t cross. Enter the ATEM’s IP in **Manual IP Address** — **not** the Dynamic Graphics machine’s IP. |
| **USB Only**                    | Forces the integration to the ATEM’s USB Control port and skips network discovery.                                                                                                                                                           |
| **Disabled**                    | Turn the integration off without closing the dialog.                                                                                                                                                                                         |

Connection is established the moment you change the dropdown; there is no separate **Connect** or **OK** button. The status line under the combo updates as Dynamic Graphics discovers the device. Look for one of:

* **ATEM connected via USB**
* **ATEM connected to network (\<IP>)**
* **Not connected. No ATEM devices found.** — Dynamic Graphics reached the SDK but found no switcher. Re-check cabling and Connection Method.
* **Not connected. ATEM drivers are missing.** — the ATEM Switchers installer hasn’t been run on this machine, or the install is incomplete. Re-install ATEM Switchers from Blackmagic Design.
* **ATEM support is disabled.** — **Connection Method** is set to **Disabled**.

## Configure the workflow

Each workflow exposes its own panel of options under the workflow selector. Set them after you pick the workflow:

### Downstream Keying

When Dynamic Graphics pushes stills into the ATEM’s media pool, you choose the range of pool slots Dynamic Graphics is allowed to use:

* **First Assignable ATEM Still** — the first pool slot Dynamic Graphics will write to.
* **Last Assignable ATEM Still** — the last pool slot in the range.

Anything outside this range is left alone, so you can reserve stills for content that was loaded by hand in ATEM Software Control.

### Upstream Chromakeying

* **ATEM input** — pick which physical ATEM input is carrying Dynamic Graphics’s feed.
* **Key** — pick the key style: **Luma**, **Chroma - Blue**, or **Chroma - Green**.
* **Automate** — when set, Dynamic Graphics commands the ATEM keyer on and off as graphics take and clear, so you don’t have to drive the key from ATEM Software Control or the panel.

### Media Capture

No extra options. The ATEM Program feed shows up as a media input you can place on a graphic layer the same way you would any other live source. See [Use live video sources](/set-up-your-production/chapter-index-2/play-live-video-source-layers.md) for how to add it to a project.

### Key and Fill

Configure the keyer assignment inside ATEM Software Control — that is where the ATEM accepts Key and Fill source pairs. Inside Dynamic Graphics, only the Connection Method and the SDI Key + Fill output need to match what you configured in ATEM Software Control.

## Piggyback ATEM transitions onto Dynamic Graphics transitions (optional)

Under **Transitions**, click **Configure Piggybacking...** to open the **ATEM 'Piggyback' Transitions** dialog. Piggybacking ties an ATEM transition (mix, dip, wipe, sting, DVE) to a Dynamic Graphics transition: when the ATEM operator fires that transition on the switcher, Dynamic Graphics simultaneously plays the title you assigned, timed and styled with it.

For each ATEM transition you want to piggyback:

* Choose the Dynamic Graphics title to overlay in the **Choose the title graphic to overlay this ATEM transition effect** dropdown.
* Tick **Reverse** if you want the title’s transition direction reversed.

Click **Enable** to commit. Use **Disable** on this dialog to turn piggybacking off without losing your assignments.

## Verify the integration

1. Watch the status line in the **ATEM Settings** dialog read **ATEM connected via USB** or **ATEM connected to network (\<IP>)**.
2. Play a title and confirm the ATEM is doing what the workflow promises:
   * **Downstream Keying** — the title appears on the ATEM’s Program output (not just inside Dynamic Graphics); the still you can see in ATEM Software Control’s Media pool matches the title that’s on air.
   * **Upstream Chromakeying** — the ATEM keys Dynamic Graphics’s feed cleanly on the input you assigned; if you set **Automate**, the ATEM keyer turns on as the title takes.
   * **Media Capture** — the ATEM’s Program feed appears as a placeable input inside Dynamic Graphics; what you see on the Dynamic Graphics input matches the ATEM’s mix.
   * **Key and Fill** — the ATEM’s downstream keyer composites Dynamic Graphics’s key + fill correctly; tweak the keyer in ATEM Software Control if the edges aren’t right.
3. If you use piggyback transitions, fire the ATEM transition you assigned and confirm the matching Dynamic Graphics title plays in step.

## Troubleshooting

* **Drivers missing** — install ATEM Switchers from Blackmagic Design. The Dynamic Graphics dialog will surface a **Visit [www.blackmagicdesign.com/support/](http://www.blackmagicdesign.com/support/)** link when it detects this.
* **No ATEM devices found** — confirm the ATEM is powered on, confirm the cable is in **ATEM Control** (not the program return port), and try toggling between **Auto Connect** and **USB Only** / **Network - Manual IP Address**.
* **Network discovery fails on a flat LAN** — switch to **Network - Manual IP Address** and enter the ATEM’s static IP. Ask your network admin which subnet the ATEM lives on if you don’t already know.
* **Piggyback transitions don’t trigger** — open the Piggyback dialog and confirm you clicked **Enable**; the dialog persists assignments even when piggybacking is disabled.

## Related

* [Output graphics with SDI](/set-up-your-production/chapter-index/output-graphics-with-sdi.md) — the SDI Program Out side of **Key and Fill**.
* [Use live video sources](/set-up-your-production/chapter-index-2/play-live-video-source-layers.md) — placing the ATEM as a source for **Media Capture**.
* [vMix recipe](/solution-recipes/chapter-index/vmix-recipe.md) — the equivalent end-to-end recipe for a vMix-based hub.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dynamicshelp.broadstream.com/solution-recipes/chapter-index/atem-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.