So i got a new TV (Sony Bravia 9) and everything worked ok but now i have a File where on 2 Scenes the Pictures stutter/hangs, whats confusing to me that it only happens in HDR10 if i play the same Movie with DV Profile 5 it doesnt stutter/hang. So i thought its the HDR10 File itself but it isnt it played without a Problem on my LG G5 with Ugoos AMB6+.
I tested some things and it looks like the Vero V is sending a resync signal. If i turn off framerate Matching it doesnt stutter/hang.
The internal media player of the TV also plays it fine.
Does it happen in the exact same place in the file every time? If you can upload just that segment somewhere, that would probably help the OSMC folks look at it and for others to see if they can duplicate the issue on their setup.
Yes but what’s funny if you jump into the scene, then it doesn’t happen, but when you jump 20 seconds before the scene, the stutter happens. So yeah can be reproduced. I will upload a sample in a few minutes.
Edit:
First stutter/freeze 04:23 (when she wants to knock on the alarm clock) it stutter/freezes for one second.
Second stutter/freeze 05:05 (he walks in the kitchen) it stutter/freezes for one second.
Rest of the movie was stutter/freeze free atleast i didnt notice any others.
Just tested your file as it sounded similar to an issue I was having playing a UHD rip of The Green Mile (HDR10) on my Sony A95L.
Your file plays fine if I have ‘Use Limited Colour Range’ disabled (settings>system>display). If I enable this option, I see stutters in exactly the same places as you.
Worth a try to see if it fixes things for you. I see no disadvantage to disabling this setting on this tv - still getting proper blacks.
using a TV Philips OLED910 (with and without image motion enhancement)
direct connected to the TV but also via AVR SONY STR-DN1080
adjust display refresh rate set to ‘on start/stop’ and ‘always’
use limited colour range on/off
using actual development staging of OSMC and current stable release
Result: None of the combinations here result in the effect or behavior you described.
The log file excerpt isn’t helpful, but I’m afraid we won’t find anything usable in the standard logs either… though it’s worth a try:
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 grab-logs -A
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.
Interesting. I can’t think of any reason for this behaviour. I will test on Panasonic and Philips. Not every TV accepts full-range video on HDMI with YUV. If you are not getting crushed blacks and blown whites then I guess the Sony does.
I have the standard firmware on it didn’t update yet because the newest update seems broken (with Dolby vision not working at all over HDMI). So I’ll wait with the updates until Sony fixed the current firmware. But it’s interesting that the issue only is in HDR10 I didn’t have it with Dolby Vision but also it makes no difference turning on and off the limited range setting (in terms of color/black levels) but fixes the issue.
Yeah, this limited colour range frame skipping behaviour has been there since owning the set, well before the recent broken firmware update.
It does feel odd that in my case the issue wasn’t present in a more consistent way with limited colour range enabled, as I didn’t see the same behaviour in any of my other HDR10 media. Just two frame skips in one film, which played perfectly otherwise. I do remember testing this on an Ugoos AM6B+ at the time running CoreELEC, with same results.
To be sure, you could connect the Vero to the LG5 and try to reproduce the problem there. If that doesn’t work (the reproduction of the problem), the issue is isolated to the Sony TV.
