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

[SirMaster]

Yeah, guess they aren't continuing the Spyder5 support as that stops at firmware 3.10 now.

[David Vaughn]

Yeah, guess they aren't continuing the Spyder5 support as that stops at firmware 3.10 now.

I've confirmed this with JVC. Only the Spyder X works with the new firmware. I just ordered one tonight. Sadly, it won't be delivered until the 19th. 

[jj-34]

Nice way to increase Datacolor sales ...
Fortunately I already have a Spyder X 

[bmoney]

I've confirmed this with JVC. Only the Spyder X works with the new firmware. I just ordered one tonight. Sadly, it won't be delivered until the 19th.

will the spyderX work with the rs600 though?

[Nooj]

Hello, I would like to use Autocal without spending too much money, I already have an i1d3 but it is not autocal compatible. so i am wondering if it is useful to buy spyder x and use it only for gamma and then do 3d lut dispcal (madVR) for color in max bright off mode.

In summary will I gain something with a gamma autocal before a 3dlut dispcal? thank you

[dcchan2]

Hello, I would like to use Autocal without spending too much money, I already have an i1d3 but it is not autocal compatible. so i am wondering if it is useful to buy spyder x and use it only for gamma and then do 3d lut dispcal (madVR) for color in max bright off mode.

In summary will I gain something with a gamma autocal before a 3dlut dispcal? thank you

If you’re using a 3DLUT there’s not much point in running Autocal.  Just set the projector to use its (uncalibrated) native gamut. 

[jj-34]

Having no knowledge about 3DLut's, I guess one has to use a PCHC and Madvr to use one ?

[SirMaster]

Hello, I would like to use Autocal without spending too much money, I already have an i1d3 but it is not autocal compatible. so i am wondering if it is useful to buy spyder x and use it only for gamma and then do 3d lut dispcal (madVR) for color in max bright off mode.

In summary will I gain something with a gamma autocal before a 3dlut dispcal? thank you

There is an unofficial hack way to use the i1d3 with autocal if that’s something you might be interested in. 

[Nooj]

If you’re using a 3DLUT there’s not much point in running Autocal.  Just set the projector to use its (uncalibrated) native gamut.

ok, can we put the color temp and the color profile on native by selecting "high bright and color profile: OFF. But how do I put the Gamma on native? So Autocal does not correct the native gamma then?"

There is an unofficial hack way to use the i1d3 with autocal if that’s something you might be interested in.

With the new firmware 3.50 it is no longer possible to use Autocal v11 so it is impossible to use the i1d3 tweak for the moment. only V12 works

[SirMaster]

ok, can we put the color temp and the color profile on native by selecting "high bright and color profile: OFF. But how do I put the Gamma on native? So Autocal does not correct the native gamma then?"
With the new firmware 3.50 it is no longer possible to use Autocal v11 so it is impossible to use the i1d3 tweak for the moment. only V12 works

There are DLLs floating around for i1d3 on autocal 12 (emulating a SpyderX)

There are actually 2 out there, one using the x-rite SDK and one using ArgyIICMS. 

[dcchan2]

ok, can we put the color temp and the color profile on native by selecting "high bright and color profile: OFF. But how do I put the Gamma on native? So Autocal does not correct the native gamma then?"
With the new firmware 3.50 it is no longer possible to use Autocal v11 so it is impossible to use the i1d3 tweak for the moment. only V12 works

There is no “native gamma” per se, but the gamma calibration is tied to the colour profile and lamp power, so with colour profile OFF the corresponding gamma does not get calibrated; i.e., you will always have the gamma  droop.

[CyberPaul]

There is no “native gamma” per se, but the gamma calibration is tied to the colour profile and lamp power, so with colour profile OFF the corresponding gamma does not get calibrated; i.e., you will always have the gamma  droop.

tied to the color filter, not profile...

[dcchan2]

tied to the color filter, not profile...

There’s really no point in getting hung up with semantics.  The user can only select profiles, not colour filter directly.  Each profile uniquely determines whether the filter is on or off, so there is no confusion.

The statement is not true in the current context of answering the question of “native gamma”.  Profile:BT.709, Profile:HDR and Profile:Off all do not use the filter.  The first two get calibrated together, but Profile:Off never gets calibrated.

[CyberPaul]

Not true in the current context.  Profile:BT.709, Profile:HDR and Profile:Off all do not use the filter.  The first two get calibrated together, but Profile:Off never gets calibrated.

I don't think you will never be able to calibrate Profile OFF, as it is a non-processed profile by definition, targeted to get the most possible light for external processors adopters . The rule is always the same: what impacts gamma calibration are color filter and lamp power in any mode you put them, plus aperture for the color. This is unchanged. Simply they introduced an unprocessed profile that can't be calibrated I guess.

[SirMaster]

I don't think you will never be able to calibrate Profile OFF, as it is a non-processed profile by definition, targeted to get the most possible light for external processors adopters . The rule is always the same: what impacts gamma calibration are color filter and lamp power in any mode you put them, plus aperture for the color. This is unchanged. Simply they introduced an unprocessed profile that can't be calibrated I guess.

You can calibrate profile off manually though.

You can do white balance, custom gamma, and CMS as normal.