AVS Forum banner

1041 - 1060 of 1240 Posts

·
Registered
Joined
·
18,305 Posts
I won't be able to do the probe matching, or calibration until I get off work. Any guidance on the 2 and 21 point grayscale? This is another thing, I'm trying to do all of this in between my work schedule when I have the time, which makes it all kind of a time crunch. Thank you for the reply though, I will definitely be doing that tonight.
Probe match first.
 

·
Registered
Joined
·
5,093 Posts
Baby steps. Don't worry about 2/21 point gray scale at the moment. Just follow the directions D-Nice has given you to a "T", and report back...
 

·
Registered
Joined
·
600 Posts
The Sony need to be set to Contrast 100 to align and match the grayscale levels.
 
  • Like
Reactions: jrref

·
Registered
Joined
·
435 Posts
Ok, tried doing a quick reading again for probe matching on a break with the Luminance matching in program before read.

Red
xyY (L)XYZYuv
Reference Meter0.6451380.32861326.62552.27060226.6252.12675626.6250.4564860.523169
Active Meter0.6427020.33729327.224151.87473127.22411.61467427.22410.4461570.526827
Difference-0.0024360.008680.5991-0.3958710.5991-0.5120820.5991-0.0103290.003658
2.25% 2.25% 2.25%
Delta EdE 1976 Luv: 5.8825 | dE 1976 Lab: 0.2099 | dE 1994: 0.1802 | dE 2000: 0.2316
Green
xyY (L)XYZYuv
Reference Meter0.2964920.60346593.838946.10455193.838915.55670293.83890.1229160.562899
Active Meter0.2953080.6056696.373146.98964396.373115.7580596.37310.1220620.563271
Difference-0.0011840.0021952.53420.8850922.53420.2013482.5342-0.0008540.000372
2.7% 2.7% 2.7%
Delta EdE 1976 Luv: 2.5804 | dE 1976 Lab: 0.3729 | dE 1994: 0.2657 | dE 2000: 0.3025
Blue
xyY (L)XYZYuv
Reference Meter0.15250.0602849.6819724.492419.68197126.4315859.681970.1784460.158716
Active Meter0.1532220.062150510.152325.02885310.1523128.16910210.15230.1781980.162633
Difference0.0007220.00186650.470330.5364430.470331.7375170.47033-0.0002480.003917
4.86% 4.86% 4.86%
Delta EdE 1976 Luv: 1.5504 | dE 1976 Lab: 0.0799 | dE 1994: 0.0608 | dE 2000: 0.0595
White
xyY (L)XYZYuv
Reference Meter0.3038240.31747142.952136.80741142.952170.525656142.9520.1959530.460696
Active Meter0.3029720.323961144.264134.917328144.264166.131533144.2640.1929270.464158
Difference-0.0008520.0064911.312-1.8900821.312-4.3941231.312-0.0030260.003462
0.92% 0.92% 0.92%
Delta EdE 1976 Luv: 6.0090 | dE 1976 Lab: 0.7352 | dE 1994: 0.7352 | dE 2000: 0.9916

Still getting errors
 

·
Registered
Joined
·
18,305 Posts
Ok, tried doing a quick reading again for probe matching on a break with the Luminance matching in program before read.

Red
xyY (L)XYZYuv
Reference Meter0.6451380.32861326.62552.27060226.6252.12675626.6250.4564860.523169
Active Meter0.6427020.33729327.224151.87473127.22411.61467427.22410.4461570.526827
Difference-0.0024360.008680.5991-0.3958710.5991-0.5120820.5991-0.0103290.003658
2.25% 2.25% 2.25%
Delta EdE 1976 Luv: 5.8825 | dE 1976 Lab: 0.2099 | dE 1994: 0.1802 | dE 2000: 0.2316
Green
xyY (L)XYZYuv
Reference Meter0.2964920.60346593.838946.10455193.838915.55670293.83890.1229160.562899
Active Meter0.2953080.6056696.373146.98964396.373115.7580596.37310.1220620.563271
Difference-0.0011840.0021952.53420.8850922.53420.2013482.5342-0.0008540.000372
2.7% 2.7% 2.7%
Delta EdE 1976 Luv: 2.5804 | dE 1976 Lab: 0.3729 | dE 1994: 0.2657 | dE 2000: 0.3025
Blue
xyY (L)XYZYuv
Reference Meter0.15250.0602849.6819724.492419.68197126.4315859.681970.1784460.158716
Active Meter0.1532220.062150510.152325.02885310.1523128.16910210.15230.1781980.162633
Difference0.0007220.00186650.470330.5364430.470331.7375170.47033-0.0002480.003917
4.86% 4.86% 4.86%
Delta EdE 1976 Luv: 1.5504 | dE 1976 Lab: 0.0799 | dE 1994: 0.0608 | dE 2000: 0.0595
White
xyY (L)XYZYuv
Reference Meter0.3038240.31747142.952136.80741142.952170.525656142.9520.1959530.460696
Active Meter0.3029720.323961144.264134.917328144.264166.131533144.2640.1929270.464158
Difference-0.0008520.0064911.312-1.8900821.312-4.3941231.312-0.0030260.003462
0.92% 0.92% 0.92%
Delta EdE 1976 Luv: 6.0090 | dE 1976 Lab: 0.7352 | dE 1994: 0.7352 | dE 2000: 0.9916

Still getting errors
Did you follow the instructions I provided? Also, what exactly is this table you are posting?
 

·
Registered
Joined
·
9,575 Posts
Discussion Starter #1,046
So I shouldn't put it on DCI or REC.2020 when probe matching? I saw in other threads that the TV should be put on those to get the full spectrum of colors for REC 709
I have replyed alw
So I shouldn't put it on DCI or REC.2020 when probe matching? I saw in other threads that the TV should be put on those to get the full spectrum of colors for REC 709
You have Sony TV, so don't look what we suggest to LG OLED users.

LG doesn't have processing to wide gamut.

Sony has the most added processing when you have REC.2020 preset selected.

So for meter profiling, you will use REC.709.
 

·
Registered
Joined
·
9,575 Posts
Discussion Starter #1,048
I'm doing the probe matching in rec709 and Meter Profile Comparison, Validate Active Meter Against Reference Meter is the tool I'm using to verify, and yes, I followed your instructions
What data are you importing to that site?

Can you start by providing the required data about your meter settings/ patch generation settings / probe matching files and settings?

Please post the data I'm asking from you.

We want to help you, but you have to follow the exact procedure... we have asked you to provide the required info but you are not helping.

Sony recommends using only 20-Point when you are using DDC calibration controls.

Skip 2-Point and start 20-Point.

But don't start anything yet; it will require to confirm first if you generate correct patterns and if your meter profiling is OK.

I don't see any progress after all that help on this thread; send me all your questions by email and all data.
 

·
Registered
Joined
·
435 Posts
I'm using the bpd files generated from ColourSpace for that website to measure values. I will admit, I did not calibrate 2 point before taking probe matching readings because of time constraint on my break.
 

·
Registered
Joined
·
9,575 Posts
Discussion Starter #1,050
I'm using the bpd files generated from ColourSpace for that website to measure values. I will admit, I did not calibrate 2 point before taking probe matching readings because of time constraint on my break.
Ok, so you compare the difference of uncalibrated meter with Spectro, so the procedure is wrong.

It will always have errors, as you are not verified the actually applied correction using that method.

You are verifying the unprofiled meter compared to spectro.

It will ways have errors.

Why are you doing steps we never suggested to you?

We have posted to your how to verify your meter profiling, and it will not be required to input any data to any site.

It will require a specific procedure to make it work with ColourSpace when you are using an external site to check.


Measure that 4 color list with the profiled meter, and the i1PRO2 and then compare these 8 xyY numbers.

It will require manual entry of data to the site you want to use.
 

·
Registered
Joined
·
9,575 Posts
Discussion Starter #1,051
I know the Sony has to be the easiest. They've already set everything up for you. All you have to do is calibrate the rec709. So let me ask you guys. What is your preferred method of calibrating the 2 point and 21 point grayscale, all the boxes ticked and settings used? I want to Auto my Luma Target Nits once I get the TV to my preferred nits. This is for both 80 and 400 nits calibration. Is it easiest to leave Profile Target nits Auto box ticked? When Calibrating 2 point and 21 point grayscale, do you like to keep Chroma Only checked? I can't seem to do 2 point grayscale without ticked. Anyways, it's the 2 point and 21 point grayscale that's tripping me up. The HSL is super easy, and I can do that all day long, no problem.

Also, I'm on an LCD, not OLED.

When doing 2 point and 21 point grayscale, I'm going from high to low on both, and repeating the process to smooth out RGB differences, I'm running into problems on the high and low end, they are getting stuck, my RGB controls are going to MAX in some cases, and I'm trying to avoid that.
Don't start any calibration yet, unless its verified that your meter profiling is OK and the patch settings.

Also, any local dimming should be disabled during calibration. (and don't perform 2-Point calibration)

 

·
Registered
Joined
·
9,575 Posts
Discussion Starter #1,052
I have a question regarding the use of probe matching (4CVM).

Which is the best way to make a display profile:
1. Probe Matching = disabled in Probe Options tab & Probe Matching Active = disabled in the Graph Options tab during profiling with the colorimeter; after profiling is done set Probe Matching Active = enabled in the Graph Options tab
2. Probe Matching = enabled in Probe Options tab & Probe Matching Active = enabled in the Graph Options tab during profiling with the colorimeter

In case of (2), would setting Probe Matching Active = disabled in the Graph Options tab still allow to see the data without the correction applied?
You can do both.

The data will be saved to the profile (display data) file, when you click to save.

I prefer the 2) method.

Start with Colorimeter:

Profile Options -> Probe Matching -> Configure.

Active Probe -> New... Enter name...OK. (Reference meter NONE)

Then do the same with Spectro.

Then select colorimeter, Profile Options -> Probe Matching -> Configure.

Select @ Active Probe the colorimeter file and @ Reference Probe the spectro file.

Graph Options -> Tick to enable Probe Matching Active.

Profile the display and then Graph Options -> Profile -> Save to store the display profiling data file.
 

·
Registered
Joined
·
1,137 Posts
I'm using the bpd files generated from ColourSpace for that website to measure values. I will admit, I did not calibrate 2 point before taking probe matching readings because of time constraint on my break.
As Ted has said above, all you are doing when using the values in the BPD files is comparing the measurements recorded by the Spectro against the measurement recorded by the uncorrected colorimeter. The actual meter correction happens in the software, and is given in the readings as you take measurements.

This is why I told you 8 days ago, two very simple ways to verify your meter correction.

The first "simple" method was
The easiest way is just to take a small series of measurements with one probe, save the profile and then run the same series series with the corrected probe and compare the results of the two.
It is also probably the easiest for new users unfamiliar with the interface of ColourSpace. In fact, Ted actually expanded on this shortly after and provided more information on how to use a custom sequence to make it slightly more "automated"

The second "simple" method was
Another way would be to open two profiling windows, connect Spectro in one of them, along with the TPG, and connect the corrected probe in the other. They can read simultaneously, so you can just set both probes to read continuously (click Repeat and Measure) and set your patches with the window controlling the TPG and compare the resulting readings in real time.
And it must be reiterated
Remember, when doing such a thing that when you have applied the correction files within Probe Options, make sure you select Probe Matching Active in Graph Options

If you really want to create a meter profile verification report such as the one you have posted, then you must use the values that are recorded in the software when you take the measurements with "Probe Matching Active", which is very easily done using either of two methods given above.
 
  • Like
Reactions: Rolls-Royce

·
Registered
Joined
·
167 Posts
Just run into a ColourSpace bug: don't save your profiles with characters in them that are not valid in a Windows file name, as ColourSpace will fail to save the profile data to file. For example, don't name a profile like this: "[2020 10 08 04:33] C8 Game".

While ColourSpace is open it will pretend the profile data is saved, but close it and open it again and you will notice the profile is not listed in the list of existing user profiles. And if you browse to "%APPDATA%\Roaming\ColourSpace\ColourSpaces", you'll notice the file was not saved there, there's just a 0 byte sized "[2020 10 08 04" file.

That's how I lost all the data of a 17 cube profile...
 

·
Registered
Joined
·
9,575 Posts
Discussion Starter #1,055
Just run into a ColourSpace bug: don't save your profiles with characters in them that are not valid in a Windows file name, as ColourSpace will fail to save the profile data to file. For example, don't name a profile like this: "[2020 10 08 04:33] C8 Game".

While ColourSpace is open it will pretend the profile data is saved, but close it and open it again and you will notice the profile is not listed in the list of existing user profiles. And if you browse to "%APPDATA%\Roaming\ColourSpace\ColourSpaces", you'll notice the file was not saved there, there's just a 0 byte sized "[2020 10 08 04" file.

That's how I lost all the data of a 17 cube profile...
Hi,

All the following special characters will not be permitted to the next beta.

It has fixed already:

< (less than)
(greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)

However, to my system, I was able to save with many special characters, the file saved:



...and I was able to open it:



But Steve found something, so thanks for your bug report.
 

·
Registered
Joined
·
9,575 Posts
Discussion Starter #1,056
ColourSpace Beta 1.0.0.773 (08 October 2020)

Release Notes


Updated Klein probes Intelligent Integration operation.

Added workaround for Klein API Presets issue.

Updated protection for invalid characters in file names.

Download

Download Link or Feedback Form here. (the password is known to Beta Testers)

Installation Notes

ColourSpace Installer will completely overwrite any previously installed version, not just update it.

It will not require to un-install older releases before installing a newer version.

Update Notes

While ColourSpace is working in beta, when the users will start ColourSpace, it will not pop-up notification to inform for the availability of newer beta.

However, I will update this thread but also refresh the form page with release notes text per each beta.
 

·
Registered
Joined
·
167 Posts
Thanks Steve & Ted!

It's interesting that you were able to save the file with colons in it, for me it did not work. It doesn't work trying to rename an existing file into one that has a colon in its name either, Windows Explorer doesn't let the typed colon be added to the new name.

I managed to save a 17-sized cube after profiling the C8 this time, but I have a question.

I used a drift setting of 15, and I got this drift graph, with an irregularity near 0.4:
3044796


Is there a way to know which measured points were affected, in order to retake those measurements?

Would you advise creating a LUT with "Drift Compensation" enabled for it in the "LUT Tools" window, or not?
 

·
Registered
Joined
·
1,012 Posts
As one of the Klein owners who very insistently asked Steve to add some sort of intelligent integration feature to the K-10A in LS / CS, I was really excited to test the latest beta of CS, as it brought the new Klein API and the highly anticipated intelligent integration.

After some hour of testing, I felt like I finally have a Klein! Fast and furiously accurate! I won't annoy you with what I did and how. I will jump directly to what are my settings for accuracy and speed and what I think is the best compromise between them.

Accuracy: Max integration 5 seconds, Intelligent integration 1 NIT, Average low light OFF. It needs 9' 36" to read 252 GS points.

Speed: Max integration 0.125 seconds, Intelligent integration OFF, Average low light OFF. It needs 1' 23" to read 252 GS points.

The Genius settings (which is as accurate as the "Accuracy" one but a lot faster): Max integration 1.250 seconds, Intelligent integration OFF, Average low light OFF. It needs 2' 35" to read 252 GS points.

HERE you can see the difference on 252 GS points between the "Accuracy" and the "Genius" settings.

So thanks @Light Illusion (and Klein) for anticipating Christmas ;)
 

·
Registered
Joined
·
7,099 Posts
As one of the Klein owners who very insistently asked Steve to add some sort of intelligent integration feature to the K-10A in LS / CS, I was really excited to test the latest beta of CS, as it brought the new Klein API and the highly anticipated intelligent integration.

After some hour of testing, I felt like I finally have a Klein! Fast and furiously accurate! I won't annoy you with what I did and how. I will jump directly to what are my settings for accuracy and speed and what I think is the best compromise between them.

Accuracy: Max integration 5 seconds, Intelligent integration 1 NIT, Average low light OFF. It needs 9' 36" to read 252 GS points.

Speed: Max integration 0.125 seconds, Intelligent integration OFF, Average low light OFF. It needs 1' 23" to read 252 GS points.

The Genius settings (which is as accurate as the "Accuracy" one but a lot faster): Max integration 1.250 seconds, Intelligent integration OFF, Average low light OFF. It needs 2' 35" to read 252 GS points.

HERE you can see the difference on 252 GS points between the "Accuracy" and the "Genius" settings.

So thanks @Light Illusion (and Klein) for anticipating Christmas ;)
Miki, Thanks for the testing. At a high level can you describe how intelligent integration works? Is your Klein now a lot faster than your i1D3? :LOL:
 

·
Registered
Joined
·
1,012 Posts
Starting from the bottom: it is almost 2x FASTER than what it used to be. Before it took 6/700 ms to read a white patch, now it's about 350 ms. Intelligent Integration just tells the meter to increase the Integration time until it gets a stable reading below a threshold expressed in nits and set by the user.
To answer your question I had to take the elevator and climbed 237 steps to get on top of the highest building in Rome, no highest level possible for me, John :D
 
1041 - 1060 of 1240 Posts
Top