Install and first launch
Confirm Gatekeeper, media-folder access, the intended station, machine-local audio hardware, and stopped first-launch behavior.
AirchainAirchain 0.9.0 · Beta 71 · Build 89
Help prove Airchain where radio happens.
This controlled beta is about more than opening the app. We need operators and engineers to exercise Airchain with representative schedules, real audio paths, deliberate clock boundaries, and a tested fallback—then tell us exactly what happened.
What we need from testers
Real conditions.
Useful evidence.
The best test is controlled, repeatable, and close enough to the station’s actual workflow to expose timing, media, routing, and operator problems before general release.
Audio and routing
Test every Program and Preview route while stopped, verify sample rate and clock source, then use representative audio through the complete on-air path.
Imported schedules
Review a real music schedule from any scheduling system that can export a supported text log, preserve repeated and same-time events, exercise live refresh, and confirm missing supported media remains in authored order.
Timing and transitions
Exercise Cue In, Downbeat, Intro, EOM, EOF, pitch, segues, breaks, one-shots, and Hard, Soft, and Hold Time Sync behavior.
Long-form operation
Run at least eight continuous AUTO hours with music, imaging, overlaps, short elements, long-form audio, and normal operator interaction.
Local safety
Build the 15-minute protected local-media horizon for network-backed audio, disconnect the source in a controlled test, and confirm protected content continues locally.
Records and recovery
Review History and Daily Playback Logs, retain each matching .tsv and .tsv.manifest.json export pair separately from normal diagnostics, relaunch after a controlled interruption, and verify honest terminal outcomes.
Remote, if approved
Use the same Build 89 on both Macs over a trusted LAN or private VPN; exercise role boundaries, authoritative Studio state, and safe unknown-outcome handling.
Current beta focus
Prove the queue stays responsive.
- Accumulate at least 7,000 rowsKeep at least 900 future rows in the working queue.
- Run five corrective Soft Sync cyclesExercise removal, tail removal, and reorder corrections without losing target or successor identity.
- Allow at least three automatic live refreshesVerify authored order, exact occurrence identity, committed audio, and timing continuity remain intact.
- Require zero correlated UI stallsNo
ui_main_thread_stallat a Soft Sync or automatic refresh, and no audible discontinuity.
A successful controlled run
Air stays clean.
The evidence agrees.
- Eight continuous AUTO hoursRepresentative music, imaging, overlaps, short elements, and long-form audio.
- No audible discontinuityNo unexplained gaps, late or duplicate starts, engine resets, or missing as-played entries.
- Responsive under real workSchedule review, refresh, editing, library work, and diagnostics remain usable without compromising playout.
- Predictable safeguardsAmbiguous time, invalid structure, missing media, unavailable routes, and stale Remote state produce the documented safe result.
When something goes wrong
Report the moment,
not just the symptom.
Protect air
Move to the tested fallback and stop or isolate Airchain when safe.
Preserve context
Note the exact local time, operator action, expected result, station, mode, Current, Next, and whether the issue was audible or visible.
Collect evidence
Use Help → Copy Support Information and Help → Collect Diagnostics while Airchain is still open. Preserve the affected exported schedule.
Send the report
Email airchain@caldercreativemedia.com. Review diagnostics first and never send passwords, access keys, Keychain contents, or licensed audio.
Before operating
Read the build record.
Beta 71 has deliberate compatibility boundaries and known issues. Review them before installing or returning a test machine to air.