Nexus Broadcast software
Purpose-built applications for broadcast engineers, station operators, consultants, and applicants — covering both the RF side of a station and the daily work of running one.
RF engineering software
Browser-based tools for the technical questions broadcasters face when evaluating channels, facilities, and proposed changes.
RF Workbench is the common platform for Nexus Broadcast engineering applications, data services, and calculation tools.
RF Navigator focuses on facility research, translator data, technical comparisons, and broadcast frequency-planning workflows.
Station operations software
Software for the work that happens after the facility is built and licensed: keeping the music library accurate, putting local news and weather on the air, filling the breaks between the records, and controlling what the station shows on the listener's display.
TroveTracks identifies, tags, and screens a station's music library automatically, and keeps it in step with the automation system.
WeatherTrove produces a station's on-air weather breaks automatically, from National Weather Service data through to a finished audio file on the automation system.
VoiceTrove writes and voices a station's between-song breaks about the records actually in the automation queue, and verifies every claim before anything airs.
NewsTrove watches the outlets covering a station's county, writes up the stories you pick four ways, and holds every one of them for approval.
RadioText Pro drives a station's RDS display — now-playing RadioText from the automation system, the station's own messages rotating around it, and Station PS.
The station-operations line is still being built out, and not every station's problem has an off-the-shelf answer. Nexus Broadcast also takes on custom broadcast software, built around how a particular station actually works.
Every Nexus Broadcast application starts from something broadcasters actually have to do. On the RF side that means finding the correct records, comparing facilities, identifying technical constraints, and applying the correct engineering rules. On the operations side it means keeping a music library accurate, getting local news and the weather on the air, filling the breaks between the records, and keeping the listener's display current — the recurring work that has no deadline attached to it and so gets dropped first. The aim in both cases is the same: produce a result you can use, without rebuilding the same workflow by hand every time.