I have an i1 pro, rev D (the beamer actually) Part # 42.17.79. I had it recently recalibrate, so I know its good. I add it to the recognized probes list as i1 pro (as well as trying all the other i1's). But it never actually shows up when I go to profile. It only does the virtual probe. Not sure whats going wrong. Do I need to add a driver to windows first or something?

Thanks,
Blase

(Also have an i1 display pro coincidentally having problems, so this is not a cross post.)

What version of LightSpace do you have?

There is a 'bug' with the present release of the LTE version (not any manufacturer specific LTE version, such as from FSI, Konvision, Kroma, etc.) that incorrectly limits probes to just the i1 Display Pro.

This will be corrected in the next release.

Steve

Hi Steve,

Thanks for the quick replies.

The invoice is from 2013 and says "Full LightSpace CMS". I think it was before LTE versioning. License page shows all features activated.
Assuming I have LTE, (and I need to calibrate this week) should I roll back to the older build?

Ah - no!
With the Full version there are no issues, so the problem is elsewhere.
Do you have the probe selected within 'Discoverable Probes"?
If so, it may be a driver issue, or did you try to update the softwate without first uninstall ingredients the previous version?

Steve

The "i1 pro 1/2" probe is selected, yes. And my Display Pro is working fine. Just the i1 pro that doesn't appear.

Ok I did not uninstall 7.14 before I installed 7.15. Perhaps thats the problem?

Do i uninstall with the IPClient_uninstall? Or just delete the whole directory? I googled but couldn't find more specific instructions.

And to be clear I did not install any separate software or drivers for the probe.

Thanks!

Uninstalled via Windows 10 "settings/system/Apps & features/uninstall". Rolled back to 7.1.14. Same results.

Probe registers in "Settings/Devices/" as "eye-one . Driver is unavailable.

Thanks for reading,
Blase

It was in fact a driver issue. Removing old non-lightspace software, and installing x-rite's driver (via the iprofiler installer) solved this.

Sorry - have just got off a flight, so missed the conversation thread.

Glad all is sorted!

Steve