For our pre-calibration measurements we target 200 cd/m2 of light output, the sRGB gamut, and a gamma of 2.2. On the VUE 30 there are color temperature settings you can use for the grayscale and the warm setting was found to produce the most accurate image.

I’m also going to approach this review differently than before. The charts for all these measurements will be available in individual galleries. There is a table at the top of the page that summarizes the pre and post calibration measurements to easily see how well the monitor does before and after calibration. This should make it easier to read, and allow me to better focus commentary about the monitor performance on the areas that need it.

  Pre-Calibration Post-Calibration,
200 cd/m2
80 cd/m2
White Level 201.78 195.562 77.6183
Black Level 0.3214 0.3197 0.1388
Contrast Ratio 628:1 612:1 559:1
Gamma (Average) 2.2552 2.2406 2.5132
Color Temperature 6657K 6593K 6452K
Grayscale dE2000 4.0657 0.7705 1.3304
Color Checker dE2000 5.7431 4.0627 4.3305
Saturations dE2000 4.6853 3.7814 4.1323

The major improvement that we see is for the grayscale and gamma. On our 200 cd/m2 target calibration, those both come out nearly perfect. There is a small gamma spike at 95% but nothing really bad at all. The overall dE2000 is so low as to be unseen. When targeting 80 cd/m2 and the sRGB gamma curve, the Nixeus doesn’t perform quite as well. The gamma has a little more variation and the dE2000 is somewhat higher, though still very low. The loss of contrast ratio is the larger issue here.

Both grayscale results highly improve upon the original, which is slightly warm and has a very large error level as you approach peak white. The problem with the Nixeus VUE 30 lies with color reproduction. The errors for both the 96-point color checker and the saturations measurements improve, but not by a huge degree. Most of that improvement can be tied back to the grayscale improving since those numbers are a large part of these later tests. The default 6-point gamut chart is dropped here as the saturations chart covers that, and that dE2000 average is too heavily impacted by the grayscale data.

What we see is a wildly oversaturated gamut where green, cyan, red, yellow and magenta all fall far outside of the sRGB gamut boundary. With Green even the 60% saturation value is outside the sRGB gamut, which leads to very over-saturated colors. Even post-calibration we see that green dE2000 errors are past 5 from 40% on, and approaching a dE2000 of 10 by 100%. Aside from a few select colors in the Color Checker pattern, and the grayscale, almost all the colors have a large visible error.

The Nixeus lacks an internal LUT to fix this, and only so much can be done through the video card. A large gamut is nice, but just like with an OLED smartphone, we don’t want that gamut to be wildly oversaturated and push the color way outside of their boundaries. For any sort of color-critical work, or even just browsing photographs, the wild gamut of the VUE 30 will likely be a bad choice for those people after accurate colors. If you like a big, punchy image, you’ll probably like it.

Since we can’t control this gamut, perhaps using AdobeRGB as a target will lead to a better result? I decided to give it a try and see if that improves things at all, or if it was still an issue.

Brightness and Contrast AdobeRGB Calibration
Comments Locked


View All Comments

  • Impulses - Tuesday, August 20, 2013 - link

    Been hearing the same thing about OLED for years now... At this point I don't have any hope for it outside of small scale specialized usage cases (phones, electronic viewfinders on cameras, media players, mayyybe tablets).
  • sonny73n - Tuesday, August 20, 2013 - link

    Oh, please! Please make a 24 inch 2560x1600/1440 IPS monitor. Please, somebody, I'm begging you.
  • DanNeely - Tuesday, August 20, 2013 - link

    Don't hold your breath. That'd be ~125DPI; high enough that at anything beyond hunched over your laptop viewing distance windows controls are going to be squinty at native resolution; but not high enough to use a linear scaling mode. What you should be lusting after in that size bracket is a quadHD panel: ~180 DPI for software that supports it and relatively clean 2:1 scaling at 90dpi when it doesn't.
  • ZeDestructor - Tuesday, August 20, 2013 - link

    I run 1920x1200 on my 15.4" laptop without any scaling, and so do my friends on the even smaller 13.3" 1920x1080 ultrabooks.

    At 24", 2560x1600 is perfectly fine, but I'd rather skip straight to 3840x2400 myself....
  • seapeople - Saturday, August 24, 2013 - link

    I speak for those of us with adequate vision insurance or other means by which we have used to correct our vision: Stop talking.
  • geok1ng - Tuesday, August 20, 2013 - link

    I think the review gave correct advice about this monitor: it is a cheap and valid alternative for those that want adobe RGB coverage. For gaming it is just about as bad as many other 30" and certainly not better for gaming than a 27" 2560x1440 LED panel. For productivity i believe the price is a bit off, since you are better served by a 39" 4k Seiki TV for the same price, with better colors at sRGB. These are the last remnants of a dieing breed of CCFL monitors.
  • JarredWalton - Tuesday, August 20, 2013 - link

    I've been gaming on a 30" HP LP3065 for something like six or seven years. I love it, and sadly I think the introduction of scalers to 30" displays simply made them more laggy. I'll be sad when I eventually have to replace this display!
  • ZeDestructor - Tuesday, August 20, 2013 - link

    Wait till the eDP panels show up. Then everyone and their dog will be doing bypasses to skip the electronics entirely and pipe DP signals straight into the eDP panel. For reference, people have done that to use iPad retina displays or test the newest batch of 13.3" IPS displays :D
  • eric appla - Sunday, December 29, 2013 - link

    I fully agree, I also have HP3065 and can't fault it for gaming and daily productive work, the only downside is power consumption.
  • DParadoxx - Tuesday, August 20, 2013 - link

    How could you not measure input lag at the native resolution? Nothing else matters.

Log in

Don't have an account? Sign up now