Broadcasters fired back Wednesday (Oct. 4) at an American Cable Association "Ransom TV" campaign blaming broadcasters for retrans blackouts and escalating retrans fees.
That came in a blog post on the TVFreedom.org Web site, a consortium of broadcasters trying to preserve the retransmission consent regime that ACA, both individually and as part of the American Television Alliance (ATVA), wants the government to revisit and reform.
Related: ATVA: Cable Act Was Disaster for Consumers
"ACA and ATVA are correct: a ransom is being demanded in the pay-tv market, but it’s not coming from broadcasters. It’s the King’s Ransom demanded by pay-TV companies every time a customer opens a monthly bill," said TVFreedom. "Start with $20 set top box fees, then add the oft-hidden fees for DVRs, second remotes, and other equipment. Include the double-digit monthly Regional Sports Network fees – for programs that many viewers never watch. Don’t forget the unannounced price increases at double the rate of inflation and harassing telemarketing calls either. And do pay-TV companies offer rebates to customers constantly subjected to blackouts caused by passing rainstorms? Not a chance."
To read the entire statement, go here.
ACA and ATVA are pressing the issue as broadcasters and MVPDs start renegotiating carriage agreements that are expiring toward the end of the year. MVPDs say broadcasters are using undue leverage provided by government to extract excessive fees, fees that hit their customers in the pocket books or lead to blackouts when deals can't be struck.
Broadcasters counter that they are only now starting to get the real value of their must-have signals in what they argue is a fair marketplace negotiation.
LEARN MORE: NYC TV Week is coming up, starting with the 27th annual Broadcasting & CableHall of Fame on Monday, Oct. 16. For more about #NYCTVWK, click here.
The smarter way to stay on top of the multichannel video marketplace. Sign up below.
Thank you for signing up to Multichannel News. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.