Last week’s discussions were lively and varied, touching on both technical and industry-specific themes. Members delved into the intricacies of maintaining reliable communication systems, explored the origins of radio jargon, and shared best practices for handling last-minute schedule changes. There was also a focus on technical calibration and the impact of training on audience ratings, reflecting a community keen on both operational excellence and industry knowledge.
This Week’s Hot Topics
IFB and comms that don’t lag
A crucial discussion for anyone dealing with live broadcasts. Members shared tips on ensuring seamless communication without delays. Read more here
Who coined the term drive-time
An intriguing dive into radio history, with members debating who first used this now-common term. It’s a perfect thread for history buffs and radio enthusiasts alike. Read more here
Field-calibrating a VHF repeater preselector
Technical minds will appreciate this practical discussion on optimizing signal clarity in the field. Read more here
Keeping last-minute swaps accurate
A valuable exchange of strategies for managing schedule changes efficiently, ensuring smooth operations even with last-minute updates. Read more here
Verifying RDS injection on-air
A technical thread focused on ensuring accurate RDS data transmission, crucial for maintaining professional broadcast standards. Read more here
Shortest chart-topper you’d spin unpadded
A light-hearted yet insightful discussion about the shortest tracks DJs would play without extra padding. Read more here
Training that actually moves ratings
Members shared experiences and methods of training that have tangibly improved audience ratings, emphasizing effective techniques over theoretical ones. Read more here
Position priorities for cleaner AM drive
A strategic conversation on optimizing morning drive shows to ensure clarity and engagement for listeners. Read more here
Looking forward to another week of insightful exchanges and shared knowledge. Let’s keep the conversations going strong.
For ‘last-minute schedule changes’, we keep a printed backup clock and a Zetta macro that flips to a 30‑minute music block with IDs baked in; it’s saved us twice when the STL hiccuped. If you’re on Rivendell, a simple cron + rmlsend trigger does the same thing without spending a dime.
I remember digging up a 1972 Broadcasting rate sheet that used “AM drive” and “PM drive” in place of “rush hour,” which makes me think it started as sales jargon more than engineer-speak. Small caveat: some diary markets carved those dayparts a bit differently, so local lore varies; if you want receipts, the Broadcasting archive at WorldRadioHistory has examples: https://worldradiohistory.com/Broadcasting-Magazine.htm.
I found our 1985 Arbitron book and rate card both used “AM Drive” (6a–10a) and “PM Drive” (3p–7p), which lines up with agency buys more than engineering slang, @lewis_k9. Tip: spell out your dayparts in the media kit and in your automation labels to avoid cross‑market confusion; some news/talk shops shift PM drive earlier with local traffic. It’s like arguing “soda” vs “pop” — the client’s dialect usually wins.
Quick example: after we tied automation, EAS, and the studio clocks to a GPS‑backed NTP (chrony on a Pi + a cheap u‑blox puck), our:00 network joins stopped clipping and last‑minute bumps didn’t desync the log — that little “calibration” paid off.
But pretty sure it’s sales-driven — ‘drive time’ shows up in RAB/Nielsen daypart grids — but in practice our AQH spikes were 5–9 and 4–6:30, so we priced those tighter than the full blocks, @lewis_k9. Small caveat: news/talk skewed earlier in the morning for us — quick primer here: Dayparting - Wikipedia.
Quick note: when we mapped app starts against Waze traffic peaks, our ‘drive-time’ listening ran 5:20–8:40 and 3:35–6:15, so we nudged top-of-hour stopsets about 5 minutes earlier and reworded promos to ‘Morning Rush.’ It lifted streaming TSL about 6%; small caveat, holiday weeks shift patterns later, so recheck after long weekends.