Stuttering h265 video on Vero4k+

I believe the issue started with the last update we accepted on the Vero and impacts all 4k and h265 encoded files accessed through the library and video routes. Files are stored on USB HDDs connected to the Vero via a Startech powered hub.

I have uploaded log files:
https://paste.osmc.tv/ozecupumil

Thanks

Looks like your system may have only partially installed the update, so it’s falling back to software decoding. Do you know how to use SSH?

It seems only my H.265 media is also stuttering. I’m accessing my NAS over NFS.
Log: https://paste.osmc.tv/jasolaxopo

Your logs show that this is not related.

Do you have some background context to your issue?

Sure thing! I can sort of describe it as a slideshow effect when viewing H.265 content. Audio is played back normally at the same time. BT.709 and BT.2020 are both affected.

Here’s a link to a video capture: 37.83 MB file on MEGA

General
Unique ID : 153619136597594551509054798579902685124 (0x7391F8327D897E26668D1AB3377F9FC4)
Complete name : /Volumes/TV Shows/Burn Notice/Season 02/Burn Notice - S02E01 - Breaking and Entering.mkv
Format : Matroska
Format version : Version 4
File size : 2.86 GiB
Duration : 43 min 10 s
Overall bit rate : 9 487 kb/s
Encoded date : UTC 2018-07-10 03:52:02
Writing application : mkvmerge v24.0.0 (‘Beyond The Pale’) 64-bit
Writing library : libebml v1.3.6 + libmatroska v1.4.9

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 43 min 10 s
Bit rate : 8 844 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Bits/(Pixel*Frame) : 0.178
Stream size : 2.67 GiB (93%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : E-AC-3
Format/Info : Enhanced AC-3
Commercial name : Dolby Digital Plus
Codec ID : A_EAC3
Duration : 43 min 10 s
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 198 MiB (7%)
Language : English
Service kind : Complete Main
Default : Yes
Forced : No

Text
ID : 3
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Duration : 42 min 21 s
Bit rate : 103 b/s
Count of elements : 729
Stream size : 32.1 KiB (0%)
Language : English
Default : No
Forced : No

I’d suggest uploading a sample of an affected clip.
I’m not sure how your issue is related to OPs, but a separate post is probably better, so both of you have a chance to have your issue resolved.

Cheers

Sam

I will definitely do that.

Cheers.

Hi Sam, Yes I know how to SSH

Try (and post output if it fails) the output of

sudo apt-get update
sudo apt-get dist-upgrade

Brilliant, all videos playing seamlessly, hardware decoding in use, thank you.

Jason

1 Like

Glad to hear.

I have exact same issue. On dist-upgrade i get:

Get:1 http://security.debian.org bullseye-security/main armhf ntfs-3g armhf 1:2017.3.23AR.3-4+deb11u3 [401 kB]
Get:2 http://security.debian.org bullseye-security/main armhf libntfs-3g883 armhf 1:2017.3.23AR.3-4+deb11u3 [161 kB]
Fetched 562 kB in 1s (1010 kB/s)
(Reading database … 40358 files and directories currently installed.)
Preparing to unpack …/ntfs-3g_1%3a2017.3.23AR.3-4+deb11u3_armhf.deb …
Unpacking ntfs-3g (1:2017.3.23AR.3-4+deb11u3) over (1:2017.3.23AR.3-4+deb11u2) …
Preparing to unpack …/libntfs-3g883_1%3a2017.3.23AR.3-4+deb11u3_armhf.deb …
Unpacking libntfs-3g883 (1:2017.3.23AR.3-4+deb11u3) over (1:2017.3.23AR.3-4+deb11u2) …
Setting up vero364-image-4.9.269-16-osmc:arm64 (4.9.269-16-osmc) …
11+1 records in
11+1 records out
12318720 bytes (12 MB, 12 MiB) copied, 0.332134 s, 37.1 MB/s
/bin/dd: error writing ‘/dev/dtb’: Cannot allocate memory
0+1 records in
0+0 records out
0 bytes copied, 0.0156381 s, 0.0 kB/s
Could not upload DTB to eMMC
run-parts: /etc/kernel/postinst.d/upload-to-emmc exited with return code 1
dpkg: error processing package vero364-image-4.9.269-16-osmc:arm64 (–configure):
installed vero364-image-4.9.269-16-osmc:arm64 package post-installation script subprocess returned error exit status 1
Setting up libntfs-3g883 (1:2017.3.23AR.3-4+deb11u3) …
Setting up ntfs-3g (1:2017.3.23AR.3-4+deb11u3) …
dpkg: dependency problems prevent configuration of vero364-kernel-osmc:arm64:
vero364-kernel-osmc:arm64 depends on vero364-image-4.9.269-16-osmc; however:
Package vero364-image-4.9.269-16-osmc:arm64 is not configured yet.

dpkg: error processing package vero364-kernel-osmc:arm64 (–configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.31-113) …
Errors were encountered while processing:
vero364-image-4.9.269-16-osmc:arm64
vero364-kernel-osmc:arm64
E: Sub-process /usr/bin/dpkg returned an error code (1)

Please help me

What’s the output of df -h?

Also can try sudo dpkg --configure --pending

df -h output:

Filesystem Size Used Avail Use% Mounted on
devtmpfs 991M 0 991M 0% /dev
tmpfs 995M 1.2M 993M 1% /run
/dev/vero-nand/root 14G 1.8G 12G 14% /
tmpfs 995M 0 995M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup
/dev/sda1 233G 44G 190G 19% /media/media
tmpfs 199M 0 199M 0% /run/user/1000

sudo dpkg --configure --pending:

Setting up vero364-image-4.9.269-16-osmc:arm64 (4.9.269-16-osmc) …
11+1 records in
11+1 records out
12318720 bytes (12 MB, 12 MiB) copied, 0.339596 s, 36.3 MB/s
/bin/dd: error writing ‘/dev/dtb’: Cannot allocate memory
0+1 records in
0+0 records out
0 bytes copied, 0.00233533 s, 0.0 kB/s
Could not upload DTB to eMMC
run-parts: /etc/kernel/postinst.d/upload-to-emmc exited with return code 1
dpkg: error processing package vero364-image-4.9.269-16-osmc:arm64 (–configure):
installed vero364-image-4.9.269-16-osmc:arm64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of vero364-kernel-osmc:arm64:
vero364-kernel-osmc:arm64 depends on vero364-image-4.9.269-16-osmc; however:
Package vero364-image-4.9.269-16-osmc:arm64 is not configured yet.

dpkg: error processing package vero364-kernel-osmc:arm64 (–configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
vero364-image-4.9.269-16-osmc:arm64
vero364-kernel-osmc:arm64

@sam_nazarko any idea?

Hi @Quicky1990

WIthout logs – it’s hard to tell, but I suspect you are on a very old version of OSMC.

Can you please upload some via My OSMC?

As you are familiar with the command line, please try:

sudo fw_setenv osmc_defenv 1
reboot

Then after the system comes back up, try:

sudo apt-get -f install

This relies on an update to date bootloader. Without logs – I can’t tell what state your system is in

Sam

The above went through without problems…

now sudo apt-get dist-upgrade does this:

Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 Index of /debian bullseye InRelease
Get:3 Index of /debian bullseye-updates InRelease [44.1 kB]
Hit:4 Index of /osmc/osmc/apt bullseye InRelease
Fetched 44.1 kB in 2s (22.1 kB/s)
Reading package lists… Done
osmc@osmc:~$ sudo apt-get dist-upgrade
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
The following packages were automatically installed and are no longer required:
libapt-inst2.0 libbind9-161 libcdio18 libdns1104 libdns1110 libevent-2.1-6
libfdk-aac1 libgeoip1 libicu63 libidn11 libip4tc0 libip6tc0 libiptc0
libisc1100 libisc1105 libisccc161 libisccfg163 libjson-c3 liblwres161
libmpdec2 libnfs12 libprocps7 libpython2-stdlib libpython2.7
libpython2.7-minimal libpython2.7-stdlib libpython3.7 libpython3.7-minimal
libpython3.7-stdlib libreadline7 python2 python2-minimal python2.7
python2.7-minimal python3.7 python3.7-minimal
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Guess all is ok now.

Glad to hear this. I’m guessing that you didn’t update your system for a long time.