99% AdobeRGB gamut coverage is stated for native gamut. PERIOD. It is an intersection between two gamuts: dell gamut and AdobeRGB gamut. They (their ICM profiles) SHOULD be compared in relative colorimetric or perceptual intent, they SHOULD NOT be compared in absolute colorimetric.

To get actual gamut, just perform a "profile only" in DispcalGUI. A lineal LUT will loaded in GPU, so no correcction is applied an you use only internal monitors LUT. Try a XYZLUT+matrix profile, smoothing 65x65x65, 600+ patches for measurement.

2D plot of DCCS ICM version2 profiles SHOULD be compared in dispcalGUI with relative colorimetric/perceptual intent, since they are defined to a PCS white and actual white is stored in a CHromatic ADaptation matrix TAG with 2D ploting utility does not read.

So there are not gamt coverage issues with these Dells, just "not so experienced users" with color management.

P.S: Do not use "native" preset in DCCS, if you want native gamut use xy custom coords fro R,G and B (from factory profile inspection or EDID) and set manually a daylight white because "native" GB-LED white is not a daylight white.
Native gamut is for use in a large variety of working profiles, from sRGB to eciRGBv2 as an example. If you only deal with sRGB and AdobeRGB images (not with eciRGBv2 tagged images), it would be WISER to use AdobeRGB preset from DCCS, than aiming to native gamut. This last statement is TRUE for widegamut Dells, for NEC spectarviews and for Eizo coloredges, specially if you do not have an nvidia Quadro or an AMD Firepro, you do not use MS Windows and you do not use Photoshop.

Thanks for reply. Fine indications, thanks. As you see, the second link I pointed in the first post gave the same indications as you (see in comments down below) which I followed. Except for the 'profile only' thing that I learnt later reading elsewhere (anyway thank you for pointing this out).

So, yes, I knew about 99% aRGB is for native (although I tested the other settings), so I calibrated in DCCS with native (I knew the thing you explain about WP, but anyway, I wanted to test), result? Max 92.8% coverage at 50% brightness which is >200 cd/m2 (~90.5% at 120 cd/m2). The result WP of this was 6511K (and 6521K for 120 cd/m2). I let the monitor warm up for 2 hours before performing the tests.

Of course these figures were obtained as you say, in dispcalGUI profiling only XYZLUT+matrix but with 442 patches (I'll re-test as you say, but I don't expect big changes). What I don't know is if the numbers (coverage) calculated by dispcalGUI are calculated in relative or absolute...

I think that you assumed that I compare gamuts in absolute intent, maybe you know that dispcalGUI gamut coverage percentage calculation is done in absolute intent? If so, then I understand, if not, you did a wrong guess, as I compared them in relative (in ColorThink and dispcalGUI), showing a reduced coverage that could fit well with the percentage calculated by dispcalGUI.

I guess that the gamut comparison in relative intent that is performed in dispcalGUI (zoomed in) and ColorThink is correct.

But I wonder... even if the coverage calculation of dispcalGUI was in absolute, isn't it too much difference between 90% and 99% in this case? Maybe not...maybe yes. I dunno.

Anyway, when comparing visually (it's not precise, I know, I know) in ColorThink (or in profile information from dispcalGUI -zoom applied-), in relative colorimetric, there is an obvious missing on greens. How much? I can't put numbers of coverage (at side of the ones from doing 'profile only' thing, indicated in last paragraph). Still, if checked the reviews in prad.de and tftcentral, it is seen that the native gamut match (almost perfectly) the green primary of aRGB, which is not the case at all for my monitors (be it relative colorimetric, perceptual, or of course in absolute intent comparison).

Am I missing something here? Likely (I don't have problems admitting I don't not know everything, this is why I put questions here). But what? If the monitors have not faults, then what are the tests to check the 99%, no matter if it implies 'native', some brightness, etc. How can be checked that the monitor satisfy 99% of aRGB?

The tests pending I'll do:

- As you suggest: in DCCS to impose the xy coordinates of primaries and whitepoint, and check. 

- I'll re-check the native 120 cd/m2 with smoothing and >660 patches to see if it changes anything.

-Check in dispcalGUI the U2413.icm that comes with the monitor. In Colorthink it can be seen already that it 'covers' aRGB, but what is the sense of that if when measured by ourselves it is quite different? Shouldn't be the reliable one the one measured for each monitor? Anyway, as it covers aRGB, it seems a good idea to check it in dispcalGUI (I think on a 'factory reset', load the U2413.icm in windows color management, and do a 'measurement report' in dispcalGUI), and see if the deviations for the primaries are ok (Delta_e<3 for example)... Thank you very much for this idea. At side of the 'measurement report', I'll do a 'profile only' to check if it fits with U2413.icm (which I doubt).

I'll report on all that later.

BTW, in a second monitor (U2413), I got for 120 cd/m2, 93.1% (at 6575K) coverage instead of 90.8% (as always DCCS in native + dispcalGUI, 'profile only' for evaluation). But this screen is corrupted in other aspects so it will go back to seller. Ah! I forgot to say I have a Quadro, Windows 7 x64, and use PS. So maybe (and maybe not) there is some issue with the monitors...

I forget a to tell you that you need to apply RG_phosphor spectral corrections in dispcalGUI or measurements will be wrong

% gamut coverage in "profile only" in DispcalGUI is done in the right way because DispcalGUI/ArgyllCMS does not store WP as PCS WP, and if you do not choose same WP as "comparison profile" (AdobeRGB D65) it will do the transformation. Of course in 2D plot you need to use colorimetric relative/perceptual if WP do not match (for example, native gamut @ D55)

After you do a profile only, please upload 2D plot of the gamut and a screenshot of your dispcalGUI configuration so we can see if there is some kind of misconfiguration of dispcalGUI or is caused by monitor (or wrong Quadro settings).
Just to lower the number of incompatibilities, please disable 10bit support on Quadro and turn off all color enhancements in nvidia control panel.

Also, it doe snot troubel you, please upload HTML report obtained in dispcalGUI when performing a "measurement report", RG_phosphor as spectral correction, and all options disabled in measurement report popup, current profile and verify extended.

Thank you!

Yes, I used RG_phosphor.

I'll do all of that (I hope having time today...), and report results and screenshots/HTML (I'll see how can I upload that...). I'll do it later, though. I can't now.

I am doing some tests (not so much time today). Anyway, although I can extract the primaries coordinates xy from the standard profile (u2413.icm), I would prefer to get the primaries from EDID .

The problem is that I don't find any program that gives me this data. Could you (or someone else) point me to some software or way to read this data from EDID, please?

Thanks!

DispcalGUI -> options -> create profile form edid. If it does not work in 2.5, try 2.1

Hello

Sorry for delay (lot of work to do). I calibrated with DCCS and then doing a profile only, and the results are below.

I used this procedure:

1. Load U2413.icm in Windows CP
2. Launch dispcalGUI Calibration and ICC Profile Loader to be sure that U2413.icm is loaded
3. Factory reset monitor
4. Load DCCS and do calibration with choosen parameters
5. Close DCCS
6. Load dispcalGUi and with correct parameters do Profile Only
7. Load the resultant profile
8. Do a Measurement report with Current profile
9. Load in Windows CP the profile from DCCS (now it should be loaded the profile created with profile only option of dispcalGUI)
10. Do a Measurement report with Target Profile as the DCCS generated profile (have to go to Windows  'color' folder, and pick it).

I summarize in a table the primaries and WP coordinates obtained from EDID (using dispcalGUI, 'profile from EDID' and obtaining the values as listed in profile information), the primaries and WP from U2413.icm obtained from both, ColorThink and dispcalGUI (profile information):

I calibrated in DCCS by imposing the EDID coordinates for primaries and WP.

First the screenshots of the settings in DCCS:

The DCCS result:

Then I did a profile only in dispcalGUI, (I checked that the profile from DCCS was loaded in WIndows CP), with these settings:

The result is:

With the details:

And next data (scrolling down). Please pay attention that in the following screenshot the gamut graphic is back in absolute colorimetric:

Then I did a 'measurement report' of the current profile (so the one created by dispcalGUI with the option 'profile only'):

The settings:

The html file:[View:/cfs-file/__key/communityserver-discussions-components-files/3529/5040.Measurement-report-2_5F00_5-_2D00_-EDIDxy-120-Cal1-Profile-Only.zip:550:0]

Just in case, I repeated the measurement report, now with the profile created by DCCS as target:

The settings:

The html file:[View:/cfs-file/__key/communityserver-discussions-components-files/3529/6116.Measurement-Report-2_5F00_5-EDIDxy-120-Cal1-DCCS.zip:550:0]

I repeated it with the other monitor (the one with manufacture date from July 2014), and the results are not good neither (although a little better in coverage terms -93%-, much worse in contrast ratio, for example).

I have all the screenshots, but to not overload this post, I don't upload them. If you want them, please tell me. Thank you very much for any help,

This one:
http://en.community.dell.com/resized-image/__size/550x0/__key/communityserver-discussions-components-files/3529/5545.DCGUI-Profile-only-results-5.png

http://en.community.dell.com/resized-image/__size/550x0/__key/communityserver-discussions-components-files/3529/5545.DCGUI-Profile-only-results-5.png

Does not seem to be related to any of your profiles. I do not know where it comes from.


Regarding green coordinates, let's check if it is an actual gammut issue of you GB-LED backlight or DCCS related. Run a "calibrate & profile" form "Custom color" OSD mode in DispcalGUI at D65 & gamma 2.2 reletive. It should be "near" GAIN R100 G91 B97 Bright 23/Contrast near 50 but it varies from unit to unit. Use same configuration than with your previous "profile only" but set calibraton speed to "slow".

After calibration is performed, check green coordinates in xyY plot. It they are as it seems from DCCS far to the right and to the boton loosing that amount of AdobeRGB cyan (less than 96-97% AdobeRGB coverage in custom color OSD, what matters to a photo hobbist/professional is AdobeRGB cyan, not green since green is not printable but cyan is), there ssems to be an issue with your unit and since it does not match specifications, I think you could use waranty (it depends on your contry laws who is responsible for exchange or repair)

I checked the graph you refer to. It is 'correct' as far as it belongs to the others (it is from the same 'profile only'). It was surprising to me too, and it makes me think that my monitor has a native temperature quite different from the U2413.icm and the xy WP coordinates from EDID (~6500K).

Only to test, I have done a calibration with EDID xy coordinates for primaries, but D50 as WP. Then the graph changes to this:

Anyway the coverage is 94%, somewhat better, but still off, and general color, quite warm/yellow.

Then I have done the calibration as you explain in the last post. I followed the steps:

1. Load U2413.icm in Windows CP
2. Launch dispcalGUI Calibration and ICC Profile Loader to be sure that U2413.icm is loaded
3. Factory reset monitor
4. Change to Custom mode in OSD
6. Load dispcalGUi and with correct parameters (as you explain, see sshot below) do a Calibrate & Profile
7. Load the resultant profile
8. Do a Measurement report with Current profile

The dispcalGUI settings are:

and

When calibrating I found this (with suggested values):

After adjusting them:

And with Brightness at 23 and Contrast at 55.

These images also suggest me that the monitor has some warmer WP than 6500K, no matter what EDID says. But I may be wrong...

After calibration these are the results:

The next one has the comparison in absolute (attention!):

And just in case, the Measurement report: [View:/cfs-file/__key/communityserver-discussions-components-files/3529/1488.Measurement-Report-2_5F00_5-_1420_-DCGUI-Cal_2600_Prof-D65_5F00_120_5F00_22.zip:550:0]

The values for the dispcalGUI calibration and profiling and also the ones of the DCCS calibration with EDID xy values. Both obtained from the 'Measurement report', from columns 'Nominal values' :

I would say that there is some problem with the monitor although the green is a bit better than with DCCS cal (why?), and it gains about 1.3% more of coverage, but in still not what it should be.

I wonder also why the blue is also better, I mean, I know I impossed in DCCS the y=0.0537 for Blue, but DCCS stopped at 0.0628...

As a side note: it does not seems an isolated case, as the other one I still have, is a little better (2% more of coverage) but still off.

If you performed a full "calibrate & profile" in "custom color" OSD mode and you obtained THIS Tone Response Curve:
http://en.community.dell.com/cfs-file/__key/communityserver-discussions-components-files/3529/5618.DCGUI-Cal_2600_Profile-results-5.png
Then there is something wrong your computer: GPU, drivers... or you have a defective DispcalGUI/ArgyllCMS instalation
This cannot be caused by monitor since DispcalGUI corrects whatever native TRC to match desired gamma and grey neutrality IN GPU, not in monitor.

GPU may be broken, may be you have some color enhancement aplied to GPU that you have to disable, ... may be you have Dell Display Manager set to a wrong mode. (set it to "manually" and disable "Smart video enhance")

Maybe you have applied "calibrate and profile" to a wrong OSD mode... I do not know what worng steps you did or what misconfiguration you have on your GPU drivers but this image ins not a monitor issue

Try DispcalGUI and your U2713H with ANOTHER computer, and if it can be choosed, pick a computer with an AMD GPU card with all color enhancements disabled.

By the way, set white and black level to "native" and put manually your desired brightness while geting desired White point, what you did may cause unnecessary grey level loss

P.S: EDID is not individually tunned for each monitor (I suppose) is a generic gamut and gamma description for all units in a model. It is the easyiest and fastest way to check what gamut a monitor should have without perform a measurement. Hence, it does not matter and does not represent a contract of which WP or gamma Standard or "unmodified" Custim color mode have.