Playback & media servers · software
Notch troubleshooting
The Notch problems live-event techs bring to Ask Roadie most (also called Notch Builder, Notch VFX). 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 Notch 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 →
Block will not load — SDK / runtime version mismatch (esp. NVIDIA 50-series)
Likely cause: Notch blocks are SDK-locked; a runtime older/newer than the block's SDK — or a GPU that needs a specific AR SDK — silently refuses to load.
- Step-by-step fixGet the fix →
How do I install/update Notch or run multiple versions?
Likely cause: The Launcher is the supported install path; side-by-side versions plus SDK-matched runtimes prevent the version-mismatch load failures blocks are prone to.
- Step-by-step fixGet the fix →
Moving a Notch license between machines / dongle vs software license
Likely cause: Notch splits licensing into account-bound (software) vs hardware-bound (dongle); knowing which you hold determines how it travels between show machines.
- Step-by-step fixGet the fix →
Notch block crashes Hippotizer / Green Hippo
Likely cause: Hippo crashes on blocks are usually SDK/patch mismatch or VRAM overrun; verifying and matching versions isolates the cause.
- Step-by-step fixGet the fix →
What license is needed to run a custom Notch block in a media server?
Likely cause: Blocks carry no playback engine of their own; the host must be licensed to execute custom block code, whereas vendor built-in effects are pre-licensed.
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 Notch
- 1. Pick the Notch. 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.