Playback & media servers · software
dT Videolabs SimpleSync troubleshooting
The dT Videolabs SimpleSync problems live-event techs bring to Ask Roadie most (also called Simple Sync). 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 SimpleSync 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 →
Which Command Type should I use — Direct Command or Clock Sync?
Likely cause: Manufacturer describes the two modes' trade-offs directly; Delay exists to give all clients time to arm before the synchronized start.
- Step-by-step fixGet the fix →
Clips slowly drift out of sync during long or looping playback
Likely cause: PlaybackPro Plus X decodes via QuickTime off each Mac's real-time clock; if clocks drift apart mid-clip the frames separate.
- Step-by-step fixGet the fix →
How do I verify the machine clocks are actually synchronized for Clock Sync?
Likely cause: A machine that will not correct back to server time is not reaching NTP, which would let its clock drift and break Clock Sync.
- Step-by-step fixGet the fix →
How many copies of SimpleSync X should run, and where?
Likely cause: SimpleSync X is the single command server; more than one server competing for the same clients causes unpredictable cueing.
- Step-by-step fixGet the fix →
Keyboard beeps/click sounds when typing clip numbers into SimpleSync X
Likely cause: The alert tone is a macOS UI sound, not a SimpleSync error; turning off UI sound effects silences it.
- Step-by-step fixGet the fix →
The "SimpleSync X" option is not visible under Network Setup in PlaybackPro Plus X
Likely cause: SimpleSync X uses Bonjour over Ethernet for discovery; a wrong subnet, Wi-Fi in the mix, a hub, or firewall block prevents the client from ever seeing the server.
- Step-by-step fixGet the fix →
What macOS versions and licensing does SimpleSync X require?
Likely cause: Manufacturer compatibility/licensing facts; version-matching to the current PBP X release avoids protocol mismatches.
- Step-by-step fixGet the fix →
Machines will not connect or sync reliably across different Macs
Likely cause: Manufacturer requirement; protocol and timing behavior are only guaranteed matched across identical app/OS builds.
- Step-by-step fixGet the fix →
Recommended network configuration for a SimpleSync rig
Likely cause: A clean, static, wired gigabit network with firewall exceptions is what Bonjour discovery and low-latency cueing need; hubs and Wi-Fi introduce collisions and latency.
- Step-by-step fixGet the fix →
SimpleSync commands do nothing / clips will not recall on the clients
Likely cause: SimpleSync addresses clips by their field; without matching alphanumeric clip numbers there is nothing for the command to target.
- Step-by-step fixGet the fix →
Machines are not staying in sync
Likely cause: Sync failures are almost always version mismatch, wrong command mode, or clock drift.
- Step-by-step fixGet the fix →
Can I use SimpleSync for a Primary/Backup (main+backup) pair?
Likely cause: SimpleSync has no failover logic; the DT18 is the supported primary/backup solution.
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 SimpleSync
- 1. Pick the dT Videolabs SimpleSync. 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.