JVC Autocal Software V12 calibration for 2019 RS1000/RS2000/RS3000/NX5/NX7/NX9

[TCramer]

To get started with the gamma editor, set your JVC to Custom1 and the correction value to Import.

Now when you select Custom1 in the gamma editor in autocal, you will have a real-time adjustment of 12 points.

The points I believe (by memory) are 5, 10, 15, 20, 30, 40, 50, 60, 70, 80, 90, 95.

So in your pattern generator or pattern source, bring up the appropriate matching white level pattern for the point you are working on, and then you can adjust each RGB color individually in autocal for that point and also move all 3 points together to manipulate the gamma.  The points in between will be smoothed between the points you are modifying.

The benefit is you have many more points than 2 to adjust, and you can raise and lower them without worry of messing with your black floor and contrast ratio.

I'll give this a try when a get chance.  Can you do the same for HDR?  That was all over the place and I made major RGB changes which apparently I should not have done.  

Attached is before and after and the auto-cal was somewhat in between, but with overly warm.  The auto-cal whitepoint was barely above 6200 if I recall right.  Red and Green were too high and blue was too low, that's why the RG gain was reduced so much.  

Gain Red: -5
Gain Green: -11
Gain Blue: 0
Offset Red: -5
Offset Green: 8
Offset Blue - 10

[SirMaster]

I'll give this a try when a get chance.  Can you do the same for HDR?  That was all over the place and I made major RGB changes which apparently I should not have done. 

Attached is before and after and the auto-cal was somewhat in between, but with overly warm.  The auto-cal whitepoint was barely above 6200 if I recall right.  Red and Green were too high and blue was too low, that's why the RG gain was reduced so much. 

Gain Red: -5
Gain Green: -11
Gain Blue: 0
Offset Red: -5
Offset Green: 8
Offset Blue - 10

You can't really do any calibration for HDR Frame Adapt other than autocal.  Everything is locked in Frame Adapt mode.

You can calibrate HDR10 mode, but I don't think it's worth it as Frame Adapt is just so much better in respect to tone mapping than HDR10 mode.

I am very surprised by your measurements after autocal.  After autocal my white balance is under 1.5dE across the board (50% and 100% color temps are less than 50 off 6500K) and doesn't require any RGB gain adjustments and only if I am being super picky a teeny tiny bit of tweaking with the 12 point gamma editor if I want it all under 1dE.

[TCramer]

You can't really do any calibration for HDR Frame Adapt other than autocal.  Everything is locked in Frame Adapt mode.

You can calibrate HDR10 mode, but I don't think it's worth it as Frame Adapt is just so much better in respect to tone mapping than HDR10 mode.

I am very surprised by your measurements after autocal.  After autocal my white balance is under 1.5dE across the board (50% and 100% color temps are less than 50 off 6500K) and doesn't require any RGB gain adjustments and only if I am being super picky a teeny tiny bit of tweaking with the 12 point gamma editor if I want it all under 1dE.

Good to know - so calibrating BT2020, HDR Color Temp or HDR (PQ) gamma manually does not impact Frame Adapt.  But autocal of those modes in a user mode other than Frame Adapt does apply to Frame Adapt.  Is that what you're saying?

[SirMaster]

Good to know - so calibrating BT2020, HDR Color Temp or HDR (PQ) gamma manually does not impact Frame Adapt.  But autocal of those modes in a user mode other than Frame Adapt does apply to Frame Adapt.  Is that what you're saying?

Yeah, you've got it.

[TCramer]

Yeah, you've got it.

Now I'm even more mixed up here.  I did the gamma correction as you suggested in the autocal module with a target of 2.3 and things were beautiful.  Then I went back about 15 minutes later and everything was running very cool, so I don't know what's going on.  Note that the projector had been on an hour before doing the initial correction so that shouldn't be an issue.  All settings were unchanged.  

First picture shows greyscale tracking after autocal then after doing the RGB Gamma corrections.  Then the second picture shows checking the exact same thing 15 minutes later.  The gamma changes should not effect a 100% white pattern right?  I literally had that at even 100% RGB across the board, same for 90% and 80% and then it changed.

For what it's worth, I'm using the Spyder X corrected to the i1 Pro2 in Chromapure for these readings.

[SirMaster]

Now I'm even more mixed up here.  I did the gamma correction as you suggested in the autocal module with a target of 2.3 and things were beautiful.  Then I went back about 15 minutes later and everything was running very cool, so I don't know what's going on.  Note that the projector had been on an hour before doing the initial correction so that shouldn't be an issue.  All settings were unchanged. 

First picture shows greyscale tracking after autocal then after doing the RGB Gamma corrections.  Then the second picture shows checking the exact same thing 15 minutes later.  The gamma changes should not effect a 100% white pattern right?  I literally had that at even 100% RGB across the board, same for 90% and 80% and then it changed.

For what it's worth, I'm using the Spyder X corrected to the i1 Pro2 in Chromapure for these readings.

Correct that the gamma editor cannot affect 100% white.

If you saw changes to your measurement after 15 minutes than something has to have drifted.  Either the projector drifted or the meter drifted or the meter placement changed or something of that nature.

I have noticed for example that when I turn on high altitude mode on my NX5, the white balance drifts massively, like more than 5dE just a few minutes after the fan speeds up from the high altitude mode due to the temperature change in the projector.

I understand that you aren't changing anything, but I would have to say something is drifting somewhere, somehow.

My NX5 does not seem to drift in my environment nor does my i1D3 meter at least not by much over my sometimes multi hour calibration sessions and I always warm my projector up for somewhere between 30-60 min before I start.

The meters also need to be warmed up too for at least as long so keep them plugged in and warm during your session.

Maybe try making a new correction for the Spyder5 and see how that compares.

All I can suggest to try is if you see it change in 15 minutes, how about start interactively measuring white with your Spyder5 after you dial it all in, and just watch the live reading over 15-30 minutes.  See if it slowly drifts.

I mean you are sure you saved your custom gamma curve after and kept the projector in custom# and correction import right?

In order to use your calibration you must have your User mode set to your Custom gamma slot and you must have your correction value set to import in order for it to use your custom autocal curve.

[TCramer]

Correct that the gamma editor cannot affect 100% white.

If you saw changes to your measurement after 15 minutes than something has to have drifted.  Either the projector drifted or the meter drifted or the meter placement changed or something of that nature.

I have noticed for example that when I turn on high altitude mode on my NX5, the white balance drifts massively, like more than 5dE just a few minutes after the fan speeds up from the high altitude mode due to the temperature change in the projector.

I understand that you aren't changing anything, but I would have to say something is drifting somewhere, somehow.

My NX5 does not seem to drift in my environment nor does my i1D3 meter at least not by much over my sometimes multi hour calibration sessions and I always warm my projector up for somewhere between 30-60 min before I start.

The meters also need to be warmed up too for at least as long so keep them plugged in and warm during your session.

Maybe try making a new correction for the Spyder5 and see how that compares.

All I can suggest to try is if you see it change in 15 minutes, how about start interactively measuring white with your Spyder5 after you dial it all in, and just watch the live reading over 15-30 minutes.  See if it slowly drifts.

I mean you are sure you saved your custom gamma curve after and kept the projector in custom# and correction import right?

In order to use your calibration you must have your User mode set to your Custom gamma slot and you must have your correction value set to import in order for it to use your custom autocal curve.

I'll try again tonight but the projector had been on over an hour and the Spyder X had been plugged in equally as long and not moved at all.  No projector settings were changed and I am indeed using custom gamma and import. 

I did save it - do you need to import that saved gamma file or should it already be applied?  I did the import but figured it would be setting the same, and didn't notice a difference.

Regardless, thanks for the help here, I really appreciate it.  And btw, I did auto-call on the RS1000 and the after auto-cal results were good enough I barely tweaked anything and didn't have these issues.  It just seems very odd the troubles I'm having with this unit.

[SirMaster]

I did save it - do you need to import that saved gamma file or should it already be applied?  I did the import but figured it would be setting the same, and didn't notice a difference.

You don’t have to import it after saving or anything like that. 

Since you are editing it live, when you are done it should just stay applied to that slot. 

Saving it is just useful if you want to change it and restore back to that saved state later. 

[TCramer]

You don’t have to import it after saving or anything like that.

Since you are editing it live, when you are done it should just stay applied to that slot.

Saving it is just useful if you want to change it and restore back to that saved state later.

Last thought - I wonder if the Spyder X reading off the screen is throwing off the reliability of the color balance versus the 5 reading off the lens.  I'll have to look back and see what Manni said about that (I've ready through his guide 3 times, you'd think I'd know this).

[jj-34]

The spyder 5 does not take the screen into account.
I had the 5 and X and I1Pro2 simultaneously and made a correction matrix of both the 5 and X against the I1Pro2, and the corrections of the X were a lot less than those that the 5 required.

[TCramer]

Alright, I'm giving up on the white balance/gamma deal.  I re-did it today and it remained closer, not perfect but closer.  All Delta Es stayed under 1 down to 40% and down to 20% were under 3. 

To the Frame Adapt HDR question, here is what the primary and saturation gamuts look like for color.  These are taken in FA mode, while the color calibration was taken in a user mode with BT2020 (same lamp and iris settings).  Does this look typical for FA, or should I expect better?

[den110]

Not sure what happened, but for some reason my efi es 2000 is not being detected by autocal.  It last worked fine back in dec 2019 when I last did a color autocal.  The driver is 2.40.0.1315 August 21 2006 and it says the device is working fine.  But when I click on the icon in autocal the device lights flash for a second and I get the error "cannot detect the sensor"  Shouldn't the device lights turn on when I plug it into the USB port?  Or when the device is selected in autocal?  Tried searching online for a better driver, but windows says thats the best driver available.  Am I doing something wrong?  Tried restarting laptop, removing and adding back device, nothing..... please help.

[Jwb2]

I have to click the little side button on my unit when it first flashes for it to work. Have you tried that yet?

[den110]

Yeah, tried that.  did nothing...it would flash white for a second then red for probably half a second then nothing.

[den110]

Stupid me... I had the white window closed on the tile when I set the es2000 down on it to calibrate.  now it works...