The i1 Display Pro is supposed to be more accurate with less variation from calibration unit to calibration unit.

I made the jump from the i1 Display 2 to the Pro and it was a nice upgrade. If your i1 Display 2 is working great and making good profiles, then there's probably not going to be a night/day difference on screen. My unit was getting old and tired though, so I noticed a big improvement.

Brain fart on a Sunday but I can’t recall if that display is wide gamut or not (I think it is). If so, the newer instrument with it’s newer filters will most likely be more ‘accurate’ in hitting the white point you ask for. Not that futzing around with the older unit to get a WP that produces a match isn’t possible.

The i1 Display Pro is supposed to be more accurate with less variation from calibration unit to calibration unit.

I made the jump from the i1 Display 2 to the Pro and it was a nice upgrade. If your i1 Display 2 is working great and making good profiles, then there's probably not going to be a night/day difference on screen. My unit was getting old and tired though, so I noticed a big improvement.

In what way do these units get old and tired? Or is it just that you have become more demanding or need to use the device for a wider variety of applications?

I have a NEC Multisync 3090 WQXi with Spectraview II and have been using the i1Display 2 for calibration. I am suspecting that my i1Display 2 puck is failing because the Spetraview II calibration fails (hangs) part way through the process, not always at the same location. The unit is about 2 years old.

So, I have 4 questions:1) Can anyone confirm that the above behavior is a symptom of a failing puck?2) If I were to buy a new i1 Display Pro, would it work well with Spectraview II?3) How does the i1 Profiler software compare with Spectraview II?4) If comparable, does it require the DDC_CI communication to function at its best? In the end, I would probably prefer a calibration program that does not require this protocol. See related link. http://http://www.luminous-landscape.com/forum/index.php?topic=62740.0

So, I have 4 questions:1) Can anyone confirm that the above behavior is a symptom of a failing puck?2) If I were to buy a new i1 Display Pro, would it work well with Spectraview II?3) How does the i1 Profiler software compare with Spectraview II?4) If comparable, does it require the DDC_CI communication to function at its best? In the end, I would probably prefer a calibration program that does not require this protocol. See related link. http://http://www.luminous-landscape.com/forum/index.php?topic=62740.0

1. Seems odd that would be the case. Will H from NEC lurks here and may comment. Can you dig up some kind of crash log? 2. The new i1D-2 IS supported. 3. You want to use SpectraView! That product has far more control over the calibration of the panel as well as useful options. 4. See #3 and consider that DDC is a mixed can of worms.

1) I wouldn't know where to look for the crash log. Nothing obvious in the SpectraView menu items.2) I assume you meant the i1 Display Pro is supported by SpectraView? I didn't think to check before, but I see now on the SpectraView web site that the i1 Display Pro color sensor is supported.3) & 4) I was afraid of that, and yes, the DDC_CI bit is is mixed bag--fine when it works, but a show stopper for SpectraView when it doesn't or isn't accessible. Unfortunately, I don't have the DDC_CI link accessible via my laptop , which is my best computer. My desktop (core 2 duo) has DDC_CI link through the dual link DVI cable and I can use SpectraView, but the desktop suffers from very slow responses in LR4. I would like to use my laptop (i7, 8 cores, 16 GB ram) with the NEC display for LR4, but Spectraview (DDC_CI) isn't supported through the available ports as discussed in the link given in my previous post. I was hoping that a i1Display Pro puck, together with the i1 Profiler software on my laptop would solve all my problems, but alas--apparently no such luck.

1) I wouldn't know where to look for the crash log. Nothing obvious in the SpectraView menu items.2) I assume you meant the i1 Display Pro is supported by SpectraView? I didn't think to check before, but I see now on the SpectraView web site that the i1 Display Pro color sensor is supported.3) & 4) I was afraid of that, and yes, the DDC_CI bit is is mixed bag--fine when it works, but a show stopper for SpectraView when it doesn't or isn't accessible. Unfortunately, I don't have the DDC_CI link accessible via my laptop , which is my best computer. My desktop (core 2 duo) has DDC_CI link through the dual link DVI cable and I can use SpectraView, but the desktop suffers from very slow responses in LR4. I would like to use my laptop (i7, 8 cores, 16 GB ram) with the NEC display for LR4, but Spectraview (DDC_CI) isn't supported through the available ports as discussed in the link given in my previous post. I was hoping that a i1Display Pro puck, together with the i1 Profiler software on my laptop would solve all my problems, but alas--apparently no such luck.

1. If you’re on a Mac, I can assist, otherwise ask a Windows user <g>. On Mac, check the Console app and filter for SpectraView. That is assuming the app is really crashing. 2. Yes, the new i1Display-Pro (or the NEC labelled version which is the same) are supported.

Events are listed in the top panel, click on an event and information about it will be displayed in the bottom panel.In the bottom panel look for "More Information: Event Log Online Help" a link to more information, maybe.

Jack,Thanks for the pointer. Win7 is similar, but the "hang" did not cause a crash report to the log.

To at least partially close my previous post concerning the hang during calibration with SpectraViewII, it turned out to be a software conflict. I uninstalled about 6-7 programs (some were just trials anyway), and now I am able to calibrate with SpectraViewII again. If I happen to reinstall the conflicting program and have a subsequent failure, I will re-post.

The software conflict on Win7-64-bit I mentioned above is between SpectraView II (version 1.1.10) and RawDigger (0.9.11). Installing RawDigger to another directory did not solve the problem. Uninstalling RawDigger and rebooting solves the problem--repeatedly. Both NEC and the folks at RawDigger have been informed.