Been running a new Vero into my Marantz AVR/Panny OLED combo, with Kodi GUI set to 1080p. Mostly everything is fine, but sometimes when I turn on the TV, it reports a 720p signal from the Vero, and when I go into the Kodi GUI settings, my 1080p setting has mysteriously changed itself to 720p.
Here is a log from today, I left the log running for quite a few hours and turned on the TV a couple of times. Sometimes the Vero resumes at 1080, final instance in this sequence the Vero has changed its GUI settings to 720p without any user intervention. Any advice?
at 16:36 Vero is receiving a curious EDID typical of a PC monitor, not a TV:
2021-08-27 16:36:53.713 T:2684 INFO <general>: Found resolution 720 x 480 with 720 x 480 @ 60.000000 Hz
2021-08-27 16:36:53.713 T:2684 INFO <general>: Fallback resolution at 16 + 0 00480060.00000pstd
2021-08-27 16:36:53.713 T:2684 INFO <general>: Found resolution 720 x 480 with 720 x 480 @ 59.940060 Hz
2021-08-27 16:36:53.713 T:2684 INFO <general>: Found resolution 1280 x 720 with 1280 x 720 @ 60.000000 Hz
2021-08-27 16:36:53.713 T:2684 INFO <general>: Fallback resolution at 16 + 2 00720060.00000pstd
2021-08-27 16:36:53.713 T:2684 INFO <general>: Found resolution 1280 x 720 with 1280 x 720 @ 59.940060 Hz
2021-08-27 16:36:53.713 T:2684 INFO <general>: Found resolution 640 x 480 with 640 x 480 @ 60.000000 Hz
2021-08-27 16:36:53.713 T:2684 INFO <general>: Found resolution 640 x 480 with 640 x 480 @ 59.940060 Hz
2021-08-27 16:36:53.713 T:2684 INFO <general>: Found resolution 800 x 600 with 800 x 600 @ 60.000000 Hz
2021-08-27 16:36:53.713 T:2684 INFO <general>: Found resolution 800 x 600 with 800 x 600 @ 59.940060 Hz
2021-08-27 16:36:53.713 T:2684 INFO <general>: Found resolution 1024 x 768 with 1024 x 768 @ 60.000000 Hz
2021-08-27 16:36:53.713 T:2684 INFO <general>: Fallback resolution at 16 + 8 00768060.00000pstd
2021-08-27 16:36:53.713 T:2684 INFO <general>: Found resolution 1024 x 768 with 1024 x 768 @ 59.940060 Hz
Any idea where these VESA modes might be coming from? These VESA modes are spurious - a result of getting a corrupt EDID read. Your Panasonic doesn’t support any VESA modes other than 640x480. So same issue as (1).
Although it’s not supposed to, Vero is forgetting your setting after that funny EDID read. 30s later it has got the correct EDID again and I can’t see that you went into the settings screen before that. (if you did, that would be enough to save the setting as 1024x768). I’ll look into that - I didn’t think anything had changed between Leia and Matrix.
thanks, all my cables are certified high speed, I will try another input.
I have a problem with disabling logging. I can disable via the GUI, but when I reboot (even a cold boot), the logging is active again. Can’t figure out how to turn it off and make that persistent after a reboot.
the cable packaging has an “Ultra Certified Cable / Ultra High Speed” logo and a QR code which I guess can authenticate certification. I have these end to end.
I tried another input on the AVR and still had issues. I also re-connected the TV HDMI cable just in case.
Just been through another cycle where the GUI resolution drops to 720p, same issues as before?
Yes. I would give your plugs and sockets a dose of contact cleaner and try other HDMI ports. Also suspect any mains cables which run parallel to your HDMI cables.
I double-checked connections, and enabled HPD lock, and this may have sorted it (I had a 1080 GUI when I switched on the TV this morning). Will keep an eye on it, here’s a log from just now with HPD lock on.
OK you still seem to be getting a load of HDMI switch events but they are indeed being ignored. It would be interesting to know if the problem exists with a direct connection Vero->TV, but if you are always going to be using the Vero with the same equipment and you obtain a good EDID on boot you should be good, now. To get a good EDID on boot you will need to ensure the AVR and TV are switched on when you fire up Vero.