The phrase "codec pipeline" suggests a problem with a defined beginning and end: audio goes in one side, audio comes out the other, and the codecs are the boxes in between. In practice, a broadcast audio codec pipeline i
There is a class of broadcast engineering requirements where the consequences of failure are not a listener complaint or a regulatory annotation — they are a safety risk. Emergency broadcast is that class. When a nationa
Loudness normalization is one of those broadcast topics where the theory is well-documented and the practice is genuinely hard. The standards exist — BS.1770-4, EBU R 128, ATSC A/85, and a collection of national variants
The overnight music block is one of those broadcast engineering problems that looks simple from the outside and becomes progressively harder the more carefully you think about it. The surface description is easy: play mu
There are two categories of on-air error that listeners notice immediately and remember long after the broadcast has ended. The first is a time call that is wrong — by a few seconds, by a minute, or simply by being absen
The public conversation about AI in broadcast tends to focus on the AI host: the voice, the style, the question of whether listeners can tell the difference. That is a reasonable thing to focus on if you are thinking abo
For most of broadcast history, the answer to overnight coverage was simple: there was a person sitting in the studio. Not doing much, usually. Watching a playout system run, ready to press a button if something went wron
There is a particular kind of silence that broadcast engineers dread. It is not the silence of dead air — you can hear that immediately. It is the silence of a station that is technically on air, outputting carrier, but
When we started having the local-versus-cloud conversation with stations in 2023, the standard advice from AI infrastructure consultants was unanimous: use the cloud. Marginal cost pricing, no upfront capital, elasticity
When broadcast engineers talk about dead air, they usually frame it as a technical failure. The playout machine crashed. The audio card locked up. The network path to the remote studio dropped. Something broke. The conve
A few years ago we watched a broadcast compliance incident unfold that had a straightforward cause: a single editor had approved a piece of content under deadline pressure, the editor was also the person who had written
*Reading time: ~18 minutes. Audience: station engineers, program directors, and technology advisors who are evaluating or replacing broadcast automation software.*
The word hallucination in AI discussions almost always refers to factual hallucination: a language model that confidently states something false. A chatbot that invents a court case. A research assistant that fabricates
Every few months someone sends us a link to a demo video: a radio station that has replaced its human DJ with an AI voice. The demo sounds impressive. The voice is natural, the transitions are smooth, the audio quality i
Every few years the broadcast technology industry rediscovers the cloud. The pitch is consistent: move your broadcast automation to the cloud, eliminate on-premise hardware, pay per seat, scale elastically, let someone e
We have been building broadcast automation software since 2005. In that time, we have shipped to more than 500 radio stations across China, survived the transition from tape to digital, watched the rise and fall of half
The broadcast content review process at a Chinese county-level station typically involves three human approval stages, a scheduling review, and a compliance sign-off before a segment is cleared for air. That review takes