[TESTING] Kodi v19 builds for Vero 4K / 4K +

I have tested 19 for a while , but i reverted back to 18.9 because of stability issues which is normal since this is a test release.
But my question is , what are the main differences between 18.9 and 19 for a vero4K+ user like me, i am using the new 4.9 kernel which is the same in 19.
What other noticeable differences are there going te be, in the stable 19 version ?
speed , even beter picture quality …??

i’ve grab logs with the error I reported last week (and appears to be ignored):
https://paste.osmc.tv/etufenicob

I switch on the Vero 4k+, change the AV Receiver to another HDMI, then return again to the Vero 4K+ and the resolution is switched to 1024x768p. (Also is changed in the configuration).

1 Like

Tried watching 30 minutes of Gemini Man. While coming out of pause, I got a sad face error. I did a grab-logs -A but didn’t have debug logging on, so there probably isn’t anything useful in there… but just in case:
https://paste.osmc.tv/uramikuneh

Other things I noticed:

  • CPU temperature didn’t go above 85, which is good - back when I was using the 3.14 kernel I used to get thermal shutdowns on that movie.

  • Over the course of half an hour with subtitles on, 462 frames skipped, so it looks like that issue sadly isn’t fixed.

  • On the same screen where you can check for skipped frames, there’s a new bit of info in Kodi 19 which lists “missed VSyncs”. I’m not quite sure what the significance of that number is, but I’m guessing it shouldn’t be high; and after half an hour of viewing it was reading something like 1200.

  • Initially I got no audio output on the Dolby TrueHD track, but switching to another track and then back to that one again made it work.

If I can reproduce any of these things reliably, I’ll get some debug logs.

A firmware update for my Marantz NR1711 landed today, and the Vero on the v19 test build is now almost usable. I’m not quite back to where I was with the 4.9 test build, but some progress.

I can now re-boot safely and see the blue OSMC splash screen.

Marantz appear to have fixed the long-standing 4:4:4 1080/50p bug, previously this blank-screened with audio output still working, unless I set the Marantz to “8K Enhanced” mode.

Input switching away from the Vero and back is still flaky, but instead of the GUI occasionally dropping to 480p, it is now dropping to 720p. I enabled the HPD lock option and I think it’s helping, but it has not cured this issue, which did not happen on the 4.9 test build.

A recent rip of Red Dward on blu-ray is leading to a green screen and I have to pull the power of the Vero to get it back. A command-line log is needed?

EDIT: log for playback start resulting in green screen: https://paste.osmc.tv/jemekijayo

mkv’s with DTS-HRA audio are occasionally losing audio after chapter skips. A stop/resume brings it back. Everything is on pass-through. I will come back to that with a log once/if the system becomes more stable for general use.

Would be great to test the 4.9 build with the Marantz on its new firmware. Clearly something changed with the v19 test release that the Marantz did not like, as previously I had a stable system. But evidently there are bugs on the Marantz side as well, and who knows if some still remain.

log for a loss-of-audio event when chapter-skipping in an mkv with DTS-HRA audio. Never encountered this problem before. First few chapter skips are fine, then lose the audio. Stop/resume brings it back.

https://paste.osmc.tv/zajinipagu

Not ignored, but logs are a great addition, so thanks for that. Nothing to do with CEC. It used to be that if the EDID changed (as it does when you switch to another AVR input) the setting would stick. Now it seems Kodi is messing with the setting - not sure why but we will investigate.

You should be able to use ‘Lock HDMI HPD’ in Display settings to stop this happening.

Hi @fzinken

I finally got around to iperf3

Here’s the result:

iperf3 -R -c 192.168.86.50
Connecting to host 192.168.86.50, port 5201
Reverse mode, remote host 192.168.86.50 is sending
[  5] local 192.168.86.51 port 41434 connected to 192.168.86.50 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  11.4 MBytes  95.9 Mbits/sec                  
[  5]   1.00-2.00   sec  11.3 MBytes  94.9 Mbits/sec                  
[  5]   2.00-3.00   sec  11.3 MBytes  94.9 Mbits/sec                  
[  5]   3.00-4.00   sec  11.3 MBytes  94.9 Mbits/sec                  
[  5]   4.00-5.00   sec  11.3 MBytes  94.9 Mbits/sec                  
[  5]   5.00-6.00   sec  11.3 MBytes  94.9 Mbits/sec                  
[  5]   6.00-7.00   sec  11.3 MBytes  94.9 Mbits/sec                  
[  5]   7.00-8.00   sec  11.3 MBytes  94.9 Mbits/sec                  
[  5]   8.00-9.00   sec  11.3 MBytes  94.9 Mbits/sec                  
[  5]   9.00-10.00  sec  11.3 MBytes  94.9 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.04  sec   116 MBytes  97.2 Mbits/sec    0             sender
[  5]   0.00-10.00  sec   113 MBytes  95.0 Mbits/sec                  receiver

iperf Done.

Now for the other direction:

iperf3 -c 192.168.86.50
Connecting to host 192.168.86.50, port 5201
[  5] local 192.168.86.51 port 41438 connected to 192.168.86.50 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  11.8 MBytes  99.2 Mbits/sec    0    125 KBytes       
[  5]   1.00-2.00   sec  11.6 MBytes  97.1 Mbits/sec    0    133 KBytes       
[  5]   2.00-3.00   sec  11.0 MBytes  92.5 Mbits/sec    0    133 KBytes       
[  5]   3.00-4.00   sec  11.3 MBytes  95.1 Mbits/sec    0    133 KBytes       
[  5]   4.00-5.00   sec  11.5 MBytes  96.1 Mbits/sec    0    133 KBytes       
[  5]   5.00-6.00   sec  11.3 MBytes  95.1 Mbits/sec    0    133 KBytes       
[  5]   6.00-7.00   sec  11.3 MBytes  95.1 Mbits/sec    0    133 KBytes       
[  5]   7.00-8.00   sec  11.3 MBytes  95.1 Mbits/sec    0    133 KBytes       
[  5]   8.00-9.00   sec  11.3 MBytes  95.1 Mbits/sec    0    133 KBytes       
[  5]   9.00-10.00  sec  11.2 MBytes  94.0 Mbits/sec    0    133 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   114 MBytes  95.4 Mbits/sec    0             sender
[  5]   0.00-10.04  sec   113 MBytes  94.6 Mbits/sec                  receiver

iperf Done.

Speed looks as expected, right? It’s a Vero 4K (non-plus).

Yes that looks as expected for the Vero4k (non +).
So now question is what is he bitrate of the Movie and/or did it play without issues before?
If it played fine before then we may have to check the debug logs.

it played without issues before.

Here’s the log
https://paste.osmc.tv/nayecenemi

One part is a EOF which could indicate a network issue. But then it might also just try to seek to a wrong position.
Did you try to play it from USB stick to figure out if it is network or ffmpeg issue?

2021-04-27 11:47:31.217 T:2713    DEBUG <general>: Seek - </mnt/bigdisk1/main/Movies/Zack Snyder's Justice League (2021) 4K DV/Zack.Snyders.Justice.League.2021.2160p.HMAX.WEB-DL.DDP5.1.Atmos.DV.x265-MZABI.mp4> waiting for position 34009562991
2021-04-27 11:47:31.225 T:2697    DEBUG <general>: ffmpeg[0xaf868d18X]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
2021-04-27 11:47:31.247 T:2690    DEBUG <general>: ffmpeg[0xae29f148X]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
2021-04-27 11:47:31.852 T:2713    DEBUG <general>: Open - avformat_find_stream_info starting
2021-04-27 11:47:31.853 T:2747    DEBUG <general>: Process - </mnt/bigdisk1/main/Movies/Zack Snyder's Justice League (2021) 4K DV/Zack.Snyders.Justice.League.2021.2160p.HMAX.WEB-DL.DDP5.1.Atmos.DV.x265-MZABI.mp4> source read hit eof
2021-04-27 11:47:32.106 T:2713    DEBUG <general>: Open - av_find_stream_info finished
2021-04-27 11:47:32.107 T:2713    DEBUG <general>: CDVDDemuxFFmpeg::AddStream ID: 0
2021-04-27 11:47:32.107 T:2713    DEBUG <general>: CDVDDemuxFFmpeg::AddStream ID: 1
2021-04-27 11:47:32.107 T:2713    DEBUG <general>: AddStream - 3d subtitle plane = #0
2021-04-27 11:47:32.107 T:2713    DEBUG <general>: CDVDDemuxFFmpeg::AddStream ID: 2
2021-04-27 11:47:32.107 T:2713    DEBUG <general>: AddStream - 3d subtitle plane = #0
2021-04-27 11:47:32.107 T:2713    DEBUG <general>: CDVDDemuxFFmpeg::AddStream ID: 3
2021-04-27 11:47:32.107 T:2713    DEBUG <general>: ScanForExternalSubtitles: Searching for subtitles...
2021-04-27 11:47:32.183 T:2713    DEBUG <general>: ScanForExternalSubtitles: END (total time: 75 ms)
2021-04-27 11:47:32.183 T:2713     INFO <general>: CDVDVideoCodecFFmpeg::Open() Using codec: HEVC (High Efficiency Video Coding)
2021-04-27 11:47:32.183 T:2713    DEBUG <general>: CDVDVideoCodecFFmpeg - Updated codec: ff-hevc
2021-04-27 11:47:32.183 T:2713    DEBUG <general>: ExtractThumb - seeking to pos 4842685ms (total: 14528055ms) in /mnt/bigdisk1/main/Movies/Zack Snyder's Justice League (2021) 4K DV/Zack.Snyders.Justice.League.2021.2160p.HMAX.WEB-DL.DDP5.1.Atmos.DV.x265-MZABI.mp4
2021-04-27 11:47:32.184 T:2713    DEBUG <general>: SeekTime - unknown position after seek

Not yet. I’ll do that now. Ext4 or exfat? Does it matter?

Shouldn’t matter but surely ext4 should be ideal.

1 Like

I didn’t received any feedback of my message, I thought it was ignored.

I’m only trying to help, but if I send possible bugs and doesn’t receive any feedback, or at least a “we’ll investigate” or “please, we need more logs”, I think that the message maybe isn’t be read by any developer.

Anyway, thanks for your help!

1 Like

@fzinken Same video performs flawlessly on USB. Do you want the logs?

This is weird. The video I was playing was Harry Potter :rofl: Logs say differently.

I think no need for logs. So that would point to the network. But quite strange considering that you use autofs.
First test could be to copy the file from the NFS server to the USB Disk via the autofs mount to see if at least the sequential reading is fine. If that is working fine (with the respective time/bandwidth). If that is working then it could only be an issue with jumping in the file.

1 Like

@fzinken
Copied via nfs mount to usb. No problems. Then played the video and skipping was fast.

Just joined. I have discovered my first issue with the new build. I tried to watch an mkv 1080 movie with 5.1. The movie stuttered continuously . I was able to watch it by disabling hardware acceleration. I did not know if this is a known problem .

1 Like

No general problem know.

  1. Need to see mediainfo of the file (can use https://videosam.pl for that).
  2. Debug Logs when playing the video might give additional info

Here is the info.

l
Unique ID : 229760451856513965568077355159700664598 (0xACDA40E0917BA58DA824621D57807116)
Format : Matroska
Format version : Version 4
File size : 2.88 GiB
Duration : 2 h 1 min
Overall bit rate : 3 387 kb/s
Movie name : Inferno (2016) 1080p BrRip x264 - VPPV
Encoded date : UTC 2017-01-06 16:38:36
Writing application : mkvmerge v9.7.1 (‘Pandemonium’) 64bit
Writing library : libebml v1.3.4 + libmatroska v1.4.5

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 1 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 1 frame
Format settings, GOP : M=3, N=24
Codec ID : V_MPEG4/ISO/AVC
Duration : 2 h 1 min
Width : 1 920 pixels
Height : 1 036 pixels
Display aspect ratio : 1.85:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : A_AAC-2
Duration : 2 h 1 min
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Delay relative to video : -21 ms
Title : Surround
Language : English
Default : Yes
Forced : No