Dec. update broke playback of UHD content in 1080p

Help and Support
1

Hi,

got a new 4K tv (Sony KD-55XF9005, also called X900F) and was checking a few UHD movies through the still installed Denon AVR-1912 (only 1080p compatible).

With the October update installed, everything was perfect but directly after updating (didn’t change any settings on the tv/avr or in OSMC, didn’t change any cabling) to the December update, no UHD file would play anymore. All i get is a black screen and a “signal missing” message from the tv. From the network usage i can see that the vero is streaming! When i press the stop button, i can get back to the menu.

1080p content plays flawlessly.

I know this is quite the edge case here with everything 4k compatible BUT the AVR…if you are still interested, i can upload the log files.

Regards,
Burrito78

2

We need to see debug logs to know what’s going on here

Sam

3

https://paste.osmc.tv/afegeqasav

What I did:

  1. Enable debug logging
  2. Reboot
  3. Try to play UHD movie
  4. TV and AVR say „no Signal“
  5. Press stop
  6. Disable debug logging
4

From the logs I see that the Denon AVR wrongfully advertises itself as 4K compatible (forwarding the TVs EDID). Shouldn’t it filter out the resolutions it doesn’t support itself?

5

Should, shouldn’t… That’s the issue. Some AVRs adjust the EDID to combine the TV’s and their own capabilites to one new EDID. But some just pass the EDID to the source untouched.

This would indeed explain your issue. v18 will solve this for you as you can use resolution whitelisting to tell Vero manually to only output 4K resolutions up to 4K30 or no 4K at all.

6

ATM we are warning but not proscribing those resolutions:

Jan 03 13:31:10 osmc kernel: Mode 2160p30hz (VIC 95) needs 297MHz clock, at 444,8-bit - more than 225MHz
Jan 03 13:31:10 osmc kernel: Mode 2160p25hz (VIC 94) needs 297MHz clock, at 444,8-bit - more than 225MHz
Jan 03 13:31:10 osmc kernel: Mode 2160p24hz (VIC 93) needs 297MHz clock, at 444,8-bit - more than 225MHz
Jan 03 13:31:10 osmc kernel: Mode smpte24hz (VIC 98) needs 297MHz clock, at 444,8-bit - more than 225MHz
Jan 03 13:31:10 osmc kernel: Mode smpte50hz (VIC 101) needs 594MHz clock, at 444,8-bit - more than 225MHz
Jan 03 13:31:10 osmc kernel: Mode smpte60hz (VIC 102) needs 594MHz clock, at 444,8-bit - more than 225MHz
Jan 03 13:31:10 osmc kernel: Mode 2160p50hz (VIC 96) needs 594MHz clock, at 444,8-bit - more than 225MHz
Jan 03 13:31:10 osmc kernel: Mode 2160p60hz (VIC 97) needs 594MHz clock, at 444,8-bit - more than 225MHz

You just need to turn off adjust refresh rate.

7

If it was just the combination of a 4k tv with this AVR that gives problems, i wouldn’t care much because that AVR is going to be replaced shortly anyway.

What makes me wonder though is that it was working perfectly with the release before the Dec. update (Oct. update i think). What did change here and is this a bug in OSMC or also to be expected behavior now?

8

Lots of things have changed, but I can’t think of a reason why it worked for you before.

9

OK, i think we can conclude:

-Playback shouldn’t have worked in either OSMC version, because EDID is wrong for the AVR.
-The workaround for this setup would be to disable “Adjust refresh rate” so the Vero doesn’t try to switch from 1080p to 2160p.
-There is probably no bug in the Dec. release that prevents this setup from working with “Adjust refresh rate” enabled.

10

It’s possible to override the EDID from Kodi’s perspective; but this may be trickier with the kernel at the moment.