I have noticed that with HEVC x265 content, the Vero 4K plays fine, but if I was to hit the Fwd button, the playback starts glitching (best way I can define it). I typically play via an NFS mount, but to rule out the network, I have tried playing back via a USB drive directly with the same results.
If you want a sample, try any ‘megusta’ encoded files.
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device twice(!)
reproduce the issue
upload the log set (all configs and logs!) either using the
Log Uploader method within the My OSMC menu in the GUI or the
ssh method invoking command
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
OSMC skin screenshot:
Uploaded as instructed via My OSMC
There are discontinuities, which cause this issue.
This is likely because of your settings.
You should set the GUI to 1080p and enable Adjust Refresh Rate.
It should then work properly.
Gave it a go. Set the display resolution to 1080p.
Video settings to adjust refresh rates all the time.
Replayed the same file, and the ‘glitch’ is still there. Just to explain, sound and playback still paying. Every few seconds the image on screen flickers briefly, the resumes and happens again.
Logs after changes at: https://paste.osmc.tv/dizanohali
I’ll check this out tomorrow.
Can you upload a sample file to https://videosam.pl?
Sorry - hard to provide a sample. But some I know of having trouble are some of the Megusta releases (megusta hevc x265).
We aren’t going to pirate material to test. Additionally, if the issue is only present in some random pirate’s rips, it’s more likely that the issue is due to his encode method and not an OSMC issue.
If you wish to have the issue looked at, use something like mkvtoolnix to create a small sample file that demonstrates the issue.