Capture Issues
Live capture problems usually trace to the capture source, the format the source reports, the network (for NDI®), or the playback node's render performance. Find the section for the capture type you use. For the capture model and multi-node source distribution, see Capture Devices.
Capture Stutters
A stuttering capture is not always the capture's fault. If the GPU rendering frame rate on the playback node is unstable, every cue on that node stutters — captured streams and pre-rendered video alike. Before troubleshooting the capture source, confirm the renderer is hitting the show's target frame rate using the Render Info overlay or the Nodes window.
If rendering is unstable:
- High GPU load — reduce show complexity or free GPU memory.
- Low GPU load but still unstable — the GPU has headroom and something else is blocking frames. Investigate the hardware: PCIe bus errors, motherboard issues, or a faulty PCIe riser card can all cause unstable rendering even when GPU load looks fine.
Generic Capture
USB and MediaFoundation capture devices. See Generic Capture.
| Symptom | Likely cause | Resolution |
|---|---|---|
| Device not listed in Stream dropdown | The device's driver does not support Windows MediaFoundation — the most common cause. Also possible: driver missing, device disabled in Windows, or another application holds it exclusively. | Open the Windows Camera app as a quick test — it uses MediaFoundation too, so if the device shows up there, WATCHOUT should see it. If not, install the manufacturer's MediaFoundation-compatible driver. Close other applications holding the device. Click Refresh. |
| Limited Format options | WATCHOUT only lists formats it can decode (NV12, YUY2, UYVY, RGB24). The device may publish other formats that WATCHOUT does not yet support. | Pick from the formats shown. If the device's native format is not in the list, use the closest available format and accept the runtime conversion, or use a different capture device. |
| Glitchy video on USB devices | USB bandwidth contention or cable quality | Move the device to a dedicated USB controller (a different physical USB hub on the motherboard). Use a shorter, certified USB cable. Lower the format to a smaller resolution. |
| Higher latency than expected | Inconsistent frame timestamps from the device. WATCHOUT holds extra frames so playback stays smooth despite the timing jitter. | Update the device's driver first — newer versions sometimes fix the timestamping. If the jitter persists, replace the device. |
| Colors washed out or crushed | Range override needed | Set Range to Full or Limited explicitly instead of Auto. |
NDI® Capture
Network video sources. See NDI Capture.
| Symptom | Likely cause | Resolution |
|---|---|---|
| Stream not listed in dropdown | Source on a different subnet, or mDNS blocked | Add the sender's IP to NDI® Extra IPs in File > Preferences... Verify the firewall allows mDNS. See NDI Video Sources → Source Discovery. |
| Capture is black or freezes | Network bandwidth insufficient, or the sender stopped transmitting | Check network throughput. Verify the source is actively sending. Try a lower-resolution source. |
| Colors look wrong | Color Space set to Auto and the stream resolution misleads the heuristic | Set Color Space explicitly to match the source (Rec. 601 / 709 / 2020). |
| Audio missing | Audio Channels set to 0, or routing not configured | Edit the source, set the correct channel count, and configure the Audio Route grid. |
| Audio dropouts | Audio Latency too low for the network | Step the Audio Latency up to the next preset value. |
Deltacast VideoMaster
SDI and ST 2110 capture through Deltacast boards. See Deltacast VideoMaster.
| Symptom | Likely cause | Resolution |
|---|---|---|
| No Deltacast inputs in Stream dropdown | Driver not loaded, or board not detected | Verify the board is recognized in Windows Device Manager. Confirm the Deltacast driver is installed. Click Refresh. |
| No ST 2110 inputs in Stream dropdown | Board not commissioned, or PTP not locked | Verify board commissioning in the ST 2110 Interfaces dialog. Check PTP is locked. See Setting Up ST 2110. |
| Subscribed to ST 2110 but no frames | Multicast address or port wrong, or switch IGMP filtering | Verify addressing matches the sender. Confirm the switch has IGMP snooping enabled and is not filtering the multicast group. |
| Black or signal-loss image (SDI) | No signal on the cable, or the connector does not support the signal format | Verify the upstream device is sending. Confirm the connector supports the signal — on Deltacast boards SDI capability is per-connector; some inputs are 12G-SDI while others on the same board are 3G-SDI only. Check the board's specs for which port is rated for the format you are feeding. |
| Colors look wrong | Range or Color Space mismatched | Set Range explicitly to Limited or Full as needed. Pick the source's actual color space instead of Auto. |
Spout
Frame sharing from another application on the same node. See Spout.
| Symptom | Likely cause | Resolution |
|---|---|---|
| Sender not listed in Stream dropdown | Sender not running, or wrong node selected | Confirm the sender is started and publishing. Confirm Node matches the host the sender is on. Click Refresh. |
| Black or frozen image | Sender stopped or paused, or sender is producing at zero alpha | Verify the sender is still actively producing frames. Check the sender's output in its own preview. |
| Colors look wrong | Sender publishes in a different color space than WATCHOUT assumes | Pick the matching Color Space in the source dialog instead of Auto. |
| Cross-GPU error in log | Sender running on a different GPU than WATCHOUT | Move the sender to the same GPU as WATCHOUT, or pin both applications to the same adapter in Windows Graphics Settings. |
Related
- Capture Devices — the capture model and multi-node source distribution.
- Network Issues — discovery and firewall problems that hide NDI sources.
- Performance Tips — keeping the renderer at the show's target frame rate.
- Getting Help — gather diagnostics and contact Dataton support.
NDI® is a registered trademark of Vizrt NDI AB.