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

[David Vaughn]

USB 3.0 ports (blue plastic inserts) put out more power for devices than USB 2.0 ports (white plastic inserts).

Phil, I wonder if too much power could be a problem? 

[bmoney]

USB 3.0 ports (blue plastic inserts) put out more power for devices than USB 2.0 ports (white plastic inserts).

This is great info and prob why I couldn’t get my spyder5 to work

[Philnick]

Phil, I wonder if too much power could be a problem?

I always use a USB 3.0 port on my laptop to connect my Spyder X and EFI ES-2000 (the OEM version of the i1Pro2).

It's the same 5 volts as USB 2.0, it just has more current (amps) available to it if needed by the external device. The amount of power drawn is controlled by the device connected to it - unless there isn't enough power available from the port - at which point the external device can't function and you get an error message like "not connected."

You're less likely to get that error message with a USB 3 port than with a USB 2 port.

[Philnick]

This is great info and prob why I couldn't get my spyder5 to work

If using a laptop with only 2.0 jacks, a powered 3.0 hub (port replicator) with its own AC adapter, plugged into a 2.0 jack could get you 3.0 power reserves on its output jacks (though still with 2.0 speed).

[Philnick]

Correction: USB 2.0 jacks' plastic insert is black, not white! (White signifies USB 1.0.)

Blue is, however, the color used to identify a 3.0 jack.

[Philnick]

Phil, I wonder if too much power could be a problem?

Dave, let me geek out for a moment in giving you a fuller answer.
 
 Current (in amps) = Voltage divided by Resistance (in ohms)
 
        and 
 
 Power (in watts) = Voltage times Current
 
Since the two jacks (USB 2.0 and 3.0) present the same 5 volts, the amount of power drawn is based on the resistance of the load (the device you plug into it). The lower the resistance of the load, the more current can flow, drawing more power.
 
 That's why "shorting out" a power connection (i.e. connecting a wire - which has nearly zero resistance), is dangerous: it draws all the power available, tripping a breaker or blowing a fuse (in the best case), or burning things out (in the worst case).

So it's actually more dangerous to plug a high-power (low resistance) device into a 2.0 jack than a low-power (high resistance) device into a 3.0 jack. If you're lucky, the high power device simply won't get enough power and won't work. If you're unlucky, it'll pull more power than the 2.0 jack is designed to give and either flip a breaker, or blow a fuse or internal circuit in the laptop.

[Big Ern]

Thanks to_shine, glad to hear you were able to get things working. 

I was actually able to get the calibration to work once (using quality mode), but then every subsequent attempt has crashed with the "connection" error, under normal and fast mode.  Interestingly, the calibration is now crashing very early on, during the initial log just after it measures yellow, whereas it was previously crashing much later.

I've tried zooming in as far as possible, but get the same error.  I'm trying to calibrate the SDR, with Natural picture mode, low lamp.  I'm projecting onto a Stewart Firehawk G5 screen, 123", from about 16' away.  My room is semi-light controlled, but with light colored walls and a white ceiling.  I'm not really sure what levers I have to increase brightness besides setting the lamp to high.

I have the same problem using SpyderX on a Surface Pro 2 running Windows 10.  Calibrating gamma with the SpyderX crashes really early in the process doing the log section or sometimes at the beginning of the 1st 20 step run.  Color calibration with the i1 Pro2 still works normally.  I had the screen zoomed as small as it would go.  Thankfully I didn't uninstall the prior version 12.0 of the Autocal software and I could complete the gamma calibration with that version.  I think it's bad programming or driver issues on this version.  If you go to the download section of the JVC website you can still get the old version if you change the end of the url to /JVC_PJ_Calibration12_en_v1_00.zip.

[dcchan2]

Thank you for the tip!

No, I wasn't aware that you could change the brightness setting used during calibration (apart from lamp mode and aperture setting). Just to be sure about this, how do you set brightness for the calibration?

Concerning the error message, I was able to run through both red and green gamma measurements even though the two first measurement steps produced 0 values (I used the 20 step "normal" measurement). For the blue gamma, however, the error message pops up. Is this expected? Do all three colors need to have measured zero in one or more steps before giving an error?





 

That was just one possible explanation; v1.1 is relatively new so the exact cause of the error is still somewhat speculative. Regardless, if there are two readings as 0 then the gamma calibration result won’t be valid. You’ll likely get colour tints in the dark tones. 

[dcchan2]

I have the same problem using SpyderX on a Surface Pro 2 running Windows 10.  Calibrating gamma with the SpyderX crashes really early in the process doing the log section or sometimes at the beginning of the 1st 20 step run.  Color calibration with the i1 Pro2 still works normally.  I had the screen zoomed as small as it would go.  Thankfully I didn't uninstall the prior version 12.0 of the Autocal software and I could complete the gamma calibration with that version.  I think it's bad programming or driver issues on this version.  If you go to the download section of the JVC website you can still get the old version if you change the end of the url to /JVC_PJ_Calibration12_en_v1_00.zip.

So Autocal 12 v1.0 still works, with FW3.5? I thought v1.1 is required for the new firmware.

[Big Ern]

Autocal V12 1.00 still worked fine for me on Firmware v3.50.  Obviously it doesn't have all the new menus like version 1.1, but it seems like for doing Gamma it is ok.

After more testing I discovered the measurements causing it to error out are close to 0 but not actually 0 when comparing version 1 to 1.1. I was still able to capture an excellent 33 step gamma curve with version 1. 

[Blu1080]

That's strange some people are having problems. I am running Autocal v12 1.10 with a Surface Pro 7, Spyder X & a 9' USB extension. I've ran several SDR & HDR calibrations without any issues.

[madmax1205]

Hello

after a gamma and color calibration in autocal in V12 1.1 
I have these coordinates for the colors
I do not understand what they correspond to impossible 
to find these coordinates in the colorhcfr software
is it just the offset (correction of the points) to arrive at the standard
 because I see that the Z of red is at 0 is this normal? 
thank you

[dcchan2]

Hello

after a gamma and color calibration in autocal in V12 1.1 
I have these coordinates for the colors
I do not understand what they correspond to impossible 
to find these coordinates in the colorhcfr software
is it just the offset (correction of the points) to arrive at the standard
 because I see that the Z of red is at 0 is this normal? 
thank you

XYZ are “raw” measurements. You can switch HCFR to those units as well.
The calibration log presents the information in the more common xyY and CIE diagram.

[madmax1205]

Hello
no these measurements are not in hcfr even by changing the xyz, 
moreover my Red is at 0 so
 I don't think that these are values ​​but rather a correction compared 
to the standard values, no?
of course the coordonates of color temp is in the hcfr but not a color signal level ? 

[madmax1205]

my pdf file report hcfr with just u autocal v12 1.1 with the i1d3
 without any editing in user mode 1 2.2 6500 rec 709 impression anyway

I just don't understand the info from my first screenshot which has Byzaric coordinates
 and which appear in the screens during measurement and the red has a Z at 0 
so for me it's just a catching up of luminance standards or others because my curves 
after this calibration are practically perfect until the colorchecker
 without touching up the menu of the jvc n5