I watched the whole thing, and no longer wonder why the world is in the state it is in. No problems with the Vero.
1 Like
Hehe yeah lots of truth in it, sadly… 
Same like for me, sometimes happens, and sometimes not. Totally random, no pattern to notice, but only during HDR10+ is active 
What is the name of the TV series, and what episode did you watch?
I am intrigued. 
The Boys S04E04
I have the 4 seasons of that in 1080p. I have not watched any yet.
I will grab S04E04 in 2160 & watch it, to see how it plays.
My TVs have HDR 10+
I had issues not only with that one episode…
The episode I am getting has “HDR10Plus” in its name, so let’s see how it goes.
It will be 24/48 hours before I watch it.
Perhaps you could grab and post some upto date logs ?
Well, I watched the whole episode.
Now I need therapy!
Although I haven’t seen any of them, I will now delete all four seasons of the series.
I have my Vero V connected directly to a 4K HDR10+ Samsung TV. I played the episode from a 1TB external Hard Drive connected to a powered USB 3 hub. I played the first half of the episode with the hub connected to the USB 2 port in the Vero V. I then plugged the hub into the USB 3 port of Vero V and played the second half. There was no difference in playback, The episode played flawlessly.
1 Like
Thanks for testing though …
Yeah, I also dont have it in every HDR10+ file, but it keeps coming back again and again from time to time ;>
It’s not clear from the log what your setup is. I see references to embuary, suggesting you are using emby, and themoviedb which is deprecated. And a load of error messages from python.
I tested with an OSMC skin named embuary, but thats uninstalled long time. I also no longer use the external scraper. I am maintaining everything in tinymediamanager, which is creating all the nfos and osmc only puts everything in the library via local scaper only.
Python maybe comes from the deprecated (Zomboided) vpn.manager.service. But as suggested in the past that one is currently deactivated. I only need it sometimes for watching TV.
As requested previously, we need logs to get a better understanding of the problem. Please see How to submit a useful support request - General - OSMC
Yeah already provided some, but can do it again… but most likely not with the problem showing up 
Fresh set of log: https://paste.osmc.tv/odixowofuk
Watched the same episode again, no crash…
Ideally, we need a log where you experience an issue.
Yeah I know, had that once but no further log entries were written after freeze
We are working on improving logging during hard freezes, which might be beneficial in the future for cases like this.
Sam
1 Like
I’m still wondering about your addons. I see similar log messages from @redrocklobster whose issue may be similar. Can you try wiping all your settings:
systemctl stop mediacenter
mv ~/.kodi ~/kodibak
systemctl start mediacenter
Then just reattach the source where those problem videos are kept and see what you get. After testing, you can wind back with
systemctl stop mediacenter
rm -r ~/.kodi
mv ~/kodibak ~/.kodi
systemctl start mediacenter
Hm ok, just had another crash, watched remaining movie aa suggested by you in a clean osmc with debug log enabled. Only 15min were left and it did not crash again, but Ill give it another try.