MadVR - ArgyllCMS - Page 43 - AVS Forum
Forum Jump: 
 57Likes
Reply
 
Thread Tools
post #1261 of 2777 Old 12-08-2013, 06:14 AM
Member
 
VerGreeneyes's Avatar
 
Join Date: May 2013
Posts: 112
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 12
Oh, right. Sorry, I completely blanked on that. I can summarize:

For dispcal, add -k0 to disable black point color correction.
For targen, add -c Rec709.icm -V2 -N1 to use a perceptual spread of patches and emphasize the grey axis and dark regions.

Zoyd also uses -G2.4 -f0 instead of -gs (-f1 is the default) to use a BT.1886 style offset. I've been experimenting with -g709 -a64 to more closely match the collink step (but my monitor has been a pain recently).
VerGreeneyes is offline  
Sponsored Links
Advertisement
 
post #1262 of 2777 Old 12-08-2013, 10:11 AM - Thread Starter
AVS Special Member
 
N3W813's Avatar
 
Join Date: Feb 2003
Posts: 1,137
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 4 Post(s)
Liked: 34
First post updated with the latest recommended settings. Included instructions to update ArgyllCMS and DispcalGUI.

The latest snapshot of DispcalGUI has incorporated the -V and -N options for targen.exe as Dark region emphasis and Neutral axis emphasis, respectively. Setting neutral asix emphasis to 100% equals -N1 and setting dark region emphasis to 33% equals -V1.99.

My ArgyllCMS/MadVR 3DLUT Creation Workflow
My Sharp Elite Movie THX AV Mode Settings
--Aug 2011 Set, 2.2 gamma [ link ]
--Nov 2012 Set, 2.2 gamma [ link ]
N3W813 is offline  
post #1263 of 2777 Old 12-08-2013, 12:11 PM
 
MonarchX's Avatar
 
Join Date: Jul 2012
Posts: 669
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 30
I spent last few days testing ArgyllCMS further but only with BT.1886 2.4 tone curve. Flow used:

dispcal.exe -v -dmadvr -c1 -yn -Yp -G2.4 -f0 -k0 -A4.0 "LUT"
targen.exe -v -d3 -e4 -B4 -s40 -g128 -m9 -b9 -f0 -N1.0 -V1.6 -p1.0
dispread.exe -v -dmadvr -c1 -yn -Yp -k LUT.cal
colprof.exe -v -qh -bl -aX -V1.6
collink.exe -v -qh -G -iaw -3m -et -Et -IB:2.4 -a LUT.cal Rec709.icm profile.icm "3DLUT_name.icm"

I realize some of the commands had no effect (like targen.exe -V1.6), but they did not harm anything either. Using targen.exe commands I listed above resulted in a more accurate 3DLUT and lower black levels than using:
targen.exe -v -G -e4 -B4 -s40 -g128 -m9 -b9 -f0 -N1.0 -V1.6 -p1.0 -c Rec709.icm -d3

To load and test a .cal file for MadVR, I used:
dispwin.exe -dmadvr -s LUT.cal

To generate a .cal file for desktop environment, I used:
dispcal.exe -v -d1 -c1 -yn -m -Yp -qh "-w0.3127,0.3290" -G2.4 -f0 -k0 -A4.0 "LUT"

To load and test a .cal file for desktop environment, I used:
dispwin.exe LUT.cal

Regardless of whether I loaded and tested a madVR 3DLUT or just a .cal file for desktop, each and every single case raised black levels. Checking generated .cal file or madVR 3DLUT black level with a colorimeter was not as effective as simply running a black clipping test pattern in MPC-HC. In each case, the original brightness setting required to achieve the lowest visible black was either 48 or 49. The end-result .cal file and madVR 3DLUT required a setting of either 46 or 47 to achieve the lowest visible black level. This doesn't bother me as much as I have a TV that let's me do that. Additionally, I managed to increase my contrast to improve CR, which allowed me to decrease brightness further, while retaining calibration accuracy. These post-calibration adjustments resulted in a better contrast ratio than the one I had before calibration. The results are still better than with ArgyllCMS 1.6.1, but still far from "slightly raised black levels". Another thing that did change was slighly increased banding when using a .cal file for desktop, visible in this test - http://www.lagom.nl/lcd-test/gradient.php . I am not sure about madVR 3DLUT - I don't have a gradient pattern.
MonarchX is offline  
post #1264 of 2777 Old 12-08-2013, 12:39 PM
AVS Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 4,721
Mentioned: 30 Post(s)
Tagged: 0 Thread(s)
Quoted: 254 Post(s)
Liked: 361
That is consistent with what I have been seeing with several more test runs. There has been significant improvement in black point handling (a factor of 2-3 for me when running dispcal in conjunction with a 3dLUT) but there is a residual shift in black input to display luminance just above mll (0,012 cd/m^2 in my case = 1 click). Still, it's impressive to do this without making any assumptions of what the true black level is but I suspect this might be the limits to which the current algorithm can map the black level. Any further improvement might require a different approach to calculating the zero input level modification. I mentioned earlier that one could assume the user has already determined what this level should be and just leave it alone, but I don't know if this constraint is compatible with near-black levels. From my limited testing of modifying the LUT myself there were no immediately observable problems but I didn't do extensive testing.
zoyd is offline  
post #1265 of 2777 Old 12-08-2013, 02:40 PM
 
MonarchX's Avatar
 
Join Date: Jul 2012
Posts: 669
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 30
I edited my post. Given the same contrast setting for before and after calibration, I only had to lower brightness by only 2 clicks in each case, not 3. Once I started increasing contrast, I had to lower brightness by 1 more click in each case. The good thing is that increasing contrast and decreasing brightness post-calibration left me with a higher contrast ratio than the one I had before calibration, while maintaining excellent accuracy. This applies to madVR 3DLUTs and desktop 1D LUTs.

Pre-calibration SM adjustments:
Contrast - 77, Brightness - 49, CR - 1950:1

Post-calibration after manual adjustments:
Contrast - 82, Brightness - 46, CR - 2100:1
MonarchX is offline  
post #1266 of 2777 Old 12-08-2013, 03:24 PM
Advanced Member
 
gwgill's Avatar
 
Join Date: Jan 2013
Location: Melbourne, Australia
Posts: 652
Mentioned: 6 Post(s)
Tagged: 0 Thread(s)
Quoted: 90 Post(s)
Liked: 81
Quote:
Originally Posted by madshi View Post

Another one was for spreading the test patches differently or something like that.

That one (targen, colprof -V) is still up for evaluation as to what should be recommended by default. My tutorial does suggest to use it, but is open to emendation based on people experiences.
gwgill is offline  
post #1267 of 2777 Old 12-08-2013, 03:36 PM
Advanced Member
 
gwgill's Avatar
 
Join Date: Jan 2013
Location: Melbourne, Australia
Posts: 652
Mentioned: 6 Post(s)
Tagged: 0 Thread(s)
Quoted: 90 Post(s)
Liked: 81
Quote:
Originally Posted by VerGreeneyes View Post

Oh, right.
For dispcal, add -k0 to disable black point color correction.
Yes.
Quote:
For targen, add -c Rec709.icm -V2 -N1 to use a perceptual spread of patches and emphasize the grey axis and dark regions.
No, I'd recommend a more conservative value for -V by default, say -V 1.8 or -V1.6, since it hasn't been widely tested. Leave -N alone - the default value of 0.5 is already twice the equivalent of the DeltaE94 formula, don't increase it any more unless you know you get benefit from it and are happy with the tradeoffs [ Increasing test point density in one area reduces it in others ].
Quote:
Zoyd also uses -G2.4 -f0 instead of -gs (-f1 is the default) to use a BT.1886 style offset. I've been experimenting with -g709 -a64 to more closely match the collink step (but my monitor has been a pain recently).
-G2.4 -f0 is fine if your display has a not very black black, but risks creating a very shallow and hard for the 3dLut to control response if your black is very dark. -gs or -gl or even -g709 are probably safer choices.
Asmo42 likes this.
gwgill is offline  
post #1268 of 2777 Old 12-08-2013, 03:44 PM
AVS Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 4,721
Mentioned: 30 Post(s)
Tagged: 0 Thread(s)
Quoted: 254 Post(s)
Liked: 361
Quote:
Originally Posted by gwgill View Post

-G2.4 -f0 is fine if your display has a not very black black, but risks creating a very shallow and hard for the 3dLut to control response if your black is very dark. -gs or -gl or even -g709 are probably safer choices.

Any suggestions for a good rule of thumb here, CR=2500? (typical minimum luminance of 0.05 cd/m^2)
zoyd is offline  
post #1269 of 2777 Old 12-08-2013, 04:48 PM
Advanced Member
 
gwgill's Avatar
 
Join Date: Jan 2013
Location: Melbourne, Australia
Posts: 652
Mentioned: 6 Post(s)
Tagged: 0 Thread(s)
Quoted: 90 Post(s)
Liked: 81
Quote:
Originally Posted by zoyd View Post

Any suggestions for a good rule of thumb here, CR=2500? (typical minimum luminance of 0.05 cd/m^2)

This is all a bit theoretical - it would be great to have some actual hard numbers on what works and what doesn't.

If the calibration is close to the final 3DLut target, then maybe -G2.4 -f0 will help if you're working in a limited precision video encoding space and higher precision device space (ie. 10-12 bit). But if calibrating in an 8 bit -> 8 bit space it can make things worse, because any calibration that isn't a straight line will lose bits. On the other hand if the device is badly behaved calibration can improve the profiling, even in an 8 bit -> 8 bit space, if the gains in profiling accuracy outweigh the loss of bits.
gwgill is offline  
post #1270 of 2777 Old 12-08-2013, 05:09 PM
 
MonarchX's Avatar
 
Join Date: Jul 2012
Posts: 669
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 30
Quote:
Originally Posted by zoyd View Post

Any suggestions for a good rule of thumb here, CR=2500? (typical minimum luminance of 0.05 cd/m^2)

I think CR needs to be much higher than 2500:1 and black levels much lower than 0.04 cd/m^2. My SM-based calibration at 48hz yielded CR 1950:1, BUT my lowest black is either 0.05 cd/m^2 for day-mode or 0.04 cd/m^2 for night-mode. However, using anything other than -G2.4 -f0 resulted in a significant black level rise, far beyond acceptable levels. I tried -g2.2 -f0, -gs -f0, -g2.2 -f1.0, -gs -f1.0 and they all raised my black level from 0.04/0.05 cd/m^2 to 0.09 cd/m^2 and cut my CR from 1950:1 to 600:1. That's from dispcal.exe alone, going forward to create 3DLUT ends up cutting CR and raising black levels even further. Maybe my i1D3 is not the best and I either have CR higher than 1950:1 or my black levels are higher than 0.05 cd/m^2, but I know it is close and -G2.4 -f0 is the only thing that provided acceptable results.

BTW, do you know if skipping dispcal.exe and going straight to dispread.exe will keep my gamma and RGB WB exactly the same or change it to be more accurate?
MonarchX is offline  
post #1271 of 2777 Old 12-08-2013, 05:49 PM
AVS Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 4,721
Mentioned: 30 Post(s)
Tagged: 0 Thread(s)
Quoted: 254 Post(s)
Liked: 361
Quote:
Originally Posted by MonarchX View Post

I think CR needs to be much higher than 2500:1 and black levels much lower than 0.04 cd/m^2. My SM-based calibration at 48hz yielded CR 1950:1

Not exactly sure what you mean, the max CR is fixed by your display minimum black which in your case looks like 0.04 cd/m^2, you'll never get lower than that on your display. I asked the question in reference to at what point would a -gs or -gl dispcal target make more sense than -G with input offset (-f0).
Quote:
BTW, do you know if skipping dispcal.exe and going straight to dispread.exe will keep my gamma and RGB WB exactly the same or change it to be more accurate?

I've found that the gamma target is matched very well with with or without dispcal and that white balance is slightly improved using dispcal but that the 3dLUT alone is acceptable. Something like an average dE00 of 0.8 vs. 0.5 or so.
zoyd is offline  
post #1272 of 2777 Old 12-08-2013, 06:22 PM
 
MonarchX's Avatar
 
Join Date: Jul 2012
Posts: 669
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 30
Yes, I know what you meant. I was saying that in my case, black level is 0.04 cd/m^2 but CR is lower than it should be for such a black level. You suggested 0.05 cd/m^2 and CR 2500:1 as a point at which --gs would make more sense than -G2.4. So, I am saying that even though my CR is somewhat below 2500:1, my black level is about the same level as you proposed. Given my bad results with -gs, I was suggesting that black level of 0.05 cd/m^2 and CR 2500:1 is not a point at which -gs would make more sense than -G2.4. Does it make sense thus far? I was also saying that black level value like mine would usually be found on a TV with a CR that is higher than mine. It is possible that the reason I have a lower CR, but a black level that would be usually found on a TV with a higher CR, is because my i1D3 could be not very accurate. Thus, in reality, I could either have a CR higher than what i1D3 reports or a black level that is higher than what i1D3 reports.
MonarchX is offline  
post #1273 of 2777 Old 12-08-2013, 06:53 PM
AVS Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 4,721
Mentioned: 30 Post(s)
Tagged: 0 Thread(s)
Quoted: 254 Post(s)
Liked: 361
The D3 reading is correct at that level (they read fine down to 0.01 cd/m^2) so that is your CR, unless you can increase your peak white while keeping black constant, that is where it will remain.
zoyd is offline  
post #1274 of 2777 Old 12-09-2013, 08:40 AM
 
MonarchX's Avatar
 
Join Date: Jul 2012
Posts: 669
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 30
The point is - you need to have a CR higher than 2500:1 and higher than 4300:1 and blacks lower than 0.05 cd/m^2 and 0.03 cd/m^2. The new true 120Hz 24" (M/P)VA Eizo monitor (one of a kind for a price of a TV!) with a cd/m of 0.03 for black and CR of 4300:1 also had black level raised to 0.07 cd/m^2 when using -gs and -g2.2 with either -f0 or -f1.0. CR was cut to ~1000:1. I realize that my TV and this monitor are just 2 examples, but common sense tells me that these results are good indicators that one needs either a plasma or an OLED or even a CRT to use -gs/2.2 -f0/1.0 with dispcal.exe. Please quote this reply so that gwgill can see this data.

I noticed that ArgyllCMS profiling is limited by the actual colorspace. Meaning, if your 100% red saturation dE is 10 because it is heavily under-saturated, then end-result 3DLUT is likely to improve that dE but only slightly. I noticed that when I tried calibrating and profiling my PC Mode, which is heavily undersaturated (all colors) and won't let me expand the Color attribute. The end-result had accurate saturation up to 75%, but 100% saturation improved only a little bit.

How can I calibrate and profile with ArgyllCMS for SD content? I was doing research and so far I figured that I need to use NTSC format for North America-based content and PAL for European (or just UK?) - based content. There was an original NTSC colorimetry which used a different white point, and then there was SMPTE C which used the same white point as current Rec.709 content.
I see Rec.601 profiles in dispcalGUI - Rec.601 625/50 & 525/60 and also SMPTE240M. I do not see a Rec.601 profile in ArgyllCMS /ref directory, but I do see SMPTE_RP145_NTSC and SMPTE431

Could you tell me which one to use for SD content like X-Files? What kind of gamma is used with Rec.601/SMPTE C? I know I should research more on my own, but I just want the info on what to use with ArgyllCMS. Too bad I will only be able to watch that SD content with madVR since dispcal.exe alone doesn't adjust color gamut. TV SM CMS applies to all content, so I would have to re-calibrate it for SD content for things like Netflix. Should SD content re-mastered to HD be watched with SD colorpsace or HD colorspace?

EDIT: ArgyllCMS results provided low dE values of <1.5 for Rec.709 standard, and the same results ended up providing dE values of <3.0 for Rec.601 standard! biggrin.gif
MonarchX is offline  
post #1275 of 2777 Old 12-09-2013, 09:28 AM
10k
Advanced Member
 
10k's Avatar
 
Join Date: Sep 2005
Posts: 689
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 4 Post(s)
Liked: 38
Quote:
Originally Posted by MonarchX View Post

I noticed that ArgyllCMS profiling is limited by the actual colorspace. Meaning, if your 100% red saturation dE is 10 because it is heavily under-saturated, then end-result 3DLUT is likely to improve that dE but only slightly. I noticed that when I tried calibrating and profiling my PC Mode, which is heavily undersaturated (all colors) and won't let me expand the Color attribute. The end-result had accurate saturation up to 75%, but 100% saturation improved only a little bit.
3dlut cannot add gamut performance to your display, it can only adjust "inwards". If your display cannot show colors at full saturation target then messing around w/ video signal will not change that hardware limitation, you just have to live with it.
10k is offline  
post #1276 of 2777 Old 12-09-2013, 10:00 AM - Thread Starter
AVS Special Member
 
N3W813's Avatar
 
Join Date: Feb 2003
Posts: 1,137
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 4 Post(s)
Liked: 34
Quote:
Originally Posted by gwgill View Post

Yes.
No, I'd recommend a more conservative value for -V by default, say -V 1.8 or -V1.6, since it hasn't been widely tested. Leave -N alone - the default value of 0.5 is already twice the equivalent of the DeltaE94 formula, don't increase it any more unless you know you get benefit from it and are happy with the tradeoffs [ Increasing test point density in one area reduces it in others ].
-G2.4 -f0 is fine if your display has a not very black black, but risks creating a very shallow and hard for the 3dLut to control response if your black is very dark. -gs or -gl or even -g709 are probably safer choices.

Thanks for the guidance, Graeme. I've updated the instructions to set Neutral axis emphasis at 50% (-N0.5) and Dark region emphasis at 20% (-V1.6).

My ArgyllCMS/MadVR 3DLUT Creation Workflow
My Sharp Elite Movie THX AV Mode Settings
--Aug 2011 Set, 2.2 gamma [ link ]
--Nov 2012 Set, 2.2 gamma [ link ]
N3W813 is offline  
post #1277 of 2777 Old 12-09-2013, 10:20 AM
Member
 
Alec246's Avatar
 
Join Date: Nov 2009
Posts: 94
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by N3W813 View Post

Thanks for the guidance, Graeme. I've updated the instructions to set Neutral axis emphasis at 50% (-N0.5) and Dark region emphasis at 20% (-V1.6).

Please continue to update your guide as you learn new stuff! It's the best thing for people like me who just wants to enjoy a good picture without understanding all these complex codes! Thank you for your work!
Alec246 is offline  
post #1278 of 2777 Old 12-09-2013, 10:53 AM
Member
 
Alec246's Avatar
 
Join Date: Nov 2009
Posts: 94
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
DispCal isn't letting me load the X-Rite .edr files for Correction. Any idea why?

Edit: It seems Argyll doesn't come with the i1d3ccss.exe file that made the conversion. Any where I can find it?

Edit2: Found out oeminst is the one now responsible for this conversion. Can anyone teach me how to use it? I have no idea how to use CMD frown.gif Or maybe send me the already converted .ccss files from the x-Rite i1D3 smile.gif
Alec246 is offline  
post #1279 of 2777 Old 12-09-2013, 12:15 PM
Member
 
Alec246's Avatar
 
Join Date: Nov 2009
Posts: 94
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Yeah.. No idea why it isn't working. DispcalGUI says "No Colorimeter corrections could be imported"

Tried using older version of Dispcal, Argyll and i1Profiler with no sucess :/

Could someone send me the .ccss file of CCFLFamily_07Feb11.edr and WGCCFLFamily_07Feb11.edr please???

I never knew which of the two I shoud use, I have a Dell U2410 which is a Wide Gamut display, but I use it exclusively in sRGB mode, so I have always used CCFL Corrections for it!

And since there are so many gurus here, let me ask.

I got into the Dell U2410 Factory Menu, and tweaked the Gain settings to give me a more neutral image, instead of letting the software do all the work. Can I still use the .CCSS file from some user who created it from a Dell U2410, but probably didn't change anything on the Factory Menu? I don't know if the .CCSS file has information regarding the neutrality of the gray, or just other stuff that doesn't matter if your screen has been tweaked inside the Factory Menu.

Thank you!
Alec246 is offline  
post #1280 of 2777 Old 12-09-2013, 01:45 PM
Member
 
Kukulcan's Avatar
 
Join Date: Sep 2012
Location: Italy
Posts: 132
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 9 Post(s)
Liked: 23
The tweaking you make in the display settings doesn't affect the spectral response of your display, so if it's a wide gamut, it remains such a display even if you set it to emulate sRGB. So you should always use WGCCFLFamily_07Feb11.ccss

I suggest to you to try the gamut in native mode, white at D65, and then calibrate and create the 3DLUT
Kukulcan is offline  
post #1281 of 2777 Old 12-09-2013, 01:54 PM
Member
 
Alec246's Avatar
 
Join Date: Nov 2009
Posts: 94
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by Kukulcan View Post

The tweaking you make in the display settings doesn't affect the spectral response of your display, so if it's a wide gamut, it remains such a display even if you set it to emulate sRGB. So you should always use WGCCFLFamily_07Feb11.ccss

I suggest to you to try the gamut in native mode, white at D65, and then calibrate and create the 3DLUT

Well thank you, but the Native Mode is FAR beyong the REC709 standard TV uses. Is it wise to make such drastic software correction, when I can use Hardware to make it so? I always read Hardware is better than software to make corrections
Alec246 is offline  
post #1282 of 2777 Old 12-09-2013, 02:28 PM
AVS Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 4,721
Mentioned: 30 Post(s)
Tagged: 0 Thread(s)
Quoted: 254 Post(s)
Liked: 361
Quote:
Originally Posted by MonarchX View Post

but I do see SMPTE_RP145_NTSC

That's the one you want if you want to target Rec.601 primaries. Sorry I didn't quote the other parts, I don't want to annoy Graeme. wink.gif And 10K answered the gamut question.
zoyd is offline  
post #1283 of 2777 Old 12-09-2013, 05:52 PM
Member
 
Alec246's Avatar
 
Join Date: Nov 2009
Posts: 94
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Used some Internet .ccss for the Dell U2410 but I'm not sure now the results are OK. My Firefox using Color Management to Full, pages look totally pink :/

I wish I had something Neutral Gray to compare to the image of this monitor. But something is not right.

I can't use the .EDR files from X-rite for calibration, so frown.gif
Alec246 is offline  
post #1284 of 2777 Old 12-09-2013, 06:09 PM
Advanced Member
 
gwgill's Avatar
 
Join Date: Jan 2013
Location: Melbourne, Australia
Posts: 652
Mentioned: 6 Post(s)
Tagged: 0 Thread(s)
Quoted: 90 Post(s)
Liked: 81
Quote:
Originally Posted by Alec246 View Post

Edit: It seems Argyll doesn't come with the i1d3ccss.exe file that made the conversion. Any where I can find it?
I've replaced it with a single utility to cover all the OEM files for all the different instruments.
Quote:
Edit2: Found out oeminst is the one now responsible for this conversion. Can anyone teach me how to use it? I have no idea how to use CMD frown.gif Or maybe send me the already converted .ccss files from the x-Rite i1D3 smile.gif
If you've installed the X-Rite tools or if you put the appropriate driver CD in your CD/DVD driver and simply run oeminst from explorer, it will do the rest, although it's hard to check if anything went wrong that way, because the window closes at the end. You can see what's going on better if you open a command prompt window, cd to where the executable is, and run it there.

Note that there seems to be a bug in V1.6.2 oeminst, so I've updated the1.6.3 beta executables
http://www.argyllcms.com/vidtools_win32.zip and http://www.argyllcms.com/vidtools_win64.zip.
Alec246 likes this.
gwgill is offline  
post #1285 of 2777 Old 12-09-2013, 06:20 PM
 
MonarchX's Avatar
 
Join Date: Jul 2012
Posts: 669
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 30
Alec246,
I attached a file with corrections just for you. Test.bat is for CCFL and Test2.bat is for WLED. I included the Rec709.icm reference file. The best location to unzip these file to would be in C:\Users\"user name"\ArgyllCMS , where you should also keep the needed dispcal, targen, dispread, colprof, and collink executable files. I used commands that provided me with the best results. Some will say that several commands I used will have no effect, but I did not want to take any chances and accidentally mess up commands that provided me with the best results. I also included a Commands.txt file which lists the commands I use and where I got them. If you want to use 64bit files, make sure to use madTPG from the updated madVR test build, found here - http://madshi.net/madVRanotherTestBuild2.rar .

Simply open madTPG, make sure videoLUTs and 3DLUTs are disabled, place your X-Rite i1DPro/3 in the center of the screen and launch Test.bat to calibrate and profile a CCFL screen (resulting file name should be 3DLUT.icm and 3DLUT.3dlut) or WLED screen (resulting file name should be 3DLUT2.icm and 3DLUT2.3dlut).

Test.zip 45k .zip file
Attached Files
File Type: zip Test.zip (44.9 KB, 4 views)
Alec246 likes this.
MonarchX is offline  
post #1286 of 2777 Old 12-09-2013, 07:03 PM
Member
 
Alec246's Avatar
 
Join Date: Nov 2009
Posts: 94
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by gwgill View Post

I've replaced it with a single utility to cover all the OEM files for all the different instruments.
If you've installed the X-Rite tools or if you put the appropriate driver CD in your CD/DVD driver and simply run oeminst from explorer, it will do the rest, although it's hard to check if anything went wrong that way, because the window closes at the end. You can see what's going on better if you open a command prompt window, cd to where the executable is, and run it there.

Note that there seems to be a bug in V1.6.2 oeminst, so I've updated the1.6.3 beta executables
http://www.argyllcms.com/vidtools_win32.zip and http://www.argyllcms.com/vidtools_win64.zip.

I got it to work! Thank you. Using CMD, I typed oeminst nameofthefile.edr and it generated the .ccss file! smile.gif

And I can confirm Argyll is doing a Wonderful job keeping the blacks intact now, it used to make my poor Dell U2410 look even worse, but now there's almost no change in the black level! Amazing
Quote:
Originally Posted by MonarchX View Post

Alec246,
I attached a file with corrections just for you. Test.bat is for CCFL and Test2.bat is for WLED. I included the Rec709.icm reference file. The best location to unzip these file to would be in C:\Users\"user name"\ArgyllCMS , where you should also keep the needed dispcal, targen, dispread, colprof, and collink executable files. I used commands that provided me with the best results. Some will say that several commands I used will have no effect, but I did not want to take any chances and accidentally mess up commands that provided me with the best results. I also included a Commands.txt file which lists the commands I use and where I got them. If you want to use 64bit files, make sure to use madTPG from the updated madVR test build, found here - http://madshi.net/madVRanotherTestBuild2.rar .

Simply open madTPG, make sure videoLUTs and 3DLUTs are disabled, place your X-Rite i1DPro/3 in the center of the screen and launch Test.bat to calibrate and profile a CCFL screen (resulting file name should be 3DLUT.icm and 3DLUT.3dlut) or WLED screen (resulting file name should be 3DLUT2.icm and 3DLUT2.3dlut).

Test.zip 45k .zip file

Thank you for the files!! I managed to get the oeminst.exe to generate it for me, but I will look into your .bat to see how you do your calibration!
Alec246 is offline  
post #1287 of 2777 Old 12-10-2013, 01:48 AM
Member
 
Kukulcan's Avatar
 
Join Date: Sep 2012
Location: Italy
Posts: 132
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 9 Post(s)
Liked: 23
Quote:
Originally Posted by Alec246 View Post

Well thank you, but the Native Mode is FAR beyong the REC709 standard TV uses. Is it wise to make such drastic software correction, when I can use Hardware to make it so? I always read Hardware is better than software to make corrections

Well it depends on the quality of the hardware, and for consumer grade displays tweaking the color settings may be worse than letting Argyll to do all the work. If your display works at 10 bit or more, set color temperature and space in the display itself, otherwise I wouldn't touch anything...
Display initial state is very important, I hope to hear a comment from the experts here...

I report an abstract from the website of Marcel Patek, here the link: http://www.marcelpatek.com/monitor.html Practical points : (Click to show)

Except of the brightness, all adjustments of common LCD displays are done by tweaking the LUT in video card. Higher end monitors use 10-bit LUT build-in the display.
Editing 8-bit lookup tables is essentially the same as editing 8-bit per channel image in Photoshop (some of the original 256 levels will be lost).
Unless the LCD monitor has internal 10-bit per channel LUT, set the white point and gamma to the "native" if such option exists in calibration software or use D65 (CCT 6,500 K) and gamma 2.2. These values are very close to the "native" settings built in the display electronics by most manufacturers.
A ballpark numbers for luminance setting are around 120 cd/m2 (LCD) and 90 cd/m2 (CRT).
Before calibration, always reset the video card LUT to ensure that LUT is in its original "cleared" state.
After calibration, always check smoothness of the grayscale gradient. The test image should be neutral without any signs of color. Also, there should be no banding or posterization visible in the image.

- See more at: http://www.marcelpatek.com/monitor.html#sthash.sMB3w7sA.dpuf
Kukulcan is offline  
post #1288 of 2777 Old 12-10-2013, 03:41 AM
Member
 
VerGreeneyes's Avatar
 
Join Date: May 2013
Posts: 112
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 12
Quote:
Originally Posted by Kukulcan View Post

Display initial state is very important, I hope to hear a comment from the experts here...
Me too. For instance the white point of my display by default is a mile off what calibration aims for. Should I leave the monitor set to its 'Warm' preset, its default 'User' preset (which sets all channels to 100% and is different from 'Warm' or 'Cold') or fiddle with each channel to reach the desired white point? I'm not sure whether I should be more worried about the bit depth of my display's knobs or reducing the output range of the RAMDAC curves.
VerGreeneyes is offline  
post #1289 of 2777 Old 12-10-2013, 06:28 AM
Senior Member
 
fhoech's Avatar
 
Join Date: Apr 2013
Location: Stuttgart, Germany
Posts: 217
Mentioned: 6 Post(s)
Tagged: 0 Thread(s)
Quoted: 51 Post(s)
Liked: 43
One important point to note is that even some cheap displays seem to apply dithering when changing their internal LUT (I have here a 6 bit TN panel screen where this is the case), so it may be preferable to do some adjustments via the actual display controls and only the rest via the graphics card videoLUT which is usually not dithered. When using madVR this becomes a different mattter though because its dithering may be superior to that of the internal display processing.
fhoech is offline  
post #1290 of 2777 Old 12-10-2013, 07:14 AM
Member
 
Alec246's Avatar
 
Join Date: Nov 2009
Posts: 94
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
I trust my Dell U2410 to make these corrections in Hardware. And I have to use sRGB mode anyway when I use the computer, or I get totally bizarre colors on games and browing

BTW, the first post tutorial uses a Gamma of 2.4. Is there a reason for that, or is it a matter of preference of 2.4 vs 2.2?

Thanks!
Alec246 is offline  
Reply Display Calibration

User Tag List

Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page


Forum Jump: 

Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off