That is a misconfiguration on your TV.
Put your TV to Just Scan or 1:1 depending on your TV Brand.
Hm, I am no expert, but if the TV would be misconfigured, wouldn’t be the video itself also scaled? I don’t think the UI overlay is sent separate for the TV to compose it… For me, the video is correct, only the Kodi overlay is bigger…
Well if you are 100% sure that the Video is correct then it might not be the case, but doesn’t harm to check if your TV is configured correct.
Also just checked, here it seems ok.
Well, feel pretty stupid now :-), of course you were right. For some reason I was sure the video was correct, but I tried some testing pattern video from youtube now to double check. And you were right, the video was also chopped, so I adjusted TV for 1:1 and all is fine now. Now there is not a single glitch on vero with 4.9 kernel for me :-). Thank you and sorry for the noise.
1 Like
Do you have subtitles turned on?
No
Hi,
I’ve tried another rip with the same result.
This is the log file: https://paste.osmc.tv/jitocenita
This is the mediainfo:
Summary
General
Unique ID : 82665525175021210808663622239864400186 (0x3E30CD10527BC683D7AFAEE2400AA93A)
Complete name : Geminis (2019).mkv
Format : Matroska
Format version : Version 4
File size : 70.7 GiB
Duration : 1 h 57 min
Overall bit rate mode : Variable
Overall bit rate : 86.5 Mb/s
Movie name : Geminis 2160p
Encoded date : UTC 2020-01-31 14:17:47
Writing application : mkvmerge v40.0.0 (‘Old Town Road + Pony’) 64-bit
Writing library : libebml v1.3.9 + libmatroska v1.5.2
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Commercial name : HDR10
Format profile : Main 10@L5.1@High
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 57 min
Bit rate : 81.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.163
Stream size : 66.2 GiB (94%)
Title : Geminis 2160p
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0010 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 5180 cd/m2
Maximum Frame-Average Light Level : 1577 cd/m2
Audio #1
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 1 h 57 min
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)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 536 MiB (1%)
Language : Spanish
Service kind : Complete Main
Default : Yes
Forced : Yes
Audio #2
ID : 3
Format : MLP FBA 16-ch
Format/Info : Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Codec ID : A_TRUEHD
Duration : 1 h 57 min
Bit rate mode : Variable
Bit rate : 4 204 kb/s
Maximum bit rate : 7 944 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 1 200.000 FPS (40 SPF)
Compression mode : Lossless
Stream size : 3.44 GiB (5%)
Language : English
Default : No
Forced : No
Number of dynamic objects : 11
Bed channel count : 1 channel
Bed channel configuration : LFE
Audio #3
ID : 4
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 1 h 57 min
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)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 536 MiB (1%)
Language : English
Service kind : Complete Main
Default : No
Forced : No
Text #1
ID : 5
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Duration : 1 h 47 min
Bit rate : 0 b/s
Count of elements : 12
Stream size : 271 Bytes (0%)
Title : Forzados
Language : Spanish
Default : Yes
Forced : Yes
Text #2
ID : 6
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Duration : 1 h 47 min
Bit rate : 49 b/s
Count of elements : 1332
Stream size : 39.1 KiB (0%)
Language : Spanish
Default : No
Forced : No
Text #3
ID : 7
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Duration : 1 h 45 min
Bit rate : 49 b/s
Count of elements : 1356
Stream size : 38.5 KiB (0%)
Language : English
Default : No
Forced : No
Menu
00:00:00.000 : en:Глава 01
00:07:21.650 : en:Глава 02
00:15:31.681 : en:Глава 03
00:18:13.134 : en:Глава 04
00:24:39.520 : en:Глава 05
00:30:59.441 : en:Глава 06
00:34:09.464 : en:Глава 07
00:42:40.308 : en:Глава 08
00:50:24.897 : en:Глава 09
00:56:45.819 : en:Глава 10
01:03:30.306 : en:Глава 11
01:08:13.172 : en:Глава 12
01:16:45.935 : en:Глава 13
01:24:43.996 : en:Глава 14
01:30:04.733 : en:Глава 15
01:34:00.927 : en:Глава 16
01:42:14.462 : en:Глава 17
01:47:07.588 : en:Глава 18
I’ve shown in debug that some times the fps fall to 24 or 35fps:
My actual kernel: Linux osmc 4.9.113-29-osmc #1 SMP PREEMPT Thu Dec 31 06:21:12 UTC 2020 aarch64 GNU/Linux
I’ve detected another issue, when resuming an UHD blu-ray directory structure, it doesn’t work.
These are the debug logs: https://paste.osmc.tv/radonokoji
After kernel upgrade, librespot (raspotify 0.12 as per howto) dies with SIGILL:
systemctl status raspotify
* raspotify.service - Raspotify
Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: signal) since Tue 2021-01-12 14:56:17 EET; 8s ago
Process: 17091 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS)
Process: 17097 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS)
Process: 17099 ExecStart=/usr/bin/librespot --name ${DEVICE_NAME} $BACKEND_ARGS --bitrate ${BITRATE} $CACHE_ARGS $VOLUME_ARGS $OPTIONS (code=killed, signal=ILL)
Main PID: 17099 (code=killed, signal=ILL)
# /usr/bin/librespot -h
Illegal instruction
Please reboot the device and then provide full logs (grab-logs -A)
Full logs are provided in first post. As seen there, I also made an effort to compile librespot with alsa support myself, but it didn’t help much.
Unfortunately, as Spotify was priority to keep household happy, I have reinstalled and went back to 3.14 kernel 
The logs were truncated, which is why I asked you to restart the device and resubmit them.
Do you want to close the thread question ?
SIGILL suggests, that librespot armhf binary is in conflict with new kernel or ld. As there was no core dumped, I cannot point to symbols.
Alright, I guess it will come up again once newer kernel is pushed to main repo.
OSMC is configured not to produce core dumps. (Run ulimit -a)
You can change it (ulimit -c unlimited) but most of the binaries will be stripped.
two days ago I watched a movie and in the mean time I kept downloading on the Vero by means of the Transmission app.
When I wanted to watch a new movie just now my TV did not have a signal from the Vero 4K. So I did a reboot by disconnecting the power and connecting it again.
Logfiles here: https://paste.osmc.tv/cerosubube
Last weekend I again had the black screen issue I mentioned in a previous post. I am using the Aeon Nox Silvo skin. This time no black screen but a completely missing connection. Could it have to do with the skin?
Do these logs show anything interesting? Do you need other logs?
-edit-
I am going away for a couple of days and I will now reboot the Vero 2 times in a row. Then I will enable the kodi logging and when I get back I will see what the status is.
With the latest update I’ve started noticing solid green video output (with UI visible) when resuming playback of 4K/UHD H.265 titles.
It has been veeeeery intermittent however, any way to try and capture logs in these situations?
As long as Vero doesn’t lock up you should be able to get logs via ssh. Does the green go away if you stop the video?
Earlier i saw a comment that an update fixed issues with the red color during HDR playback.
I calibrated my TV now (test pattern directly from vero4k). Do i have to do this procedure all the time again after an update or do you “keep” the settings how they are right now?
Yes the green does go away when the video is stopped, however replaying the video will bring back the green - A restart reboot does resolve it though.
Apologies for not being clear about capturing logs - What I meant was rather than enabling logging for extended periods of time (i.e. a few days) until the intermittent issue recurs, is there a way to capture the required data when issue occurs or potentially limit the size of the logs so it doesn’t get too big for uploading?
Understood. There is probably no need for kodi debug logs which do get big, but if it happens, can you note the time when it happened so we can find the right place in the kernel log.