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

[jj-34]

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.

What version of autocal are you using ?

N5 with Spyder X requires Autocal V12

[chiayc]

What version of autocal are you using ?

N5 with Spyder X requires Autocal V12

Yes, I am using Autocal V12

[jj-34]

Yes, I am using Autocal V12

Autocal with the Spyder X does not require any dedicated driver as it uses the Windows generic usb one.
Plug in the spyder and check your windows device manager to see if it is there and without any yellow warning sign.

Also have you installed the Datacolor software that comes with the spyder ?   If yes remove it.

[chiayc]

Autocal with the Spyder X does not require any dedicated driver as it uses the Windows generic usb one.
Plug in the spyder and check your windows device manager to see if it is there and without any yellow warning sign.

I can see the SpyderX in the Device Manager (no yellow exclamation mark), so it should be installed ok. And SpyderX Elite software can detect the sensor. I read that there may be some conflict with the SpyderX software so I have uninstalled it. In short, the sensor is detected by Windows 10 successfully, it is just the JVC Autocal that could not detect it. 

[jj-34]

In the W10 device manager what is the driver associated to your spyder ?

Have you reloaded Windows and tried autocal since uninstalling Datacolor  ?

With Datacolor installed windows may start a Datacolor background task that grabs the spyder  so that autocal cannot use it.

[chiayc]

In the W10 device manager what is the driver associated to your spyder ?

Have you reloaded Windows and tried autocal since uninstalling Datacolor  ?

With Datacolor installed windows may start a Datacolor background task that grabs the spyder  so that autocal cannot use it.

It is winusb date 2016. I have deleted the VM and re-installed W10, I have also deleted the BootCamp and reinstalled W10, after which I omitted the SpyderX software, but still experienced the same problem. The strange thing was when I successfully ran it the first time, the SpyderX software was there, as I calibrated my monitor before moving on to projector. Now I am facing problem with or without SpyderX software.

[jj-34]

Winusb 2016 is the good driver.
But unfortunately no experience with macbooks with W10, but if it worked once it should work again

Some thoughts just in case :

- re-install autocal ? 

- Have you run another calibration software like HCFR or DisplayCal ?

- In the W10 device manager try to reload the spyder driver using the option to search in your computer then choose within a list of available drivers, is there a list of more than one driver ( like ArgyllCMS ) ? 

[chiayc]

Winusb 2016 is the good driver.
But unfortunately no experience with macbooks with W10, but if it worked once it should work again

Some thoughts just in case :

- re-install autocal ? 

- Have you run another calibration software like HCFR or DisplayCal ?

- In the W10 device manager try to reload the spyder driver using the option to search in your computer then choose within a list of available drivers, is there a list of more than one driver ( like ArgyllCMS ) ?

No, I don't have HCFR or DisplayCal, is it good idea to download these? I have tried to manually install the driver with the win7usb in SpyderX folder before I uninstalled the software. All won't solve the issue. I agree with your suspicion that something is blocking or hijacking the sensor from Autocal, unfortunately I couldn't find out which. I have also borrowed an older MacBook Pro running W10, but with USB-A port and it worked well. So it could also be the conversion of USB-A to USB-C. But strange thing is SpyderX software can detect no problem in both W10 and MacOS.

[jj-34]

For what it's worth, this is my winusb with my SpyderX :

[chiayc]

For what it's worth, this is my winusb with my SpyderX :

Thanks jj, mine is almost the same, except my W10 is 10.0.19041.1. I have just wiped out my BootCamp and re-installed W10 but no success. Couldn't understand why it only ran once and then not detectable anymore.

[jj-34]

No more clues .....  just one, borrow a PC laptop   

[chiayc]

No more clues .....  just one, borrow a PC laptop 

Thanks JJ, I will continue to investigate and post if I have any success. 

[jj-34]

As a reminder from my long ago pro time in software development and support we had a final memento when something stopped working and no issue in sight :  what has changed hardware and software since last time it worked ?  Then made a list and put back one step at a time till it worked again, usually we did find the cure .....  

[chiayc]

As a reminder from my long ago pro time in software development and support we had a final memento when something stopped working and no issue in sight :  what has changed hardware and software since last time it worked ?  Then made a list and put back one step at a time till it worked again, usually we did find the cure ..... 

JJ, thanks for the good advice. Will try, but slim chance as I don’t remember changing anything, both software and hardware. It just refused to work after the first calibration, *sigh*

[chiayc]

As a reminder from my long ago pro time in software development and support we had a final memento when something stopped working and no issue in sight :  what has changed hardware and software since last time it worked ?  Then made a list and put back one step at a time till it worked again, usually we did find the cure ..... 

Something interesting to post here. I took your advice and tried to remember all events from the beginning. I recollected that I have initially installed W10 Home on my VM in Parallels Desktop, I then re-installed W10 Pro, but as I wasn't familiar with PD, I installed from the setup.exe directly instead of using the menu in PD. That installed the W10 Pro alright but with screen resolution of 800x600 and no shared folders with Mac. That was the time I managed to run the JVC Autocal. So today I repeated the same steps and got to the 800x600 state of W10 Pro, and JVC Autocal ran successfully! However, when I changed the screen resolution to higher, it stopped working, even after I changed back to 800x600. Very weird behaviour.