Design & previz software · software
syncronorm Depence troubleshooting
The syncronorm Depence problems live-event techs bring to Ask Roadie most (also called Depence R3, Depence2). 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 Depence 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 →
Console DMX drives fixtures but the Depence timeline / programmer is dead
Likely cause: Overwrite Mode is designed to hand 100% of DMX control to the external console for performance; by design it shuts off internal playback, which looks like a broken timeline.
- Step-by-step fixGet the fix →
Crash when adding objects, fixtures/light library, or video sources; or Asset Library error during install
Likely cause: AV real-time scanning quarantines or locks Depence asset files mid-write, corrupting the library and crashing the app when it loads those assets.
- Step-by-step fixGet the fix →
Depence errors on start or misbehaves unless run as admin
Likely cause: Depence writes to protected program/asset directories and talks to the dongle/network drivers; without admin rights those operations fail.
- Step-by-step fixGet the fix →
Dongle detected intermittently / not found after updating (e.g. 4.0.12+)
Likely cause: The license and 3D subsystems depend on VC++/.NET runtimes; when those are missing the dongle service loads unreliably, producing intermittent not-detected errors.
- Step-by-step fixGet the fix →
Insert the dongle / license not detected at launch
Likely cause: Multiple CodeMeter/USB dongles on one machine can shadow each other so the license lookup grabs the wrong key; a clean single-dongle launch lets Depence bind to its own license.
- Step-by-step fixGet the fix →
Latest version and how updates work
Likely cause: Depence uses a cloud-based asset library and in-app updater, so most fixture and software fixes arrive automatically as long as the machine has internet.
- Step-by-step fixGet the fix →
Project 3D view looks pixelated / low resolution
Likely cause: A mismatched or downscaled internal render resolution makes the viewport look pixelated; pinning it to the screen resolution restores sharpness.
- Step-by-step fixGet the fix →
System / GPU requirements for running Depence
Likely cause: Depence is a GPU-intensive real-time renderer; it is built against NVIDIA drivers, so non-NVIDIA or underpowered GPUs cause poor performance, artifacts, or unsupported behavior.
- Step-by-step fixGet the fix →
Timecode / show-control synchronization and system integration
Likely cause: Depence is both a visualizer and a show controller, so aligning it to house timecode and the right protocol makes external triggers and playback stay frame-accurate.
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 Depence
- 1. Pick the syncronorm Depence. 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.