It's a Memorial Day Nonstop Commercials Marathon... 😄Tuned into the hard-right conservative radio station this a.m. All it's running at 8:48 a.m. CT is commercials and promos.
No content whatsoever.
All commercials.
Has been running since 8:30 a.m.
Tuned into the hard-right conservative radio station this a.m. All it's running at 8:48 a.m. CT is commercials and promos.
No content whatsoever.
All commercials.
Has been running since 8:30 a.m.
The automation was not happy. It was skipping events.You would think that someone on the staff listens to the station occasionally.
How about a system that calls the GM or someone else when the automation malfunctions?
The automation was perfectly happy, it had audio and a source was on the air. It just wasn't detecting the secondary cue or the stop cue.
The FM was easy listening, so the rock jocks who worked on the AM probably didn't want to bother with the FM as they were too busy being a star in their own minds and tolling for chicks.
Except... this wasn't at a small town or an inconsequential radio station.Sounds like many here, with an exception or two are perfect themselves, never make mistakes, dont understand how things work and have no grace for others.
I aint perfect, and i get sloppy sometimes too. I know no one at KLBJ and have no dog in this fight.. but crap happens sometimes.
Except... this wasn't at a small town or an inconsequential radio station.
This was the large metro area's major (and almost only) talk radio station in one of the Top 10 fastest-growing U.S. cities.
Sounds like someone should lose their job, or receive a stern reprimand, allowing a station to go on "autopilot" repeating commercial after commercial ad nauseum during MORNING DRIVE.
When I was in radio, someone would've been dismissed over this.
Of course, it was a holiday, but still... no one's minding the store?
With the radio industry's revenue at about one-third of that of 20 years ago, stations don't have "live staff" all the time. And stations on "auto pilot" can have things happen that are not predictable and are not the fault of a particular person.Sounds like someone should lose their job, or receive a stern reprimand, allowing a station to go on "autopilot" repeating commercial after commercial ad nauseum during MORNING DRIVE.
Chances are that this was a malfunction, not human error.When I was in radio, someone would've been dismissed over this.
Of course, it was a holiday, but still... no one's minding the store?
A story from my past at KTRH in Houston, in its all-news incarnation.this is hardly a lose your job situation, i dont care that its austin.....this is an unfortunately ... easy mistake to make. someone needs a talking to, but id barely call it a reprimand.
So, yes, people can lose their jobs over technical faults - not because of the faults, but because they failed to take action to react to them.
A story from my past at KTRH in Houston, in its all-news incarnation.
In the summer of 1985, KTRH obtained permission for remote control of its transmitter site at Dayton from the studios at 510 Lovett Blvd. in Houston. Previously, operators with first-class tickets pulled 12-hour shifts at Dayton to monitor the station. They kept their jobs; they were just moved to 510 for board-operator and production work. The engineering staff rigged up a fail-safe at Dayton: two reels of public-domain beautiful-music tapes. They thought it would never be needed.
One morning, a 69-cent Sprague "Atom" capacitor blew in one of the audio processors (either Optimod or Dorrough, I forget which). No audio came through. The tapes were triggered. In morning drive.
There was an editor and news assistants and two anchors on duty. The editor had de facto management responsibility until the managing editor came in. Aforesaid managing editor's clock radio turned on at 6 o'clock. Instead of the hourly CBS newscast, there was music. Managing editor calls the newsroom. Managing editor talks to the morning editor. Managing editor asks the morning editor if they have called the engineer on duty. The answer was "no". Managing editor tells morning editor to do that. Then the managing editor gets dressed as fast as possible and rushes to 510.
Managing editor sees morning editor, news assistants, and anchors sitting, not doing anything. Managing editor makes some more calls, gets an engineer in, and the station finally gets back to normal programming about 7:30.
The news assistants didn't lose their jobs. Nor did the anchors. The engineers who came up with the fail-safe system weren't fired. (They were told to come up with another system!) The morning editor was fired, because they had the responsibility delegated to them to ensure that the news wheel was being aired but, instead, seemed not to know what to do.
(Your smart-aleck correspondent asked at the time why there wasn't a phone line to the Dayton site that we could dial up and feed audio to; anticipating dial-up modem technology, I guess. But such a thing wasn't in place, though I believe it would have been possible.)
So, yes, people can lose their jobs over technical faults - not because of the faults, but because they failed to take action to react to them.
Note that I wrote this in a slightly strange way, because all the people involved are, to the best of my knowledge, still around and might run across this at some point.
Spots were not aired during the time that I described. Whatever happened on the commercial side for make-goods or whatever, I was not privy to, and I did not address that here because I try not to opine on things of which I have no knowledge.But typically the first question asked during the senior staff discrepancy meeting will be: How much money was lost? Do we have to make good any spots? In this case, the only thing that aired were spots. The automation may have gone through the entire invetory, or it may have repeated spots over, but the spots ran, and in fact the clients likely received bonus airtime.