So, my Vero4K/EGreat is not switching to 24Hz playback if TV is switched off/on. I have to mess around with the EGreat to get back 24Hz but then I get a black screen saying resolution not supported on switching back to the Gui. A few more EGreat button clicks and GUI comes back. Only a full system reboot will get it working properly again - only to be all lost when TV is switched off/on.
NB, this is with the AVR switched off. If AVR is on, then no issue. I also have Sync to Display disabled and tried Lock HDM enabled / disabled.
I would normally suspect the EGreat as the Vero is fine plugged directly into the TV. But I replaced the Vero with my RPi3 and works flawlessly (with AVR off).
Hopefully the issue is now addressed
I’d appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:
Add the following line: deb http://apt.osmc.tv stretch-devel main
Run the following commands to update: sudo apt-get update && sudo apt-get dist-upgrade && reboot
Your system should have have received the update.
Please see if the issue is resolved.
I also recommend you edit /etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.
Vero is correctly reading the EDID from your screen when it’s on. This includes 24Hz modes.
When you restart the TV, Vero knows this and re-reads the EDID but it is a much reduced set of screen modes - no 24Hz modes - probably being generated just by the Egreat. It’s possible that the EDID sent by your AVR does include 24Hz hence why it works with the AVR on.
We will try adding a short delay between vero detecting an HDMI change and re-reading the EDID.
Thanks but why does the RPi3/OSMC work? I can post the logs for that too if it helps.
EDIT : Also, the Vero works fine on first start if I remove the AVR from the equation by disconnecting it. It’s only on the TV restart that it goes wrong.
Or could Vero ignore the TV restart and keep it’s initial settings?
PS, I’ve never been a fan of introducing sleeps etc int code to get over race conditions and the like etc - just causes more issues down the line
Ok, I am not convinced the Vero is to blame here. I did a bit more testing:
Same as above, but this time, instead of switching outputs on the EGreat to get 24Hz working again, i rebooted the Vero fully expecting that to work as it would re-read the EIDE right?
Nope, still 60HZ playback. So that points to EGreat unless I am mistaken in my understanding of how this stuff works - not an expert so making some educated guesses
That suggests the EGreat is not reacting to the TV being turned on (as it should), re-reading the TV EDID and repeating the display caps to vero. From the logs, vero is correctly reacting to the TV being turned on but it can only read the EDID served up by EGreat.
Read a post by Sam somewhere stating that have to reboot after enabling Lock HPD setting. I hadn’t done that when i tried it so enabled it again & rebooted.
It works! Playback at 24Hz after TV is switched on/off!