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

[IanW]

I also have two INIT files, how do I ensure that at least one of them is the FULL init file?

[jj-34]

Maybe with the creation date and time embedded in the file name :   
10440336_Init_2019-0817-0015.cbd = created the 17 August 2019 at 00:15 

[dcchan2]

Yeah I have calibrated the same NX projector on multiple computers before and only ever got the INIT file the first time on the first computer.

Upgrading firmwares or changing computers never produced another INIT file on subsequent autocal runs, only user mode backups for the mode I was in when I ran the autocal.

I have two INIT files for the same projector:

11440414_Init_2019-1120-1455.cbd
11440414_Init_2019-1213-0035.cbd

They are identical in size - 25280 bytes.

In the AppData folder I was able to find two corresponding logs:
11440414_HDR10_201911201455.clog (v11)
11440414_Natural_201912130035.clog (v12)

[jj-34]

I have two INIT files for the same projector:

11440414_Init_2019-1120-1455.cbd
11440414_Init_2019-1213-0035.cbd

They are identical in size - 25280 bytes.

In the AppData folder I was able to find two corresponding logs:
11440414_HDR10_201911201455.clog (v11)
11440414_Natural_201912130035.clog (v12)

There we have the proof that you can get more init files than the very initial init file ... 
I'd say the oldest one ( date in the file name ) is probably the genuine init file ( that is IF at the creation time your PC had a good clock of course ).

They are all of the same file size, but if you open one ( you can with any text editor, just be careful not to save it ) you'll see that the genuine init file has a lot of blank spare space, whereas an actual autocal one has not.

[dcchan2]

There we have the proof that you can get more init files than the very initial init file ...

There was never any doubt in my mind regarding this.

I'd say the oldest one ( date in the file name ) is probably the genuine init file.

It was previously used so I can’t be sure if the previous owner had never calibrated it.

They are all of the same file size, but if you open one ( you can with any text editor, just be careful not to save it ) you'll see that the genuine init file has a lot of blank spare space, whereas an actual autocal one has not.

As I stated previously, the two Init files have the same "appearance"; both zip to 4836 bytes, which gives an indication of the spaces contained in them.  In comparison, one of my user-generated cbd file zip to 10941 bytes, starting from the same file size of 25280 bytes. 
The bottom line, as I have been saying all along, is that it’s impossible to tell if an Init file truly contains factory calibration data, unless you're talking about someone renaming a user cbd file to Init. Not that it matters that much, as the factory calibration quickly loses its relevance once the panels start developing gamma droop and colour shift.

[SirMaster]

Yeah as long as you have properly functioning calibration meters, you should always be able to get a better autocal result than the factory calibration.

[KarlKlammer]

For those, who are still interested in using the i1 Display Pro for Autocal: the author of the original mod released a new version that follows a different approach. It uses ArgyllCMS in the background.

It can be downloaded from github:
https://github.com/scyomantion/FakeSensor

[SirMaster]

For those, who are still interested in using the i1 Display Pro for Autocal: the author of the original mod released a new version that follows a different approach. It uses ArgyllCMS in the background.

It can be downloaded from github:
https://github.com/scyomantion/FakeSensor

Spyder 4?

But autocal 11 and 12 only use spyder 5 and X. 

[KarlKlammer]

It should also work as a replacement for Spyder 5.

The functions in the dll are identical.

Spyder X is a different matter with different function and file names.

[jj-34]

It should also work as a replacement for Spyder 5.

The functions in the dll are identical.

Spyder X is a different matter with different function and file names.

OK, but with which version of Autocal ?
The spyder 4 is only supported by autocal V6 for the X5000 / X7000 family.

[KarlKlammer]

I'm not the author and just wanted to point out that there is a newer version.

I have not tested it with Autocal myself, but ran the i1test.exe that was part of the original mod. The new dll behaved like the old one.


But since I wrote a dll for a different meter (intended to replace the Spyder 5 in Autocal 11) and a friend used it with Autocal 6 without a single change in the code, I suppose that it will be the same with this i1 Display Pro dll.

[jj-34]

So I take it this new dll is only to get rid of the x-rite driver, no change about using autocal.
I had the impression that he was re-writing something similar to autocal to avoid interfering with JVC policies ?

[KarlKlammer]

Yes, this is mainly to avoid using the x-rite SDK.
I don't know if/when we will see something about the other project.

Here is a post from him in a german forum (in german )
http://www.hifi-forum.de/index.php?action=browseT&forum_id=94&thread=15592&postID=163#163

[dcchan2]

Spyder 4?

But autocal 11 and 12 only use spyder 5 and X.

I tried it using i1D3 with Autocal 7 (for Spyder5 and RS500) and that works.

[chiayc]

Hi, I am new to this forum. I have read the post about the sensor detection problem with SpyderX. I am having the same issue now. I am using a MacBook Pro with Windows 10 running in Parallels Desktop. As it doesn't have a USB-A port I use a USB-C to USB-A adapter. I successfully calibrated my JVC NX5 projector once, but strange thing is since then I have been unable to detect the SpyderX sensor, it always prompt me "Sensor can not be detected. Check again". I have tried to switch to BootCamp to run Windows 10 but same issue. I accept that it is complicated to run Windows 10 on MacBook Pro, furthermore with a USB-C. However, it intrigues me that I was able to run it successfully once! There must be something missing since the first success, but I couldn't figure out what was that. Anyone who managed to solve the issue? Appreciate any advice.