> For the complete documentation index, see [llms.txt](https://docs.timeinpixels.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.timeinpixels.com/nobe-omniscope/sources/decklink-and-ultrastudio.md).

# DeckLink & UltraStudio

Nobe OmniScope supports any BlackMagic input card. It will be detected automatically and displayed in the “Connect to…” dialog box.

OmniScope requires **DesktopVideo 10.10 or later**.

Supported input-device examples include **UltraStudio Mini Recorder 12G**, **UltraStudio Recorder 3G**, **UltraStudio 4K Mini**, **DeckLink Mini Recorder 4K**, **DeckLink Recorder 4K**, **DeckLink 4K Extreme**, and **DeckLink 8K Pro**. For newer Blackmagic Design hardware, install the latest Blackmagic Desktop Video driver first.

For a standalone OmniScope machine on Thunderbolt, the **UltraStudio Mini Recorder 12G** is our default recommendation — it captures up to UHD 2160p60 over 12G-SDI and is the most cost-effective capture device for the job. See [Dedicated Scope PC](https://docs.timeinpixels.com/nobe-omniscope/sources/decklink-and-ultrastudio/dedicated-scope-pc.md).

### Checking the current device status

You can check the device in Help / DeckLink window:

![](https://565437294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFqn5MuayPgQPMZ9pwf%2F-MHjfKjAwUcEGmV2I7df%2F-MHjfs63xz5IQdI9KzyJ%2Fos_decklink_status.png?alt=media\&token=7a9b50bf-1270-4d24-be75-2a859f1652e6)

### DeckLink Unavailable Message

If OmniScope cannot access a DeckLink device at startup (for example, the device is in use by another application or the driver is not loaded), the input source will display a clear **"DeckLink unavailable"** status message instead of a blank or generic error. Check that no other application is capturing from the same device, then reconnect the source.

OmniScope also handles the case where a DeckLink device reports no name string — device enumeration will complete normally instead of crashing, and the device will still appear in the source list.

### REC Badge

When a supported DeckLink or UltraStudio source is actively recording, OmniScope shows a **REC** badge on the input tile. Recording state is detected from supported input metadata. This gives you a quick visual confirmation that recording is in progress without needing to open any additional windows.

### Pass-Through and Feedback Flashes

On cards such as the DeckLink 8K Pro that use Desktop Video-managed port profiles, OmniScope correctly preserves the profile on connect and disconnect. If you experienced SDI/HDMI feedback flashes on disconnect or app exit, this was fixed in version 1.11.39.

### Diagnostics View (1.11.19+)

Open Input Settings for a DeckLink or UltraStudio source and select **Diagnostics** to see live signal and device health (format, link, queue state). Use this view when troubleshooting capture stability or pass-through issues.

### Auto signal format detection

In Input Settings, set **Display Mode** to **Auto** to follow the incoming timing and whether the signal is RGB 4:4:4 or YCbCr 4:2:2. **Auto** remains selected after capture restarts or signal recovery, so OmniScope detects the current signal again instead of retaining the previously detected fixed mode. Invalid frames are ignored until the device reports a locked, valid signal.

### Signal Metadata (1.11.61 beta+)

Open Input Settings for a DeckLink or UltraStudio source and expand **Signal Metadata** to inspect what the device and driver report for the current signal. The view includes:

* detected format, scan type, color space, dynamic range and SDI link configuration;
* frame metadata such as EOTF, mastering-display values, MaxCLL and MaxFALL;
* RP188 VITC1, VITC2 and LTC timecode, including user bits;
* decoded ancillary data for AFD and bar data, ST 2108-1 HDR, ST 12-2 ATC, SCTE-104 and ST 352 payload IDs;
* an ANC packet inventory with DID/SDID, line, data space and packet counts.

The available rows depend on the capture device, Desktop Video driver and metadata present in the incoming signal. A missing row or **Not present** value does not by itself indicate a capture problem. Use **Reset** to clear the ANC counters and inventory before checking a new signal.
