Pioneer VSX-LX302 Gives Sound but No Video

[bajo79]

I am definitely new to home theater equipment and setup, so I am hoping the forum can help.

I have a Pioneer VSX-LX302 connected to an Epson Projector. It has been working well for two years now. I went to use it, and the Cable/Sat input was producing sound from my Xfinity cable box but not video. Instead I get an "HDMI 1: Not Supported" message on the screen. I have had this problem before with components in this setup and it has pointed to a problem with a board in the receiver. However, I proceeded to troubleshoot a bit and found the following:

1) Connecting my Blue Ray player to the Cable/Sat input produces both sound and image and appears to work fine. Conversely connecting the cable box to the Blue Ray input produces the same issue as the Cable/Sat. It also appears that a Chromecast I have connected to another input seems to work as expected.
2) If I pull the power on the cable box and reboot it, I can see the initial boot/"Welcome" screens from the cable box, but as it prepares to show me the video, it goes out and I only get sound.
3) Changing the HDMI cable between the cable box and the receiver has no affect.
4) Connecting the cable box directly to a different TV works just fine, producing both video and audio.
5) I have tried switching the cable box with one from another room. Initially this seemed to be successful. However, when I came back to it a couple days later it was out again and producing the same error.
6) The on screen menus for the receiver do not appear on the screen when the video is not displayed.

I am at a loss as certain troubleshooting steps seem to point to a faulty receiver, while others indicate there might be a problem with the cable box. I appreciate any help this forum can offer. Thanks.

 

[TLS Guy]

I am definitely new to home theater equipment and setup, so I am hoping the forum can help.

I have a Pioneer VSX-LX302 connected to an Epson Projector. It has been working well for two years now. I went to use it, and the Cable/Sat input was producing sound from my Xfinity cable box but not video. Instead I get an "HDMI 1: Not Supported" message on the screen. I have had this problem before with components in this setup and it has pointed to a problem with a board in the receiver. However, I proceeded to troubleshoot a bit and found the following:

1) Connecting my Blue Ray player to the Cable/Sat input produces both sound and image and appears to work fine. Conversely connecting the cable box to the Blue Ray input produces the same issue as the Cable/Sat. It also appears that a Chromecast I have connected to another input seems to work as expected.
2) If I pull the power on the cable box and reboot it, I can see the initial boot/"Welcome" screens from the cable box, but as it prepares to show me the video, it goes out and I only get sound.
3) Changing the HDMI cable between the cable box and the receiver has no affect.
4) Connecting the cable box directly to a different TV works just fine, producing both video and audio.
5) I have tried switching the cable box with one from another room. Initially this seemed to be successful. However, when I came back to it a couple days later it was out again and producing the same error.
6) The on screen menus for the receiver do not appear on the screen when the video is not displayed.

I am at a loss as certain troubleshooting steps seem to point to a faulty receiver, while others indicate there might be a problem with the cable box. I appreciate any help this forum can offer. Thanks.

From what you said, it is pretty clear to me that the fault is with your cable company and you probably need to change cable companies. Who is your cable company?

This is what I think has happened.

First you need to understand that if you connect an HDMI unit to a TV directly, then it only needs one initial handshake. However if you connect a device to a receiver and connect the receiver to a TV, the sending device and the receiver have to make continuing and repeated handshakes. This called repeater architecture. This is required of devices that receive and send HDMI. It is also required of a device connected to a device that sends HDMI to a repeater device like a receiver. A TV is an end device and does not require repeater architecture.

What I think has happened is that your cable company has sent an "update" down the line which has omitted repeater architecture. When you replaced the cable box it worked until it received the update. This is far from unknown among cable companies who by and large are a really motley crew. So you need to make the cable company make this right or break the contract and get someone else.

 

[bajo79]

From what you said, it is pretty clear to me that the fault is with your cable company and you probably need to change cable companies. Who is your cable company?

This is what I think has happened.

First you need to understand that if you connect an HDMI unit to a TV directly, then it only needs one initial handshake. However if you connect a device to a receiver and connect the receiver to a TV, the sending device and the receiver have to make continuing and repeated handshakes. This called repeater architecture. This is required of devices that receive and send HDMI. It is also required of a device connected to a device that sends HDMI to a repeater device like a receiver. A TV is an end device and does not require repeater architecture.

What I think has happened is that your cable company has sent an "update" down the line which has omitted repeater architecture. When you replaced the cable box it worked until it received the update. This is far from unknown among cable companies who by and large are a really motley crew. So you need to make the cable company make this right or break the contract and get someone else.

Thank you for your quick response. I greatly appreciate it.

I have Comcast Xfinity cable service.

I have thought about returning my cable box and exchanging it for a new one. Is it likely that this could provide a long term fix? Or is it more probable that even if this offers immediate relief, it will quickly fail again? I suppose that depends on if they exchange it like-for-like, or if they provide some other hardware.

Thanks again.

 

[lovinthehd]

When a glitch like that with an avr occurs I like to run soft reset first, then a full microprocessor/factory reset just in case that can clear it up....

 

[TLS Guy]

Thank you for your quick response. I greatly appreciate it.

I have Comcast Xfinity cable service.

I have thought about returning my cable box and exchanging it for a new one. Is it likely that this could provide a long term fix? Or is it more probable that even if this offers immediate relief, it will quickly fail again? I suppose that depends on if they exchange it like-for-like, or if they provide some other hardware.

Thanks again.

That is interesting. I have xfinity Comcast running on three systems.

I'm sure this is an HDMI incompatibility issue. I see there are quite a few firmware updates for that receiver. So the first thing to do is to make sure you have the latest software installed on your system. If that does not solve the problem then I would get hold of Comcast and see if you need new cable boxes.

I suspect that Comcast have done an update, and your receiver has out of date HDCP codes.

HDMI is still a problem, part of the issue is manufacturers failing to get their products certified.

If all those things do not solve the issue, then although that receiver is not very old, it will need to be replaced.

Along the way in my searches, I note that unit has a bad reputation. I suspect your receiver is the one out of compliance and not the Comcast set top boxes unless they are very old. Pioneer is currently a mess, so it is likely that unit may not be properly supported.

Your task is to find which of the units, receiver or set top boxes have the rogue HDCP codes. One thing I am certain of is that this is an HDCP incompatibility issue.

 

[bajo79]

For what it's worth, I exchanged my cable box at Xfinity and the new box has been working. That being said, I also had it working for a short period of time with a set top box from another room, and it eventually failed as well. So right now, I am crossing my fingers that trading out the STB resolves the issue.