When it’s ready – it will be delivered as an automatic update.
This will be announced on the blog.
I’ve no idea about this. Doesn’t seem to be anything significant in the log.
No issues on my Shield TV’s, already did a full reinstall as well.
Got the issue only with AAC with multiple files and some just don’t have issues.
Just checking - are the Shields connected direct to TV or also feeding the Onkyo?
Everything is connected to the AVR, which is the only device connected to the TV.
Strange bug for me today, I connected a usb 3.0 external drive and my vero 4k+ just shut down (lost connection), i unplugged the power cable and tried to reboot, it was ok until i tried to play a movie from the external drive and the same thing happened again.
Here is my today log file:
https://paste.osmc.tv/yecuzuvejo
BlockquoteJun 29 15:55:18 osmc kernel: snd_spdif_dai: aml_hw_iec958_init,runtime->rate=192000, runtime->channels=8
same source mode(0), stream format=TrueHD
Jun 29 15:55:18 osmc kernel: snd_spdif_dai: set 4x audio clk for 958
Jun 29 15:55:18 osmc kernel: hdmitx: audio: aout notify rate 192000
Jun 29 15:55:18 osmc kernel: hdmitx: audio: aout notify size 16
Jun 29 15:55:18 osmc kernel: hdmitx: audio: hdmi_ch: 0 speaker_layout: 0
Jun 29 15:55:18 osmc kernel: [0]VH265: output first frame
Jun 29 15:55:18 osmc kernel: video first pts = 66204c
Jun 29 15:55:18 osmc kernel: DI bypass all 3840x2160-0x101000.
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: [0]cur lcu idx = 0, (total 2040), set error_mark
Jun 29 15:55:18 osmc kernel: audio_dsp: buf=2
Jun 29 15:55:18 osmc kernel: audio_dsp: IEC958_mode_raw=2
For the first time, I’ve had these as well… We’ll try investigating 
2 Likes
How is the drive powered? The Vero should not be depended on to power external disks. Try as recommended with a self powered USB hub.
Its a 2.5 portable external hard drive powered only by usb.
Yeah, so you need a powered hub.
1 Like
Quite a bit of headscratching in the team on this. Tentative conclusions so far:
- audio is affected only when playing at 4k24Hz resolution - other resolutions (1080p or 4k at different refreshrates) play OK
- audio glitches are random (more precisely, I don’t get glitches at the timestamps you reported, but my glitches do tend to occur at the same places each time I play the clip)
- audio and/or video are affected differently by different versions of AML microcode and AML h264 decoders.
Could you confirm (1) and re (3) can you post the output of:
cat /etc/modules-load.d/amlvideodri.conf
md5sum /lib/firmware/osmc/video/*
just so we know we are on the same page.
Thanks.
osmc@vero4k:~$ cat /etc/modules-load.d/amlvideodri.conf
amvdec_h265
amvdec_vc1
amvdec_vp9
amvdec_mmpeg12
amvdec_h264mvc
amvdec_h264
amvdec_mmpeg4
amvdec_ports
osmc@vero4k:~$ md5sum /lib/firmware/osmc/video/*
da048ceec3cbc8433b30b286cad86bc1 /lib/firmware/osmc/video/h264_enc.bin
2a9a9020529342dff875fd2e60d9d615 /lib/firmware/osmc/video/video_ucode.bin
Will have a look if I got any different refreshrates.
480p 23,976 h264 no issue
480p 25.000 h264 no issue
480p 29,970 h264 no issue
576p 25.000 h264 no issue
720p 23,976 h264 (sw) no issue
1080p 29,970 h264 no issue (5.1 track)
2160p 23,976 h264 issue every 25sec or so
2160p 29,970 h264 issue every 25sec or so
1080p 23,976 h265 no issue
2160p 23,976 h265 no issue
I hope you have enough with this info, couldn’t find more files atm 
Thanks. All useful to know but I didn’t phrase it right. I can make your 2160p24Hz clip play nicely if I turn off refreshrate switching and set the output to 2160p60Hz or 1080p24Hz (say). If you can do the same then we’re not looking at differences between TVs. I also get the same results whether I play direct to TV or through my AVR.
Are all those clips AAC BTW?
All are AAC indeed.
Woah indeed no skipping when I disable refreshrate switching 
1 Like
So I have to ask - is refreshrate switching turned on in the Shields?
Yes it is, with the same setting: on start / stop
MKA Audio Files (as opposed to MKV Video Files) - Problems with current playback time display
I have noticed the following problem on my Vero 4K+ whilst using software version ‘OSMC November 2020 2020.11-1’ and I’m wondering whether it will be corrected in the next Vero 4K+ release with Kodi 19.
I dont really want to upgrade to the latest Kodi 19 test build and I am waiting patiently for a more formal release.
Perhaps someone else with the latest Kodi19 test build could check whether this problem has been resolved - if not, it needs looking at !
Basically the problem concerns the incorrect (‘flickering’) display of the current playback time field (and consequently its expected end-time) for MKA audio files. Its best to view the MP4 videos to understand the problem, provided by way of the link below.
I know that the MKA file format is not a particularly common, but it is useful for containing original (Dolby/DTS multi-channel) audio streams and a chapter index. I quite often convert these to multi-channel FLACS.
So, with my test MKA files I note the following types of audio streams are affected or not as the case maybe:
ATMOS TrueHD 7.1 - affected
Dolby Digital AC3 5.1 - seems to be OK
DTS 5.1 - affected
DTS-HD MA - affected
LPCM 24-96 2.0 - seems to be OK
LPCM 24-96 5.1 - seems to be OK
I have provided a link below to a folder containg a zip archive with six test MKA audio files, half of which exhibit the problem, along with evidence for each MKA audio file, of the problem in the form of videos of my TV screen, displaying the Vero 4K+ Kodi playback screen (default skin).
in folder ‘Vero 4K MKA Audio Problem’
I look forward to hearing more about this, and hope that it will contribute towards the next Vero 4K OSMC/Kodi release sometime soon !
Hi,
This is probably an issue with the version of ffmpeg which shipped with Kodi v18.
I’m sure someone can try this on Kodi v19 (which has a newer version) in due course and give some feedback
Sam
1 Like
I can confirm the exact same behaviour like you described with the newest build - although the issue is most noticable with Dolby TrueHD as the time indicator is not just flickering a bit, but jumping a lot.
1 Like
Would this be ffmpeg? In my testing the problem affects only passthrough. Seems to me it’s Kodi getting confused with the timestamps.
1 Like