4k video playback issue after October update


#22

so it seems the update was done, but the issue sadly remained exactly same as I described in my 1st post.
Btw how do I know that the update was successful?
I went into the System info and I see under Version info, Compiled: Oct 31 2018


#23

What is the output of:

uname -a

#24

Linux osmc 3.14.29-127-osmc #1 SMP Sat Nov 10 20:21:10 UTC 2018 aarch64 GNU/Linux


#25

Good, you are on the correct version.

At this point we need new logs. Also, if you’ve been reading here there have been several people report that their problem was with the HDMI cable. Even quality cables have been an issue so I’d suggest trying a different cable.


#26

OK, so I enabled debug logging and I tried to play a few 4K files. Logs are here:
http://paste.osmc.tv/wirabezovo

Please look at them and if you don’t see anything suspecious I will buy new HDMI cables.


#27

I’m not sure if this could be a problem:

00:26:17.745 T:3068130048    INFO: ffmpeg[B6DFF300]: Input #0, matroska,webm, /media/USB DATA/MOVIES/Jurassic.World.Fallen.Kingdom.2018.2160p.UHD.HDR.Blu-Ray.Remux.HEVC.DTS-HD-MA.7.1.HUN-No1/Jurassic.World.Fallen.Kingdom.2018.2160p.UHD.HDR.Blu-Ray.Remux.HEVC.DTS-HD-MA.7.1.HUN-No1.mk':

It’s a webm remux. I’d suggest that you use MakeMKV (or a similar tool) and create a straight rip of a UHD disk instead of a questionable remux.


#28

hi,

See the linked posts, I have the same issue, even with the updated kernel.

One thing you could try is removing the Denon from the display chain (connect the vero directly to the tv/projector). Without the Denon it works for me in the new update – with the Denon 4k only works before the October update.

Maybe this can help to narrow down the issue (and get me back to playing 4k content ;))


#29

Hi @obstler42 – just to confirm – did you try the updated kernel?
Could you please try the instructions again as we made some further improvements today.

Many thanks.

Sam


#30

hi,

updated to

Linux vero4k 3.14.29-128-osmc #1 SMP Fri Nov 16 16:52:34 UTC 2018

unfortunately still no 4k playback…

Also with this update there is no signal during the boot process (before I could see text for a second and then the osmc logo screen). Kodi UI displays fine though.


#31

Please post logs with vero connected through your AVR and describe the videos you are trying to play (name, resolution, framerate, bitdepth).

Remind us what model of TV and AVR you have.


#32

There was apparently another update, so now I am on

Linux vero4k 3.14.29-129-osmc #1 SMP Sat Nov 17 17:40:12 UTC 2018 aarch64 GNU/Linux

Unfortunately still the same, no 4k playback at all – just results in No signal, and also no sound on the AVR.

Here is the log: http://paste.osmc.tv/ovetenuvic

Display chain: Vero4k+ – Denon X6500H – Sony VW570

4k has not worked on any build since the October update, before all different 4k files played fine (if too dark, but that should be fixed – just can’t see it yet ;))

The two files I was playing in the log are:

demo 2160p uhd 10 bit HDR TrueHD Atmos x265.mkv
    Video: HVC1 3840x2160 23.976fps [V: hevc main 10, yuv420p10le, 3840x2160 [default]]
    Audio: TrueHD 48000Hz 8ch 9216kbps [A: English [eng] (truehd, 48000 Hz, 7.1, s24) [default]]

and

LG Chess 4K HDR Demo.mp4
    Video: HEVC 3840x2160 59.94fps [V: hevc main 10, yuv420p10le, 3840x2160]
    Audio: AAC 48000Hz stereo 384kbps [A: aac lc, 48000 Hz, stereo, 384 kb/s]

Both played before October update, as did all other 4k files.

Also still with this kernel there is no display (logo) during bootup, this is new for kernel -128 and -129

Again, when I connect the Vero4k directly to the Sony projector (without the AVR) 4k plays fine.

So the problem must lie somewhere in how vero talks to the Denon receiver since the October update.

My previous log with kernel -127 is here: https://discourse.osmc.tv/t/testing-vero-4k-4k-video-improvements/74832/343?u=obstler42


#33

I can’t inmmediately see anything of note in those logs but will look closer tomorrow.

Could you try echo 422now | sudo tee /sys/class/amhdmitx/amhdmitx0/attr.


#34

When should I do that? After reboot? Before/after/during media playback?


#35

any of the above.


#36

Yes, after sending the command 24fps 2160p 10bit content plays fine now!

Only the 60fps 10bit 2160p file (second file from the log above, LG chess demo) doesn’t play – probably because that needs to playback as 420 for bandwidth reasons (before October and without the Denon in the display chain that plays fine, too).

So partial progress!


#37

Good to hear, thanks. As I suspected (and I think we had indications of this with the test kernels before the October release) there is a problem with 444,10bit modes.

Can you cd /sys/class/amhdmitx/amhdmitx0 and confirm what cat config says as you are trying to play a 4k60p10bit file as you issue:

  • echo now | sudo tee attr
  • echo 422now | sudo tee attr
  • echo 4208bitnow | sudo tee attr

The last one should give you a picture but with banding. It may also give you garish green colours - if so just stop and restart the vid.


#38

Here is the output:

osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ echo now | sudo tee attr
now
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ cat config
cur_VIC: 353
VIC: 353 3840x2160p60hz
Colour depth: 10-bit
Colourspace: YUV420
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000029a, Vid clock div 0x000b0000
audio config: on
3D config: off
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ echo 422now | sudo tee attr
422now
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ cat config
cur_VIC: 353
VIC: 353 3840x2160p60hz
Colour depth: 10-bit
Colourspace: YUV420
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000029a, Vid clock div 0x000b0000
audio config: on
3D config: off
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ echo 4208bitnow | sudo tee attr
4208bitnow
osmc@vero4k:/sys/class/amhdmitx/amhdmitx0$ cat config
cur_VIC: 353
VIC: 353 3840x2160p60hz
Colour depth: 8-bit
Colourspace: YUV420
Colour range: limited
EOTF: HDR10
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off

First two resulted in No Signal, the third played back as you expected.

What’s interesting is that my projector actually reported the signal as 2160p HDR10.


#39

That shouldn’t happen. Can you post a log for that case, please?


#40

Do I have to do the echo … attr commands while the media is playing? I always stopped playback, sent the echo commands, started playback and then got the config while media was playing.


#41

It shouldn’t matter. Once you have written something to attr it sticks until you reboot.