Playback & media servers · software
Playdeck troubleshooting
The Playdeck problems live-event techs bring to Ask Roadie most (also called Play Deck). Pick your symptom, or describe your own in plain words, and get the likeliest fix first, with the manual page when there is one.
Common Playdeck errors & problems
What techs run into most, and what's usually behind it. The step-by-step fix for your exact software is in Ask Roadie.
- Step-by-step fixGet the fix →
A clip stops early and skips to the next clip in the playlist
Likely cause: Realtime SDI/UDP/RTMP output must keep continuous timing, so the engine will not block indefinitely on a stalled read - after a 3s recovery window it advances.
- Step-by-step fixGet the fix →
After disconnecting Remote Desktop (RDP) to a headless PLAYDECK PC, playout/NDI/streams stop or PLAYDECK hangs on reconnect
Likely cause: Previews need a live display device; RDP yanking its virtual display out from under the render pipeline on disconnect crashes it.
- Step-by-step fixGet the fix →
ATEM switcher not found by PLAYDECK (for ATEM DSK cue/play trigger)
Likely cause: PLAYDECK talks to the ATEM through Blackmagic's installed control libraries over IP; without the 9.x software, a matching subnet, or a USB link it cannot discover the switcher.
- Step-by-step fixGet the fix →
Clips will not load or there is no video output at all
Likely cause: No output almost always traces to a broken GPU decode path - a stale driver, wrong GPU selected, or a laptop where NVIDIA only offloads and cannot be the exclusive decoder.
- Step-by-step fixGet the fix →
Colored popup "PLAYDECK could not be started" - missing/corrupt install files, no UI
Likely cause: The error means startup files or settings are missing/corrupt; reinstalling restores the binaries and the reset option wipes a corrupt cache/config that would otherwise re-break startup.
- Step-by-step fixGet the fix →
GPU not found / not listed in PLAYDECK
Likely cause: PLAYDECK enumerates GPUs through the WMI CIMV2 namespace; if the user account lacks WMI read rights or the driver is missing, the card cannot appear.
- Step-by-step fixGet the fix →
Green blocks/areas in the preview and output
Likely cause: Intel GPUs mis-handle certain codecs, producing green macroblock artifacts (and wrong SD aspect ratios); CPU decode is a correct, if heavier, fallback path.
- Step-by-step fixGet the fix →
PLAYDECK will not start - Windows "Error" popup showing Internal Error or Memory Error, no UI appears
Likely cause: PLAYDECK uses an advanced license-protection layer that AV engines flag as a false positive and block; whitelisting both the UI and engine binaries lets them launch.
- Step-by-step fixGet the fix →
Popup "ACTION REQUIRED. We could not connect" - UI loads but engine will not connect
Likely cause: The UI and the separate PlaydeckEngine process communicate over local network sockets; a firewall blocking either binary breaks that link.
- Step-by-step fixGet the fix →
ProRes, DNxHD, HAP or MXF clips stutter or overload the CPU
Likely cause: ProRes/DNxHD/HAP/MXF have no GPU decode path on Windows so they tax the CPU; transcoding to H.264/AV1 moves decode onto the GPU.
- Step-by-step fixGet the fix →
Stuttering playout / audio hiccups traced to the PC or Windows
Likely cause: Pinning high performance and removing contention keeps decode/output real-time.
Not on the list? Describe it your way, or paste the error code off the display. Ask Roadie works the problem with you until it's fixed or you have a clear next move.
How Ask Roadie helps with the Playdeck
- 1. Pick the Playdeck. It's already in the list.
- 2. Describe what you're seeing. In your own words, or the error code off the screen.
- 3. Get the likeliest fix first. Steps in order, the manual page when there is one, and a note when other techs have confirmed it.
- 4. Still broken? Tap 👎 and it keeps going from where you left off.