Well done with the patchset,hard to fault the pq
Hi,Did a new 21^3 profiling of the screen,seems like i am missing something out due to the time it took (before around 3.05 and now 3:39) thought the new klein api was to improve the speed.
Klein settings i used:
It's a better idea to use the suggested settings as per the LG guide.Hi Ted, thank you for the detailed answer.
I used drift 15 because I wanted to make sure the patch sequence I made was good enough.
OLED has that effect, but you can notice it when you perform manual calibration, but only when you keep displaying the same pattern to the screen and adjusting RGB balance TV controls in real-time.I noticed in the past the TV having low luminosity for a while just to suddenly become brighter later, so maybe this is what happened here. Maybe my sequence has a longer series of dark patches and it made the TV enter into that low brightness mode.
It will 'pause' both probes (or one probe) and the patch if the PC is busy.I also noticed that ColourSpace sometimes "hangs", but I don't think this is what happened here. For example, if you have two profile windows open, and you do measurements in one, while you start a i1Pro2 calibration in the other, the patch display in the first window halts until the i1Pro2 calibration is done - this is when using the ColourSpace internal pattern generator.
I will look in the measurements file and try to figure out what is the problematic area, as you suggested. Thanks!
Hi Wayne,Hi Ted,
This is a picture showing my profile run, where I suspect my meter settings - due to the sizer/number of tangents.
View attachment 3046140
Could you clarify the 1.5secs you refer to in your quote? My settings are shown, with the meter attached....but not all options are available. Are he other settings corect?
Its a Rev A.02 - and a Projector.
View attachment 3046137
ColourSpace/LightSpace uses the same logic in the numbering of color patches and drift patches.@Ted, I identified the drift measurement with the problem.
It's the drift frame 2193. But I also noticed there is a patch frame 2193. What is the relationship between this patch frame and the drift frame with the same number?
As a side-note, ColourSpace said that it showed 4977 patch frames + 332 drift frames, for a total of 5309 frames.
Please don't remove the frames, do as I suggested, edit, and paste valid data to that specific problematic frame.The previous drift frames had good values (the previous drift frame number was 2177 and the next was 2209), and I'm thinking of removing from the measurements file all the frame patches between 2177 and 2209 as well as the drift frame 2193, instead of doing what you said, just to be safe. Does that make sense?
Please send me an email to forward you the optimized LG OLED patchsets for pre-roll/profile/verification.Excellent,the patch set i used is the sofs7 preroll 1000p-profile 21*3-verification 1000p set,guess those was made for 2018 oled,maybe the later patchset 17*3 is better to use even if it has less points?
Thanks,but i am already using them ted with the 17*3 charts,before i used the sofs7 21*3 but seems unnecessary now 🤓Please send me an email to forward you the optimized LG OLED patchsets for pre-roll/profile/verification.
All these are available inside the ColourSpace LG Guides zip.
Thanks for posting this. I referred to it a couple of weeks ago, and the picture included in the Guide for i1Display Pro is very misleading though.Hello people,
I sincerely invite you guys to have a look at it, you won't regret it!
I've just been directed here by another user (we do not follow discussion outside of our own forums).I agree the new guide looks good though, I just lost confidence it will always be correct, and hence checking here is still worth it.
hi Ted, I tried your settings for my Rev A iD3 Pro, and the Low Light Average option (without Inteligent integration) refused to work. There was an error, but I didn’t get a screen grab. Something about my meter not having that option? I’ll try and double check what it was.....I moved on and ran another profile (15^3) and it took 6hr20m.Hi Wayne,
I will need the profile file to have a complete idea of what is happening.
I can see that projector has some active processing, but I need a full file and more details about the pre-calibration you have performed.
For REV.A meter and projector, BURST mode, 1.5 sec integration time, no intelligent integrator, enable low light average.
Hi Steve,But, this comment really needs a reply, as the poster has totally missed the reality of the guides (and using ColourSpace is general), and how such probe setting MUST be defined by the user.
There are NO SET VALUES at all.
Different display/probe/tpgs/signal path combinations will require different settings.
That's an error when trying to use the AIO with a Rev.A meter usually. Are you sure you used Burst mode?hi Ted, I tried your settings for my Rev A iD3 Pro, and the Low Light Average option (without Inteligent integration) refused to work. There was an error, but I didn’t get a screen grab. Something about my meter not having that option? I’ll try and double check what it was.....
Ted will need to confirm this, but I believe he has added and renamed the specific patch sequences to the guide so that users can easier understand which ones to use. In this case there would be at least a "Profiling" and "Verification" sequence, and possibly a "Pre-Roll" sequence too. Each would be self explanatory due to the naming of the sequence.The patchset we need to load in custom sequences is "profiling.csv" which came with guides?
How long approximately it takes for the process to finish (i1d pro , settings as written in the guide)?
I haven't tested this myself, but I guess that if the HDMI Override menu works as intended, then theoretically it could work. You can use UHD Rec2020 and modify the target to 2.2 Gamma.2. Can I do the 2pt calibration for HDR with PGenerator using CX HDMI override? I used HDMI Override menu to set the TV to ST2084 ,DCI P3 D65 with MaxCLL - 1000 MaxFALL - 400 as recommended in PGenerator thread for HD Fury . The patch scale I set to 16-235 in CS and Target Gamut sRGB with 2.2 gamma. Is it ok ?
I guess the question kind of answers itself. Remember that with the instability of WOLED in general, especially at high luminance values, then it is very difficult to get repeatable measurements in HDR mode. So slight variances can always occur in HDR, even using a reference external pattern generator from one minute to the next.* I had very close results using iTPG . I did a test after calibrating as I mentioned above , then I played HDR video and enabled iTPG via Device Control and checked the grayscale - had almost the same result as with HDMI OVerride menu setting + PGenerator
You can verify PQ EOTF tracking (Grey Only). Colours will not track correctly using the standard Primary and Secondary patch sequence due to reduced peak luminance, tone mapping, loss of colour volume with WOLED at high luminance, among other things. @ConnecTEDDD will probably explain this in more detail when he has some more time and will possibly provide a solution for LG OLED users.3. For varifying HDR I go to characterization tab and run PRIMARY&Secondary?
Try a different USB thumb drive. Some have reported this behaviour in the past and simply using a different drive solved the issue. While not essential, I have found smaller drives (16GB or less) formatted to FAT32 with absolutely nothing else on the drive but the Configuration file to work more consistently. Sometimes having another drive plugged into another USB port of the TV can block it too.4. I did DV calibration and I can't upload the .txt file to my CX as instructed in the guide. I tried formatting the usb to FAT32 and NTFS and still it doesn't ask me to upload the config once I run DoVi video