Not switching to 4K output

Just noticed something…

If Vero4K has been unplugged from power and is plugged in again with my TV turned off, then the TV doesn’t switch to 2160P when playing 4K. I have to reboot Vero4K to get it working.

Not that big of a deal, but it just nags me, that I can’t be 100% sure the TV will switch to the correct output (maybe if the power has been out without my knowledge).

The TV needs to be on in order to make it’s compatible display modes available to the Vero4k when it boots and queries the TV for supported modes. Not much to be done for such a hardware limitation.

As @actiona says, we query the TVs EDID when powering on so that we can determine the TVs capabilities

If your TV is off we fallback to 1080p as a failsafe

Sam

Makes sense. But wouldn’t it be possible to query afterwards, maybe on play and of cause only if needed?

That’s already done, but won’t always work (timing issues)
You can mount --bind disp_cap; but the Vero 4K is doing what it should be
doing.

This isn’t persistent (just for a test):

cat /sys/class/amhdmitx/amhdmitx0/disp_cap > /tmp/disp_cap
cat /sys/class/amhdmitx/amhdmitx0/aud_cap > /tmp/aud_cap
cat /sys/class/amhdmitx/amhdmitx0/edid > /tmp/edid
sudo mount --bind /tmp/disp_cap /sys/class/amhdmitx/amhdmitx0/disp_cap
sudo mount --bind /tmp/aud_cap /sys/class/amhdmitx/amhdmitx0/aud_cap
sudo mount --bind /tmp/edid /sys/class/amhdmitx/amhdmitx0/edid

Tried it with the TV on. Didn’t do anything.

This means your TV deasserts on standby. Unfortunately it’s a quirk of the TV.

What’s the output of /sys/class/amhdmitx/amhdmitx0/disp_mode when working as expected, and /sys/class/amhdmitx/amhdmitx0/disp_cap when TV has been off for some time

Ideally this is something I don’t want to try and ‘fix’. If we ignore changes to HDMI events, then this will cause problems for receivers that send an EDID when other devices are unavailable or in standby and lead to other issues.

How do I see the output of /sys/class/amhdmitx/amhdmitx0/disp_mode ?

Use the cat command

VIC:16

480p60hz
576p50hz
720p60hz
1080i60hz
1080p60hz
720p50hz
1080i50hz
1080p30hz
1080p50hz
1080p25hz
1080p24hz
2160p30hz
2160p25hz
2160p24hz
smpte24hz
smpte25hz
smpte30hz
smpte50hz
smpte60hz
smpte50hz420
smpte60hz420
2160p50hz
2160p60hz
2160p50hz420
2160p60hz420

But the problem doesn’t occur because the TV has been off for some time. It occurs if the Vero4K is started when the TV is off.

As expected.

We fall back to 1080p as a safe resolution.
But you can override this, setting a disp_mode from your previous post, for example

fw_setenv hdmimode 1080p50hz
fw_setenv outputmode 1080p50hz