Posts by csadoian

Quote from blinkmxq

The display calibration "issue" you are seeing is from fractional and integer frame rates switching to the correct refresh rate (so 60.0hz and 59.97hz function correctly now for example). Up until very recently, this wasn't working correctly (ty kszaq!).

However each refresh rate has separate calibration profiles, so calibration must be done for each potential refresh rate. I'm not sure if in the GUI you have the ability to switch between 59.97hz and 60hz for instance, so if not there is a bug there. If so, I wouldn't consider this a bug.

I recommend you leave adjust display refresh rate enabled, and calibrate for each refresh rate in display settings. If you can't select between 59.97 and 60 for instance, you can play one of the fractional 59.97 clips that is "resetting" as you put it, and then while playing hit the back button and calibrate in settings. Do this each time your calibration "resets," and eventually you should have saved calibration for each mode.

I'm sorry I don't have a box in front of me to check the options, but this should work for you.

I don't have the image loaded up on my Nexbox at the moment, but what happened to me was that I calibrated my screen at 1080p 60hz and then exited back to the menu. After that I chose REBOOT from the Kodi menu. When it came back up, the screen was all messed up again, having lost the calibrating I did moments before. I did this twice and both times it did not save the calibration. I never played any video, so the screen should have stayed at the same refresh rate after each reboot and use the calibration settings that I had done originally.

When I have a chance tomorrow I will put the image back in my box and play around a little more with it.

Chuck

Quote from richdtv

Does anyone has issues with video calibration resetting? I am on 8.01e and tried in system, display. Also tried to calibrate the overscan when playing a movie but it did not help. went back in settings, did the calibration again, reboot kodi thinking that settings would be saved but no luck.

See my post above yours ...

Settings/Player the option "Adjust display refresh Rate" needed to be turned off. It fixed the issue on my Nexbox.

Chuck
[hr]

Ok, my mistake. I rebooted Kodi and the calibration settings were not saved. Definitely a problem here.

Chuck

Using LibreELEC on a Nexbox A95X 2GB/8GB box.

I was testing 8.0.1d and noted some minor freezing when watching an OTA TV channel from my NextPVR setup. I have two Silicon Dust devices, one is the HDHomeRun Connect 2 tuner OTA, the other is a HDHomeRun Prime 3 tuner cable using Comcast. The freezing occurred only when using the Connect on OTA channels. Didn't see it when tuned to a cable station using the Prime.

So today I switched to 8.0.1e and I don't see any freezing, but the display is not acting correctly. I normally feed the Nexbox into a computer monitor at 1920x1080p, and I used the video calibration to move things around to make it look correct. In player settings I also set it to minimize black bars at 20%. This has always worked fine on my setup. However after I loaded up 8.0.1e and I switch to a TV channel the display momentarily blinks and then looses the custom calibration I had set (image is very large and shifted to the left). The video looks normal for a few seconds, then after the screen blinks it's obvious it's ignoring my custom settings. When I exit the TV channel the Kodi menu returns and everything looks fine.

The loss of custom calibration occurs regardless of the native resolution of the TV channel I am watching.

Ok, more info ... it's not just the TV, it's even doing it on Movies and TV shows I have stored and playback using Kodi. Must be something in the player that's causing the issue. In addition, when I switched to 720p resolution it does the same thing ... it goes to a large image shifted off to the left.

I will roll back to a previous version for the time being.

Edit: Ok, sorry, false alarm. For some reason in Settings/Player the option "Adjust display refresh Rate" needed to be turned off. It was set to "On Start/Stop" and that never made any difference in the past. It does now.

Thanks,

Chuck