RadioDiscussions.com

 
RadioDiscussions.com Discussion Boards
Login May 25, 2013, 05:30:29 AM *
Username Password Session Length
 
Welcome, Guest. Please login or register. Did you miss your activation email? Did you forget your password?
:  
   Home   Help Search Contact Us Login Register  
Pages: [1] 2 3   Go Down
  Print  
Author Topic: KTCK didn't Encode Signal ???  (Read 4704 times)
zone_guy
rimember

Offline Offline

Posts: 37


KTCK didn't Encode Signal ???
« on: February 09, 2012, 09:28:37 AM »

So, listening to The Ticket this morning, I heard the Musers announce that in there move to the new Victory Park Studios, their engineers DIDN'T ENCODE their signal for PPM.  Apparently, it took them 2 weeks to realize the problem...UGH!  So, for the first two weeks of the January 2012 book, they are going to have a 0.0!  Yikes!

You can listen to the segment at The UnTicket: 

http://www.theunticket.com/pulling-back-the-curtain-musers-explain-the-2012-encoding-snafu/

How in the world is that possible?

Well, I guess the good news is that The Fan or ESPN will FINALLY beat the Ticket.  Smiley

Are they the first station in the PPM era to screw up that badly?

Surely, someone has been fired, right? 

Does anyone know the "inside" story of the Cumulus Catastrophe at Victory Park?
Logged
BenB
rimember

Offline Offline

Posts: 542


Re: KTCK didn't Encode Signal ???
« Reply #1 on: February 09, 2012, 09:30:52 AM »

WOW!!!  That's greatness!
Logged

Best Variety... 90s, 2K & Today... The New Sound of 103.7 KVIL
DavidEduardo
rimember

Offline Offline

Posts: 24816

"Things do not change; we change." - Thoreau


Re: KTCK didn't Encode Signal ???
« Reply #2 on: February 09, 2012, 11:38:13 AM »

So, listening to The Ticket this morning, I heard the Musers announce that in there move to the new Victory Park Studios, their engineers DIDN'T ENCODE their signal for PPM.  Apparently, it took them 2 weeks to realize the problem...UGH!  So, for the first two weeks of the January 2012 book, they are going to have a 0.0!  Yikes!

I checked the weeklies, which for January are 1/5 to 1/11 and 1/12 to 1/18, and the weeklies are "normal" within the range that this station wobbles. Further, the last week of Holida, ending the 4th of January, also has normal range numbers.

Sounds like they were encoded, but "making it seem" that they were not as an excuse to get listeners to "tell a friend" to listen and to openly discuss ratings.

Interesting. I'm going to check in with an Arbitron rep and see what they say.
Logged

"Change does not roll in on the wheels of inevitability, but comes through continuous struggle." Martin Luther King, Jr.

www.americanradiohistory.com - Broadcasting Magazine and Yearbooks and RCA Broadcast News, Television Magazine, Radio Annual, Radio News and many, many more.
dawireless
rimember

Offline Offline

Posts: 120


Re: KTCK didn't Encode Signal ???
« Reply #3 on: February 09, 2012, 01:21:07 PM »

Fire the engineers or better yet give them a raise,for providing an excuse for potential bad book
Logged
DavidEduardo
rimember

Offline Offline

Posts: 24816

"Things do not change; we change." - Thoreau


Re: KTCK didn't Encode Signal ???
« Reply #4 on: February 09, 2012, 03:01:09 PM »

Fire the engineers or better yet give them a raise,for providing an excuse for potential bad book

There is no evidence that they did not encode. January Week 1 and January Week 2 had normal numbers, not zeros (subscribers get weekly numbers).
« Last Edit: February 09, 2012, 03:02:53 PM by DavidEduardo » Logged

"Change does not roll in on the wheels of inevitability, but comes through continuous struggle." Martin Luther King, Jr.

www.americanradiohistory.com - Broadcasting Magazine and Yearbooks and RCA Broadcast News, Television Magazine, Radio Annual, Radio News and many, many more.
w9wi
rimember

Offline Offline

Posts: 4294


Re: KTCK didn't Encode Signal ???
« Reply #5 on: February 09, 2012, 04:21:18 PM »

Again showing my ignorance as a TV type Wink  what does Arbitron do if they realize a station isn't encoding properly? 

I mean, if there's the slightest glitch with our encoding for TV, we hear from Nielsen almost immediately.  (one day, one of our guys bumped the encoder offline & they were on the phone with me within ten minutes)   Do they not do that in radio?
Logged
DavidEduardo
rimember

Offline Offline

Posts: 24816

"Things do not change; we change." - Thoreau


Re: KTCK didn't Encode Signal ???
« Reply #6 on: February 09, 2012, 07:35:26 PM »

Fire the engineers or better yet give them a raise,for providing an excuse for potential bad book

There is no evidence that they did not encode. January Week 1 and January Week 2 had normal numbers, not zeros (subscribers get weekly numbers).

The latest news is that the encoding... or lack of same... was affected in a five day period at the end of Week 3 and the beginning of Week 4. The dates mentioned by the station talent's post are off, but there really appears to have been a period where no encoding took place. As far as Arbitron is concerned, it's the same as being off the air.
Logged

"Change does not roll in on the wheels of inevitability, but comes through continuous struggle." Martin Luther King, Jr.

www.americanradiohistory.com - Broadcasting Magazine and Yearbooks and RCA Broadcast News, Television Magazine, Radio Annual, Radio News and many, many more.
Scott Fybush
rimember

Offline Offline

Posts: 4295


Re: KTCK didn't Encode Signal ???
« Reply #7 on: February 09, 2012, 08:02:58 PM »

Again showing my ignorance as a TV type Wink  what does Arbitron do if they realize a station isn't encoding properly? 

I mean, if there's the slightest glitch with our encoding for TV, we hear from Nielsen almost immediately.  (one day, one of our guys bumped the encoder offline & they were on the phone with me within ten minutes)   Do they not do that in radio?

I don't think Arbitron does any sort of constant monitoring for PPM data in each market. But they provide both encoder boxes and decoder boxes to stations, and the decoders can (and should) be wired up to send an immediate alarm if PPM encoding isn't being detected. It's really hard to imagine that going unnoticed at a station owned by a major group in a top-10 market.
Logged

All kinds of good stuff over at http://www.fybush.com
DavidEduardo
rimember

Offline Offline

Posts: 24816

"Things do not change; we change." - Thoreau


Re: KTCK didn't Encode Signal ???
« Reply #8 on: February 09, 2012, 08:08:41 PM »

Again showing my ignorance as a TV type Wink  what does Arbitron do if they realize a station isn't encoding properly? 

I mean, if there's the slightest glitch with our encoding for TV, we hear from Nielsen almost immediately.  (one day, one of our guys bumped the encoder offline & they were on the phone with me within ten minutes)   Do they not do that in radio?

The Nielsen system is wired, thus the ability to do overnight ratings. Any deviation from the norm can be seen... and here I am guessing... by means of an algorithm that sets off a warning for any unusual occurrence or from monitoring of the outlets themselves. The Nielsen "set top boxes" actually know what they are tuned to, and can send this data back very quickly. The PPMs are portable and only send data home each night if they are docked in a charger (although wireless ones are in development). Just in case, I am checking with Arbitron to see if they have any specific systems in place.

I do know of one nameless station that somehow took the encoder out of the audio chain, and the station did not know about it until the first weeklies came back with horrific numbers... they called Arbitron... and the first question was, "is your encoder working?"
Logged

"Change does not roll in on the wheels of inevitability, but comes through continuous struggle." Martin Luther King, Jr.

www.americanradiohistory.com - Broadcasting Magazine and Yearbooks and RCA Broadcast News, Television Magazine, Radio Annual, Radio News and many, many more.
DavidEduardo
rimember

Offline Offline

Posts: 24816

"Things do not change; we change." - Thoreau


Re: KTCK didn't Encode Signal ???
« Reply #9 on: February 09, 2012, 08:11:15 PM »

Again showing my ignorance as a TV type Wink  what does Arbitron do if they realize a station isn't encoding properly? 

I mean, if there's the slightest glitch with our encoding for TV, we hear from Nielsen almost immediately.  (one day, one of our guys bumped the encoder offline & they were on the phone with me within ten minutes)   Do they not do that in radio?

I don't think Arbitron does any sort of constant monitoring for PPM data in each market. But they provide both encoder boxes and decoder boxes to stations, and the decoders can (and should) be wired up to send an immediate alarm if PPM encoding isn't being detected. It's really hard to imagine that going unnoticed at a station owned by a major group in a top-10 market.

I've heard of a handful of cases when PPM was new where the alarm was either hooked to a lamp in engineering and not noticed for days. In several others, the alarm sent a text to the engineer, who said "I'll fix it Monday after the weekend." In all these cases, it took some training for everyone to realize that not encoding was about the same as being off the air. 
Logged

"Change does not roll in on the wheels of inevitability, but comes through continuous struggle." Martin Luther King, Jr.

www.americanradiohistory.com - Broadcasting Magazine and Yearbooks and RCA Broadcast News, Television Magazine, Radio Annual, Radio News and many, many more.
Pages: [1] 2 3   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP

Postings on Radiodiscussions.com are the opinions of the people who post them. Views expressed do not necessarily represent the views of Radiodiscussions.com or its owner or operator. In fact many of the views expressed here are just plain wrong. But they are opinions and this site allows us all to discuss those opinions. Any reliance on information posted is done so at the user's own risk. For a detailed look at the rules, regulations and uses of Radiodiscussions.com please see our TERMS OF SERVICE.

Valid XHTML 1.0! Valid CSS!
Page created in 0.281 seconds with 20 queries.