Repeating/cycling Blank Screen

For sometime now (and I mean for several months and probably only since I started testing the DV builds, not 100% sure on this)
I have had this problem with my Vero-V (or is it the AVR?) after leaving it in standby/suspend overnight.

So in the morning/afternoon the next day powering it on and selecting the Vero-V as the source for the TV greets me with a repeating blank screen, as if it is performing a display resolution change. I can clear the problem by doing a full power cycle of the AVR.

The video below shows this repeating blank screen behaviour.

(video removed)

Currently my connection setup is as follows: Vero-V > Yamaha RX-A2A AVR > LG OLED48CX6LB

If I connect the Vero-V directly to the TV, the problem goes away, which kind of points the finger at the AVR, or possibly how the Vero-V interacts with the AVR.

The problem is also not specific to Dolby Vision videos either. This happens in the menu screens and with other non DV videos.

I have collected the logs made during the video above:

https://paste.osmc.tv/najecibotu

I really don’t want to be power cycling the AVR all the time.

Are my settings wrong in someway for the CEC interface, especially as this is showing a constant cycling repeat interval. Could it be an interation with the screensaver ?

I also note I am seeing the same logging events as per this thread
https://discourse.osmc.tv/t/screen-blanks-out-every-few-seconds)

20:27:35.556 T:4081934928 NOTICE: Display resolution ADJUST : 1920x1080 @ 50.00 - Full Screen (24) (weight: 0.000)
20:27:35.556 T:4081934928 NOTICE: VideoPlayer: OnLostDisplay received
20:27:35.841 T:4081934928 NOTICE: VideoPlayer: OnResetDisplay received

HDMI cable might be loose, or need replacing.

So, I’ll try a few obvious things like changing the HDMI cable between the Vero-V and the AVR.

Chris.

If it’s the same thing, I doubt if recent upgrades to Vero V have much to do with it. That was 7 years ago.

Changing the HDMI cable has made no difference.

I was able to repeat the problem, sending the Vero-V into SUSPEND when TV turned off (CEC setting) and then a short time later, waking it up by powering on the TV.

The repeating blank screen struck again.

Next, I’ll try another PSU.

Logs here -

https://paste.osmc.tv/wasacifoni

Video here -

Why would you think it may be the PSU?
CEC is a mess; always has been and likely always will be.
There’s really only so much OSMC can do about it since there are way too many variables.
Unfortunately I have to leave CEC turned on with my LG TV otherwise ARC doesn’t work.
Why do they tie those two together?
They don’t have to
It’s just another example of how messed up CEC is.
I hope you find a fix for your issue but using CEC and having the Vero suspend sounds like a bad recipe to me.

This resembles the issue I’m having (at least superficially). I intend to debug things a bit more but need a free evening. Hopefully next week.

I have had unstable (switched mode) PSUs cause problems in the past. There was a slight possibility of this, and worth a try.

I did a little more experimentation and found the following CED & Power Saving settings to at least be stable in the short term. See below.

I changed the settings to disable any SUSPEND behaviour orinating from the TV/AVR, other than PAUSING PLAYBACK, and also to totally minimise any other from of CEC control from the TV/AVR. This was followed by a complete power down of all devices in this CEC chain (TV, AVR & Vero) and a wait of 5 mins or so, to make sure any ā€˜stored’ CEC settings were lost in the TV/AVR. So far this seems to be OK and I just now need to check they are still OK the next day (after an overnight run so to speak).

You’re right though @Kontrarian, having the Vero SUSPEND as invoked by the TV/AVR was a recipe for disaster, and this was the cause of the cycling blank screen, when it came out of the suspended state.

I still have the Vero SUSPENDing, but only by way of its very own ā€œidle shutdownā€ timer (5 mins) and not from a CEC command (in the Power saving menu). See below.

That’ll be an AVR bug I suspect.
Does enabling HPD Lock and rebooting help?

I tried enabling the HPD lock + reboot, which made no difference.

I’ve written to Yamaha Customer support. They have helped in the past.

and so this is what Yamaha suggest -

With regards to your question, our first suggestion would be to test your source device into the HDMI inputs 4, 5, 6 or 7, when you do you, do you have the same issue happen, as the first three HDMI sockets are designed for source devices that can support 4K@120Hz (e.g. PS5, Xbox series X/S and gaming PC’s).

When moving the HDMI leads, it is good practise to switch all devices OFF at their mains sockets, then disconnect and move your HDMI lead, then once they are all connected, if you can power ON all devices.

If you can try the above and please let us know how you get on.

Hope this helps and if you have any further questions or queries, please do not hesitate to ask.

Many thanks

Yamaha Technical A/V

So I am now trying a non 120Hz HDMI input for the Vero-V (even though I may have resolved this by changing the CEC settings).

Update -

After powering down the AVR completely, as suggested by Yamaha I reassigned all my sources to use HDMI inputs 4, 5, 6 & 7 of the AVR and turned back on the suspend CEC functionality. This seemed to be ok - no blank screens.

BUT,

Playing back some of the DV videos (ā€˜amaze’ clip) on the Vero-V just showed up the old problem of intermittent audio. So, I reassigned the Vero-V back to one of the HDCP 2.1 4K@120Hz inputs, and checked the SUSPEND CEC functionalilty, and audio, which was OK, even after an overnight suspend.

Just shows how fickle CEC can be. I’ll let Yamaha know.

I’ll update this thread if there are anymore developments.

P.S.
When moving the HDMI leads, it is good practice to switch all devices OFF at their mains sockets, then disconnect and move your HDMI lead, then once they are all connected, you can power ON all devices.

1 Like

Yes, this is to prevent the ā€˜ghost’ syndrome.
CEC is very frustrating.

It’s a shame it can’t really be standardised…

Thats the beauty of (CEC) standards, there’s so many of them.