Hi Steve, in reply to both above..
Steve:
1 - a 33% patch will be too large for an LG OLED
Go with a patch size that is as small as possisble!
33% seems to be fine based on my tests. (Using your greyscale method to determine patch size) When the luminance is throttled down below 130cd, the display driver stops throttling based on patch scale. So we're good there.
Steve:
2 - a 15 min time difference between when the probe measurements were made for the probe matching to too long. They need to be done back to back.
Warm up the probe with a different USB port if needed.
Ok. Even if the offsets aren't great, wouldn't that just affect the overall accuracy to the primaries? The problem I'm having is the bad greyscale.
Steve:
3 - What do you mean 'Calibration settings: manual', and why 'Burst' - can you not use AIO?
(If you cannot use AIO you have the earlier i1D3 probe, and that 'could' be an issue?)
Calibration settings: generic CMS (essentially default)
I have earlier i1d3 which doesn't support AIO, so you told me to use burst with an OLED.
Steve:
4 - if the 'Relax' filter is causing issue that suggests you really do have an underlying problem.
"Smooth" filter is problematic, not relax. Though relax filter doesn't create better results in greyscale. Just different ones.
Steve:
Using a value of '10' for drift, so a drift patch is inserted every 10 frames, is way to short a duration!
A value of around 100, or even higher for a display such as the LG OLED that suffers high-frequency instability would be a lot better.
Sorry thats an older screen cap. Since then I adjusted to 100.
Steve:
The 'Matrix' screen grab also shows you are using an integration tike of just 0.25 - the smallest setting.
As has been said before, that needs to be a lot longer for OLEDs when using the i1D3!.
Yes sorry its the older screen cap again. Currently using 2 seconds.
Steve:
You may also need a small amount of Extra Delay Time as those displays can take a short while to 'stabilise' in-between patch changes.
Ok I will try that as well.