Diagnostics

What it's for — Diagnostics is the runtime health dashboard for your CueSync installation. It surfaces beat pipeline timing, output connection history, the error feed, system resource usage, and a self-test so you — or support — can pinpoint problems quickly. The screen is enabled by a launch flag; it does not appear in the navigation bar unless CueSync was started with diagnostics mode on.

The screen, region by region

The screen is a single scrollable column. Sections appear in this order:

Health banner — A colour-coded bar at the top: green (Healthy), amber (Warning), or red (Critical). This reflects the worst condition of any monitored subsystem.

Beat pipeline timing — Three cards showing median, 95th-percentile, and worst-case latency for the cue-fire pipeline, the Auto Pilot engine, and the waveform renderer. Values turn amber above 5 ms and red at the budget limit (5 ms for beat processing, 16 ms for waveform frames). A "Waiting for beats" message shows until a Pioneer player or the internal clock starts sending events.

Active warnings — Only visible when at least one warning is active. Each entry shows the source system and the warning text. Warnings auto-clear when the underlying condition resolves.

License — The current license state, edition, offline grace remaining (if any), and the most recent validation failure reason. Use this when troubleshooting "why aren't my cues firing?" — the edition shown here is the one CueSync is actually enforcing.

Hardware telemetry — Displays the exact non-identifying data CueSync sends with each license revalidation check (boolean flags and low-cardinality strings — no serial numbers, MAC addresses, or unique identifiers). This is a transparency surface; nothing here can be changed from within the app.

Connection health — Per-output uptime statistics: 1-hour and 24-hour uptime percentages. An output flagged as "FLAPPING" is connecting and disconnecting repeatedly — check the cable or the target software.

Error feed — A timestamped list of the 20 most recent errors across all subsystems, with a live errors-per-minute rate. Amber above 5 per minute, red above 20. Use the Clear button to reset the feed (useful after fixing an issue to confirm it stops producing errors).

Recent connection events — A timestamped log of connects, disconnects, and circuit-breaker trips for all outputs. Entries appear here the moment an event occurs.

System resources — CPU usage and heap memory (used / max). Both turn red when above 90 % of their budgets.

Self-test — Runs a built-in validation suite: cue pipeline firing test, connectivity ping to each configured output, and cue readiness check. Results show pass/fail with latency detail for each output. Click Run Self-Test to trigger a run; the button is disabled while a test is in progress.

Analysis cache — Memory and disk entry counts and disk size for the track-analysis cache. Only visible once a Pioneer player has connected and cache activity has started.

Waveform cache — Status (Inactive / Cold / Warming / Hot), entry count, hit count, and hit rate for the waveform tile cache. "Hot" means 80 % or better hit rate. Visible even before a CDJ connects so you can monitor cache behaviour after toggling the dev flag.

Library batch analyse — Shows the result of the most recent library-wide analysis run: total tracks, successes, failures, mean and p99 processing time. Shows "Awaiting first run" until you trigger a batch analyse from Track Prep.

Audio subsystem — Active clip count (out of 8), transport state, selected output device, and live peak and RMS level bars. Helps correlate "audio isn't playing" with concrete subsystem state.

GrandMA 3 feedback — Appears only when at least one GrandMA 3 console connection is configured. For each console: the last reported cue, reconciliation status (In sync / Drifted), and the age of the last feedback message. "Never" or "last feedback Xs ago" over 10 seconds indicates the console's OSC output is not configured.

Execution heatmap — Post-show visualiser of when and how often cues fired across the beat grid. Includes a Export CSV button that writes the heatmap to ~/.cuesync/heatmaps/ for post-show analysis.

Common tasks

1. Check latency before a show — Expand the beat pipeline cards and confirm p95 is under 5 ms. If a value is amber or red, look at the active warnings and error feed for the cause.
2. Diagnose a failing output — Find the output in the Connection Health section, note its uptime percentage and whether it is flapping. Then scroll to Recent Connection Events to see the exact timestamps of its disconnect and reconnect cycles.
3. Confirm license and edition — Read the License section. The edition shown is what is active right now. If a feature gate is blocking you unexpectedly, the validation failure reason here is the starting point for support.
4. Run a pre-show self-test — Click Run Self-Test. All pipeline and connectivity checks should pass. A failed connectivity result means the output address or port is wrong, or the receiving software is not running.
5. Export an execution heatmap after a show — Scroll to the Execution Heatmap section and click Export CSV. The file appears in ~/.cuesync/heatmaps/ with a timestamp in the filename.

Tips & gotchas

• Diagnostics mode is a launch flag, not a user toggle. The screen does not appear unless CueSync was started with the diagnostics system property enabled. Check with the person who set up your CueSync install.
• Clearing the error feed does not fix anything. It only resets the display. If errors reappear immediately after clearing, the underlying issue is still active.
• The waveform cache "Inactive" status is normal when no tracks have loaded yet. It switches to "Cold" (first renders) and then rises toward "Hot" during a session as the cache fills.
• GrandMA 3 "Drifted" means CueSync sent a different cue than the console is reporting. This can happen if the console accepted a manual override between cue fires. In sync after the next matched fire is normal.

Related

• Network Outputs — Add and test outputs; view the Monitor tab for live latency graphs
• Devices — At-a-glance output health and PRO DJ LINK device status
• Settings — Tune timecode source timeout, audio pre-fire offset, and other parameters that affect the values shown here