Population Statistic: Read. React. Repeat.
Sunday, September 18, 2021

turn up the audio
It’s been awhile since I’ve heard Sterling Sharpe on the air. He’s doing color commentary for tonight’s Raiders-Chiefs game, paired with Mike Tirico, while the regular ESPN Sunday Night Football crew do tomorrow’s Katrina-rescheduled Saints-Giants game.

Sharpe sounds downright weird tonight. His voice has a pinched, nasally quality to it. I don’t remember him sounding like this during his old ESPN NFL Primetime studio gig.

In fact, I’ll go as far as to characterize Sharpe’s announcing voice tonight as nerdy. It reminds me of a cross between Steve Urkel and the Art Instruction Schools president (who’s top-of-mind, because his commercials are running during tonight’s game).

- Costa Tsiokos, Sun 09/18/2005 10:53:55 PM
Category: TV, Football | Permalink |

Trackback this entry: Right-click and copy link

3 Feedbacks »
  1. Tony Gwynn has almost made immune to notice this sort of thing, but he did sound a bit different. Might have just been under the weather though.

    Comment by David — 09/19/2005 @ 03:23:09 AM

  2. I had read in Friday’s USA Today that ESPN was using Sterling Sharpe’s work sunday as an “audition” for possible future use. I noticed his nervousness more than his voice, although he loosened up a little later in the game. He must have known what was at stake and reacted. I like Sterling but Michael Irvin would have been the inspired choice.

    Comment by Chuck — 09/19/2005 @ 11:01:31 AM

  3. Must have been a highly unofficial “audition”, as Sharpe is working for NFL Network (technically a rival). Maybe they want him to go back to ESPN.

    I thought he might have been sick too, but he seemed to fall in and out of the nasal twang during breaks in the game action. I think he was nervous, and was attempting some sort of “professional” delivery.

    Comment by CT — 09/20/2005 @ 09:29:28 AM

RSS feed for feedback on this post.

Leave a comment

PLEASE NOTE: Various types of comment moderation may be triggered once you hit the "Say It!" button below. Common causes for this are the inclusion of several hyperlinks and/or spam words in the comment field. Please do not hit the "Say It!" button more than once. If you feel your comment is being blocked without cause, feel free to email me about it.