Solving playback issues

[iFrog]

---

@jplp wrote:

I concur with @mikew_nt. Saying that Roku devices are intended to be connected directly to the TV is false and a cop-out. Using an AVR is an extremely common setup and nearly all just pass the signal through with no alterations. It's not about the setup or configuration. It's about what protocols and standards these devices claim they support and don't. HDCP is HDCP regardless of who is implementing that into their device. The common denominator throughout countless posts and extensive troubleshooting is that Roku has these issues in abundance and other competitor hardware does not using the exact same protocols, cables and AV equipment. When I've invested hundreds of dollars in Roku devices and the time and effort to setup, troubleshoot, and test, I expect more from an company than just resending the boilerplate HDCP troubleshooting page or saying to just plug it directly into your TV. If Roku isn't meeting the industry standard set by the HDMI Forum and advertises on its product, then Roku has a problem that only they can resolve instead of giving customers, loyal ones at that, the runaround and passing blame wasting our time and money.

---

I agree with what you're saying.  I'm not the one taking the easy way out here though.  What I have stated in my last few posts is more Roku's attitude toward the consumer.  I agree AVRs and sound bars are more common in setups today.  However, the Roku isn't a power user device, if it was, it would have features  targeted toward all classes and experience  of users.  For example most people who have AVRs want Lossless audio, Roku and many streamers don't support that only the Shield does.  Apple TV does to a degree as it can pass multi channel PCM, but not lossless ATMOS, or DTS:X, etc.  So because Roku doesn't choose to support those things, even with an optional fee to unlock those codecs, for those who want it, and the fact that as people have mentioned here that it should just work in any configuration, and yet people with more complex setups tend to have more problems, and then even reading people's posts about having to connect the device directly to the TV to resolve issues, suggests that's Roku's attitude towards it's users.  My suggestion to most people who use a Roku that complain is buy an Apple TV 4K. Because aside for the HDCP issues, most of the complaints I see on a regular basis are regarding frame rate matching and other related things the Apple TV is known to be good at.  Then again having been an apple user my whole life, I would always recommend them first if they made a product that could meet people's needs I was helping.  I only bought the Roku 3 back in 2013, because the Apple TV wasn't the mature device it is today.  If it had been, I may not have even bothered with Roku.  As it is after investing in it, I got used to the interface, and as long as it's stable I like using them.  The problem is that I've observed is, Roku  works well when it's stable, but they can't seem to keep it that way for very long at one point.  Even if it's not me having issues specifically, someone is. 

[jplp]

AVRs and sound bars have been "more common" starting 15 years ago or longer. Anyone who wants more than the 5W TV speakers has to look for upgrades and anyone with a simple AVR or sound bar setup isn't a power user. I don't care about lossless audio codecs. I have a cheaper Polk 5.1 system because it's magnitudes better than just the TV alone.

Regardless someone's technical setup, standards are standards and Roku clearly isn't meeting the HDMI standard. Roku advertises "The ultimate streaming player. See your TV at its best with Roku Ultra—our fastest streaming player ever, with unmatched cinematic picture and sound." So they themselves feel their unit is ultimate player and targeted towards the "higher-end" crowd.

"Then again having been an apple user my whole life." Well, there you go. That explains your feelings and dismissal towards an "inferior" product. OEMs are known to lie about the port standards they claim their hardware offers such as Apple never supporting the DisplayPort core standard of Multi-stream transport because they want to force you to buy thunderbolt capable equipment from them.

I didn't buy Apple for my own separate reasons. I bought Roku and Roku needs to own this issue and make it right.

[lmacmil2]

As I noted previously in this thread, the only way I could get rid of HDCP errors on my 4802 was to plug it directly into my LG C3.  My previous setup, 4660 into Denon AVR into Samsung KS8000 never gave an HDCP error.  I got the 4802 when I got the C3 so I'd have Dolby Vision capability (the Samsung TV was HDR only.)  I also got new HDMI cables but going into the Denon (which is HDCP 2.3 compliant) resulted in random and inconsistent HDCP errors with the 4802 and LG.  Sometimes I'd get 2 or 3 in an hour and sometimes I wouldn't get any for a couple days.  They occurred mostly on HDR programs but I did also get them occasionally on SDR programs.  I get Dolby sound through the AVR via the eARC channel so this is a workable, if not really elegant, solution.  Some day I'll put the 4660 back in and connect via the AVR to see if that works better (knowing that I'd be giving up DV.)  If I ever buy another streaming device, it will not be a Roku.  Kinda sorry I bought the 4802 but as a $50 refurb direct from Roku it was hard to pass up.

[rbraunston]

HDCP error 2.2

I have resolved the HDCP 2.2 error for most users. I have reported the fix to Roku support. Roku said they are going to post the information so let’s see if they do. I have been testing this for the last two weeks with no 2.2 error.

Background: I am a video and audio engineer and I’ve been getting this error for years and I’ve called Roku many times to get this issue resolved. I have replaced a new Samsung 77” OLED TV, all of my HDMI cables with 8K fiber optic, and bought a new Roku Ultra directly from Roku. They promised it would resolve the issue. It didn’t.

If your Roku is directly connected to a TV’s eARC HDMI port, you probably don’t have the 2.2 error because the port has constant power even though your TV has been turned off. The Roku is able to acknowledge that the TV is 2.2 or 2.3 compliant.

I have my Roku directly connected to a Denon receiver, not the TV. The Denon is connected to the TV’s HDMI eARC port. When the TV and audio components are turned off, the Roku loses direct connection to the TV. When the components are turned back on, the Roku doesn’t see the TV as it’s directly connected to the Denon and this produces the error. The Roku has to be restarted for it to reconnect to the TV. This is done by disconnecting the Roku power or selecting restart in Roku’s setting.

Denon and Marantz receivers have a setting that will allow the Roku to constantly see the TV and stop the error. For both receivers, go to the Se-up Menu, Video, HDMI Setup, scroll to “Pass Through Source”, and select your Roku as pass-through. By doing this the Roku constantly sees the TV and stops the error.

If you are connecting your Roku to a soundbar, game controller, or any other device that gets turned off, you are probably going to get the error. It loses connection with the TV. See if the connected devise has a pass-through setting. If you are using another AVR brand receiver, determine if it has a pass-through setting or something similar.

[rbraunston]

I have resolved the HDCP 2.2 error for most users. I have reported the fix to Roku support. Roku said they are going to post the information so let’s see if they do. I have been testing this for the last two weeks with no 2.2 error.

Background: I am a video and audio engineer and I’ve been getting this error for years and I’ve called Roku many times to get this issue resolved. I have replaced a new Samsung 77” OLED TV, all of my HDMI cables with 8K fiber optic, and bought a new Roku Ultra directly from Roku. They promised it would resolve the issue. It didn’t.

If your Roku is directly connected to a TV’s eARC HDMI port, you probably don’t have the 2.2 error because the port has constant power even though your TV has been turned off. The Roku is able to acknowledge that the TV is 2.2 or 2.3 compliant.

I have my Roku directly connected to a Denon receiver, not the TV. The Denon is connected to the TV’s HDMI eARC port. When the TV and audio components are turned off, the Roku loses direct connection to the TV. When the components are turned back on, the Roku doesn’t see the TV as it’s directly connected to the Denon and this produces the error. The Roku has to be restarted for it to reconnect to the TV. This is done by disconnecting the Roku power or selecting restart in Roku’s setting.

Denon and Marantz receivers have a setting that will allow the Roku to constantly see the TV and stop the error. For both receivers, go to the Se-up Menu, Video, HDMI Setup, scroll to “Pass Through Source”, and select your Roku as pass-through. By doing this the Roku constantly sees the TV and stops the error.

If you are connecting your Roku to a soundbar, game controller, or any other device that gets turned off, you are probably going to get the error. It loses connection with the TV. See if the connected devise has a pass-through setting. If you are using another AVR brand receiver, determine if it has a pass-through setting or something similar.

[rbraunston]

I'm the person that started this thread - the information I got from Roku was not correct. Please read

I have resolved the HDCP 2.2 error for most users. I have reported the fix to Roku support. Roku said they are going to post the information so let’s see if they do. I have been testing this for the last two weeks with no 2.2 error.

Background: I am a video and audio engineer and I’ve been getting this error for years and I’ve called Roku many times to get this issue resolved. I have replaced a new Samsung 77” OLED TV, all of my HDMI cables with 8K fiber optic, and bought a new Roku Ultra directly from Roku. They promised it would resolve the issue. It didn’t.

If your Roku is directly connected to a TV’s eARC HDMI port, you probably don’t have the 2.2 error because the port has constant power even though your TV has been turned off. The Roku is able to acknowledge that the TV is 2.2 or 2.3 compliant.

I have my Roku directly connected to a Denon receiver, not the TV. The Denon is connected to the TV’s HDMI eARC port. When the TV and audio components are turned off, the Roku loses direct connection to the TV. When the components are turned back on, the Roku doesn’t see the TV as it’s directly connected to the Denon and this produces the error. The Roku has to be restarted for it to reconnect to the TV. This is done by disconnecting the Roku power or selecting restart in Roku’s setting.

Denon and Marantz receivers have a setting that will allow the Roku to constantly see the TV and stop the error. For both receivers, go to the Se-up Menu, Video, HDMI Setup, scroll to “Pass Through Source”, and select your Roku as pass-through. By doing this the Roku constantly sees the TV and stops the error.

If you are connecting your Roku to a soundbar, game controller, or any other device that gets turned off, you are probably going to get the error. It loses connection with the TV. See if the connected devise has a pass-through setting. If you are using another AVR brand receiver, determine if it has a pass-through setting or something similar.

[DoughertyPM]

But Of course, thery release an update that fouls up existing roku units alledgedly because theyre worried about people copying shows to a dvd.  But lo and behold, they have a new product that will fix the problem their update caused for only 99.99. Im tired of being continually railroaded into buying new electronics due to planned obsolescence! We have multiple boxes of manufacturer generated electronic waste! Im done!

[DoughertyPM]

My Roku was plugged directly into the tv

[JanJ]

retired tv network engineer. 
been working around this HDCP 2.2 Issue, and the HDCP 1.4 Issue that preceded it on MULTIPLE DEVICES!!

Just put an HDCP 2.2 Compatible HDMI SPLITTER after the Roku, And in front of the Dolby Sound System or ‘Next’ Device!

DONE!  Problem GONE! Forever!!