Jump to content

Welcome to DBSTalk

Sign In 

Create Account
Welcome to DBSTalk. Our community covers all aspects of video delivery solutions including: Direct Broadcast Satellite (DBS), Cable Television, and Internet Protocol Television (IPTV). We also have forums to discuss popular television programs, home theater equipment, and internet streaming service providers. Members of our community include experts who can help you solve technical problems, industry professionals, company representatives, and novices who are here to learn.

Like most online communities you must register to view or post in our community. Sign-up is a free and simple process that requires minimal information. Be a part of our community by signing in or creating an account. The Digital Bit Stream starts here!
  • Reply to existing topics or start a discussion of your own
  • Subscribe to topics and forums and get email updates
  • Send private personal messages (PM) to other forum members
  • Customize your profile page and make new friends
Guest Message by DevFuse

- - - - -

922 HDCP enforcement on HBO & Cinemax & possible solution

  • Please log in to reply
40 replies to this topic

#41 OFFLINE   JimD



  • Topic Starter
  • Registered
  • 151 posts
Joined: Apr 08, 2005

Posted 22 December 2011 - 11:07 AM

I have the same problem with my ViP 722. According to a tech support person I spoke with at Dish, this is NOT a DVR or TV problem. It is a HBO/Cinemax problem, or rather, something that HBO and Cinemax are doing at their end, randomly and arbitrarily screwing things up with every distributor of their content.

Their position makes no sense to me. :nono2: I am no expert on HDCP, but I seriously doubt that the method used by the 922 (or 722) to establish and maintain an HDCP encrypted connection over the HDMI interface is in any way controlled by content providers.

I have no doubt that the content providers can require (or not) an HDCP connection, this is apparent given that only HBO/Cinemax has this issue - but if the receiver is intermittently and erroneously detecting that a fully compliant display device is NOT compliant, this is clearly Dish's fault.

The fact that it works initially (or after you unplug and replug the HDMI cable) shows that the receiver can reliably establish this encrypted link in the first place - but something is later causing it to lose the link, and it never succeeds at re-establishing it. It seems to me that this is where the Dish (Echostar?) engineers should be focusing their effort.

...Ads Help To Support This Site...

Protected By... spam firewall...And...