The Official ChromaPure thread - Page 84

Originally Posted by TomHuffman

They recently added a new custom color command that we tried out and just didn't implement correctly. We've now fixed it and will release in a day or two.

Originally Posted by TomHuffman

They recently added a new custom color command that we tried out and just didn't implement correctly. We've now fixed it and will release in a day or two.

Originally Posted by Citation4444

I'm confused. Who had the problem? Lumagen didn't implement the custom color command correctly? Or, Chromapure didn't implement correctly its use of the custom color command?

Originally Posted by wmwilker

I don't know the answer to this but Lumagen did release a new firmware update.

Originally Posted by Citation4444

I'm confused. Who had the problem? Lumagen didn't implement the custom color command correctly? Or, Chromapure didn't implement correctly its use of the custom color command?

Originally Posted by visca blaugrana

a while back I talked to you about the ACM module and the option to ,for the saturation module to use different amplitude levels, and for the amplitude module to use different saturation levels (without having to make new base readings).

is this the plan to introduce this as a v2.x release or as a 3.x release

Originally Posted by TomHuffman

If you have 50% intensity test patterns for 75%, 50%, and 25% levels of saturation, then the base readings would have to be at 50% intensity also. However, in that case you would have to make a separate set of readings to check the amplitude scale using 100% as the base readings.

Originally Posted by sotti

If you adjusts your targets based on your 50% reading, everything will be wrong, you'll have to recalculate everything.

Originally Posted by TomHuffman

No idea what you are talking about. The saturation targets don't change when the intensity changes. As long as the intensity is the same for all of the test patterns, including reference white, then relative luminance will remain unchanged, and this is what is used for dE calculation.

Originally Posted by sotti

The luminance is based off of gamma. If you change your target luminance from the 50% reading, then you've changed the gamma. Now you've got to go recalculate your target triplets to get the same x,y or modify your x,y.

Either way you've got to recalc everything.

Originally Posted by MaDBeN

Looking to run a calibration in the next couple of days I have downloaded the latest lumagen firmware am I all good to go or are we still waiting for a chromapure update to address the color command

Originally Posted by anta1974

ChromaPure 2.2.12 Release Notes
The 75% of Rec 709 option in the Color Management module was broken. This has been fixed.

That was broken?

Used as a module with a broken before???

How much is wrong?

Originally Posted by anta1974

Tom!
Why does not match the data in conversion utility (chromapure) and ΔE, LSH, and RGB Analysis (your site).
example:
Red
0.641-measure
0.3245-measure
26.3238-measure
0.64-reference
0.33-reference
29.5785-reference

Conversion utility deWeb.xls
CIELUV 30.6 6.4
CIE94 13.8 3.1
CIELAB 30.7 5.9
CIEDE2000 3.9 3.2
H -1.3% -1.3%
S 2.1% 2.1%
L -4.0% -4.9%

Why???

Originally Posted by TomHuffman

Just uploaded a new build tonight that fixes this. Since the change is so small, I kept the version at 2.2.13. Note: This update only affects the 75% of Rec. 709 gamut in Color Management when using the Lumagen as a test pattern generator.

Originally Posted by flint350

However, when I tried to use the Rec 709 75% - I do NOT have Lumagen or other processor in the chain - I got an error message ("unhandled exception error") in the Color Management module. It occurs, will allow the "continue" button to proceed after the error, then go to the next color and the error re-appears on trying to measure each color.

Originally Posted by TomHuffman

You need to provide four pieces of additional information.
1. When you get the Unhandled Exception message, click on Details. What does it say?
2. What are you using for test patterns?
3. Do you have "Enable Signal Generator Support" checked in Options, Signal Generators?
4. Did you download and install the latest build that I uploaded Tuesday?

Originally Posted by flint350

1.It's a long message, with "Object reference not set to an instance of an object" on the main window. The following is the 1st part of the error, showing the "exception text". I am not including the rest here, but will gladly send it to you if you wish (all the modules, etc).

Originally Posted by flint350

1.It's a long message, with "Object reference not set to an instance of an object" on the main window. The following is the 1st part of the error, showing the "exception text". I am not including the rest here, but will gladly send it to you if you wish (all the modules, etc).


************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at ChromaPure.Controls.Calibration.ColorManagementControl.Color RadioButton_CheckedChanged1(Object sender, EventArgs e)
at System.Windows.Forms.RadioButton.OnCheckedChanged(EventArgs e)
at System.Windows.Forms.RadioButton.set_Checked(Boolean value)
at ChromaPure.Controls.Calibration.ColorManagementControl.btnMe asure_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(M essage& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Mes sage& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


2. Test Patterns are from the AVS HD - I have done other cals, everything the same, except using REC 709 %100 - it only occurs at REC 709 75%

3. None of the Signal Generator Options are enabled, including Built In.

4. Yes, when I read your post on it, I updated. That was what led me to try the Rec 709 75% in the first place, to see if it had different results from my 100% tries. That's when I got the error.

Originally Posted by rurika

Just got iScan DUO and here is my result

6.jpg

I used CIE94 dE method and Rec709 Gamut.

Any advice for this ?

Thanks