MadVR - ArgyllCMS - Page 106 - AVS Forum | Home Theater Discussions And Reviews

Forum Jump: 
 449Likes
Reply
 
Thread Tools
post #3151 of 4398 Old 03-26-2015, 12:00 PM
Member
 
Join Date: Nov 2014
Posts: 129
Mentioned: 4 Post(s)
Tagged: 0 Thread(s)
Quoted: 102 Post(s)
Liked: 25
Quote:
Originally Posted by zoyd View Post
ok - then the 679 patch profile just doesn't give as accurate a location of the blue primary.

So you could stick with the larger profile you already have, or try another one of that size and use this one as a preconditioning profile. I noticed your peak white is pretty bright, do you intend this for a daytime viewing mode? If so, you might try out different gamma targets to see what works best in your environment.
Yes, I found that the OLED behaves a bit different than plasma or LCD...I notice that PQ is improved with a higher Y. On one hand the calibration controls only work with contrast at 100 (or very close to it), on the other RGB values on all IREs get closer to 100% with a higher Y and get apart with a lower Y. Specially with blue on low IREs. If I go for a 130cd/m2 or lower White Y the blue on IRE 5 and 10 are much more unaligned.

I don't know if it's a common trait of OLED or just my set. But it helps the calibration to have a higher than normal Y. The funny thing is that I don't find it uncomfortable (my previous set was calibrated to 130cd/m2, so I was used to that kind of level). It might have to do with how the APL works and with the pure blacks. It's really something amazing at night to not be able to distinguish where are the borders of content from TV border or the rest of the wall. The movie seems to be hovering in the air...

Quote:
Originally Posted by fhoech View Post
And the correction used (none for the V3 679, custom OLED for the V4 2527 patches profile), which would explain the gamut differences.
Yes. you're right. I have to try to create one LUT using correction and one without and compare the differences. I find it very odd that the version without correction actually produces better results.
Pepelegal is offline  
Sponsored Links
Advertisement
 
post #3152 of 4398 Old 03-26-2015, 12:33 PM
AVS Forum Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 6,293
Mentioned: 86 Post(s)
Tagged: 0 Thread(s)
Quoted: 1314 Post(s)
Liked: 1043
Quote:
Originally Posted by fhoech View Post

I'd still say don't use it without good reason. The default mode is slightly more accurate as Zoyd had briefly tested. Of course, if you want to play around with it, I'm not stopping you, but as you already get good results you're probably not going to gain anything.
Just to follow up, the one test I did comparing the two gamut mapping modes is shown below. The dotted line is the alternate "PCS-to-device" mode that requires the high resolution tables.

fhoech likes this.
zoyd is offline  
post #3153 of 4398 Old 03-26-2015, 01:01 PM
Advanced Member
 
fhoech's Avatar
 
Join Date: Apr 2013
Location: Stuttgart, Germany
Posts: 822
Mentioned: 31 Post(s)
Tagged: 0 Thread(s)
Quoted: 403 Post(s)
Liked: 262
Quote:
Originally Posted by Pepelegal View Post
Yes. you're right. I have to try to create one LUT using correction and one without and compare the differences. I find it very odd that the version without correction actually produces better results.
The one without correction just has a blue closer to the rec. 709 blue, doesn't necessarily mean it's better (unless you trust the uncorrected i1D3 readings more than the corrected ones). I undid the correction matrix from the V4 measurements, and the uncorrected V4 gamut is extremely similar in shape to the V3 gamut (dotted line is V3, colored is V4 with correction undone).
Attached Thumbnails
Click image for larger version

Name:	Gamut V4 invcorr vs V3.png
Views:	78
Size:	41.7 KB
ID:	627913  
Pepelegal likes this.

Last edited by fhoech; 03-26-2015 at 01:21 PM. Reason: Wording
fhoech is offline  
post #3154 of 4398 Old 03-26-2015, 05:55 PM
Member
 
baii's Avatar
 
Join Date: Jul 2013
Posts: 70
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 23 Post(s)
Liked: 16
I find the spectral correction (ccfl or rgb led for my case) for i1d3 only really affect the calibrated target whitepoint only.
If I verify a spectral corrected color profile w.o using a correction,vice versa, I see huge delta e in whitepoint but not in the color test patches.
baii is online now  
post #3155 of 4398 Old 03-27-2015, 05:27 AM
Member
 
Join Date: Nov 2014
Posts: 129
Mentioned: 4 Post(s)
Tagged: 0 Thread(s)
Quoted: 102 Post(s)
Liked: 25
Yesterday I created a new LUT using the same parameters (with the correction file enabled) with 994 patches but the result was for some reason very bad with lots of artefacts... I ended up deleting it as V3 and V4 created previously were much better.

One situation I'm getting is when the process of creation the LUT ends, it now hangs on the "Generating gamut views" and I need to cancel to close DCG. Sometimes I get the popup to choose to install the 3DLUT (which I always do) and view the profile, but not always.

After the bad result with that LUT, I spent some time doing a full calibration using the 20points controls and aligning the gamma curve for the Wide Gamut option.

I then configured DCG with a new calibration file for the i1d3 and did a profile only (with the same parameters I posted before and that worked well with V3). I choose for test pattern the "Massive Testchart for Rec709" with a small change to just use 80 neutral patches (instead of the default 140) - 2486 total patches.

I choose this large test pattern because I wanted to let it run unmanned overnight, so that was a way to minimize the time the TV is left displaying the last grey pattern until morning.

So, this morning, I found DCG hanged again in the "Generating Gamut Views" (a believe on "iccgamut.exe" command) but no popup to install the 3DLUT (log file ends with that command).

So, because (I believe) I canceled the process (I had no other choice), I don't have the .3DLUT file and I can't check in madVR how were the results. The only information I have of the profile is that peak err = 1.744424, avg err = 0.340880, RMS = 0.403823 which is a bit worse than the previous V3 with peak err = 1.613902, avg err = 0.311188, RMS = 0.383008

The .icm also seems similar to the ones of previous created LUTs.

Here is the link for the V5 project : LINK

Is there any way to generate the 3DLUT using the existing information ?

Thank you,
Pepelegal is offline  
post #3156 of 4398 Old 03-27-2015, 05:40 AM
Member
 
Join Date: Nov 2014
Posts: 129
Mentioned: 4 Post(s)
Tagged: 0 Thread(s)
Quoted: 102 Post(s)
Liked: 25
I think I found the way to generate the 3DLUT file.
I dropped the .icm on DCG, unchecked the "create 3D LUT after profiling" and clicked on "Create 3D LUT" button.

It's filling the LUT table right now...
Pepelegal is offline  
post #3157 of 4398 Old 03-27-2015, 07:14 AM
Advanced Member
 
fhoech's Avatar
 
Join Date: Apr 2013
Location: Stuttgart, Germany
Posts: 822
Mentioned: 31 Post(s)
Tagged: 0 Thread(s)
Quoted: 403 Post(s)
Liked: 262
Quote:
Originally Posted by Pepelegal View Post
I then configured DCG with a new calibration file for the i1d3 and did a profile only (with the same parameters I posted before and that worked well with V3). I choose for test pattern the "Massive Testchart for Rec709" with a small change to just use 80 neutral patches (instead of the default 140) - 2486 total patches.
That's a reasoanble way to do it. Just as a note, none of the default testcharts go over 121 grayscale steps, and there's a reason for that too: When using 20% dark region emphasis (like most of the "optimized for ..." patchsets), the maximum number of grayscale steps that'll still round to different RGB levels when quantized to 8 bits is 129 (assuming full range RGB encoding).

Quote:
Originally Posted by Pepelegal View Post
So, this morning, I found DCG hanged again in the "Generating Gamut Views" (a believe on "iccgamut.exe" command) but no popup to install the 3DLUT (log file ends with that command).
Seems like Argyll 1.7b isn't working right on your system (keep in mind it's a personal build of in-development beta code). I'd recommend going back to 1.6.3 for the time being.

Quote:
Originally Posted by Pepelegal View Post
I think I found the way to generate the 3DLUT file.
I dropped the .icm on DCG, unchecked the "create 3D LUT after profiling" and clicked on "Create 3D LUT" button.
Yes, you did this the right way.
fhoech is offline  
post #3158 of 4398 Old 03-27-2015, 08:44 AM
AVS Forum Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 6,293
Mentioned: 86 Post(s)
Tagged: 0 Thread(s)
Quoted: 1314 Post(s)
Liked: 1043
I ran a profile only sequence using Auto targets and it worked flawlessly - I'm really impressed with the functionality and performance of DCG. I was interested in how the 154 target preconditioner + auto targen settings performed compared to my typical choices.

Results of previous 2500 patch set using a 2500 patch preconditioning profile:

Code:
% < 1.5% < 1.0
      99.8667      97.6000
dE00 avg,stdev,max,worst 10%
      0.37704436      0.22404800       1.5180518      0.86936644
Grayscale avg,stdev,max
      0.39472615      0.22042243       1.1321318
Red ramp avg,stdev,max
      0.36715921      0.22067996       1.0229049
Green ramp avg,stdev,max
      0.34363367      0.32186486       1.5180518
Blue ramp avg,stdev,max
      0.27777325      0.31259952       1.4135966

Results of Auto targen with total 2661 patches:

Code:
% < 1.5% < 1.0
      99.8667      97.7333
dE00 avg,stdev,max,worst 10%
      0.36758927      0.22620677       1.5419512      0.86988927
Grayscale avg,stdev,max
      0.42411560      0.23800477       1.0835316
Red ramp avg,stdev,max
      0.38564623      0.20958563       1.1055526
Green ramp avg,stdev,max
      0.36779837      0.19635333      0.75162999
Blue ramp avg,stdev,max
      0.24217088      0.22392966       1.0053001
And the histograms, auto targen in green:



A slight edge to the auto mode. The primary differences with my typical selection is that the auto mode has a higher density of single axis patches (41 vs. 20), higher density of neutral axis (121 vs. 50) and uses a dark region emphasis of 1.6 vs. no emphasis.

If we look at dark region patches [L* < 15] there are also some minor improvements:

Auto mode = green squares
fhoech likes this.

Last edited by zoyd; 03-28-2015 at 05:20 AM.
zoyd is offline  
post #3159 of 4398 Old 03-27-2015, 09:01 AM
Advanced Member
 
fhoech's Avatar
 
Join Date: Apr 2013
Location: Stuttgart, Germany
Posts: 822
Mentioned: 31 Post(s)
Tagged: 0 Thread(s)
Quoted: 403 Post(s)
Liked: 262
Quote:
Originally Posted by zoyd View Post
I ran a profile only sequence using AUTO targets and it worked flawlessly - I'm really impressed with the functionality and performance of DCG. I was interested in how the 154 target preconditioner + auto targen settings performed compared to my typical choices.
Thanks for testing this (and I really appreciate the time and effort you put into these tests ). So it seems my choice of targen and preconditioning parameters work well, atleast on the display tested (I based most of the parameters roughly on what Graeme recommends in his excellent Argyll "Scenarios" guide, aswell as the targen parameters used in the first post of this thread). My hope is that this allows people to tap into the power of Argyll's sophisticated patch generator, with little configuration effort in DCG.

Last edited by fhoech; 03-27-2015 at 09:04 AM.
fhoech is offline  
post #3160 of 4398 Old 03-27-2015, 09:20 AM
AVS Forum Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 6,293
Mentioned: 86 Post(s)
Tagged: 0 Thread(s)
Quoted: 1314 Post(s)
Liked: 1043
Quote:
Originally Posted by fhoech View Post
My hope is that this allows people to tap into the power of Argyll's sophisticated patch generator, with little configuration effort in DCG.
Well you've done a great job at streamlining the whole process and your behind-the-scenes choices are good ones. Another tidbit out of the last round of testing was a comparison between relative and absolute with white point scaling linking. Even though my display was pre-calibrated to D65 at 100% the -iaw switch performed better.

Relative linking
Code:
% < 1.5% < 1.0
      99.6000      96.0000
dE00 avg,stdev,max,worst 10%
      0.41226702      0.26387419       1.7096775      0.99160210
Grayscale avg,stdev,max
      0.59467771      0.34061948       1.4649735
Red ramp avg,stdev,max
      0.42744775      0.21403045       1.0441158
Green ramp avg,stdev,max
      0.35370066      0.21686359      0.76892840
Blue ramp avg,stdev,max
      0.32615412      0.24309381       1.2243409
Relative in green:
zoyd is offline  
post #3161 of 4398 Old 03-27-2015, 09:36 AM
Advanced Member
 
fhoech's Avatar
 
Join Date: Apr 2013
Location: Stuttgart, Germany
Posts: 822
Mentioned: 31 Post(s)
Tagged: 0 Thread(s)
Quoted: 403 Post(s)
Liked: 262
Quote:
Originally Posted by zoyd View Post
Even though my display was pre-calibrated to D65 at 100% the -iaw switch performed better.
Interesting. Up to now, I basically went with Graeme's recommendation of relative colorimetric for the defaults in DCG, but with this result, I'm thinking of changing the default to abcol + wtpt scaling. Worst case I can think of right now is it performs as well as relcol, and best case is it performs better like in your case, and I currently can't think of any harm it could do. Will probably change the defaults in the next DCG snapshot update.
Pepelegal likes this.
fhoech is offline  
post #3162 of 4398 Old 03-27-2015, 10:36 AM
Member
 
Join Date: Nov 2014
Posts: 129
Mentioned: 4 Post(s)
Tagged: 0 Thread(s)
Quoted: 102 Post(s)
Liked: 25
Quote:
Originally Posted by fhoech View Post

That's a reasoanble way to do it. Just as a note, none of the default testcharts go over 121 grayscale steps, and there's a reason for that too: When using 20% dark region emphasis (like most of the "optimized for ..." patchsets), the maximum number of grayscale steps that'll still round to different RGB levels when quantized to 8 bits is 129 (assuming full range RGB encoding).
You're right. It's was my mistake, the original Massive test chart had only 120 patches on neutral, which I reduced to 80.

The maximum number of grayscale steps on 8 bits, shouldn't be 255? I'm sure I'm seeing this wrong, but grayscale is formed by a common value on all R,G and B (ie: 10,10,10 ; 16,16,16 ; 20,20,20 ....so on through 255,255,255). This should get 255 levels of grayscale.

But I guess the 129 has to do with the "20% optimized for"...

Quote:
Originally Posted by fhoech View Post
Seems like Argyll 1.7b isn't working right on your system (keep in mind it's a personal build of in-development beta code). I'd recommend going back to 1.6.3 for the time being.
I know. No problem with that, but I can't use Argyll 1.6.3 because of the problem with madTPG set window size
Pepelegal is offline  
post #3163 of 4398 Old 03-27-2015, 10:50 AM
Advanced Member
 
fhoech's Avatar
 
Join Date: Apr 2013
Location: Stuttgart, Germany
Posts: 822
Mentioned: 31 Post(s)
Tagged: 0 Thread(s)
Quoted: 403 Post(s)
Liked: 262
Quote:
Originally Posted by Pepelegal View Post
The maximum number of grayscale steps on 8 bits, shouldn't be 255? I'm sure I'm seeing this wrong, but grayscale is formed by a common value on all R,G and B (ie: 10,10,10 ; 16,16,16 ; 20,20,20 ....so on through 255,255,255). This should get 255 levels of grayscale.
There's the achievable number of digital levels, and the distribution of test points along the gray axis. You're right that the max number of achievable (not necessarily discernable, especially near black) digital levels in 8-bit is 255.
But when distributing test points, using dark region emphasis causes compression of the values at the low end (and expansion at the high end). Also, it would probably challenge the repeatability of display + instrument if you would use the full 255 test values along the gray axis even if not using dark region emphasis.

Quote:
Originally Posted by Pepelegal View Post
I know. No problem with that, but I can't use Argyll 1.6.3 because of the problem with madTPG set window size
When using Argyll CMS 1.6.3, it'll only influence patch size if using a perfectly black background in madTPG (because DCG 2.9.x graps the background level off of madTP, and then adds the respective dispcal/dispread -F parameter so the background level can be kept at the user set value). It should help to set background level slightly higher than zero (e.g. 1%) in madTPG before starting DCG.
anta1974 likes this.
fhoech is offline  
post #3164 of 4398 Old 03-27-2015, 10:59 AM
Member
 
Join Date: Nov 2014
Posts: 129
Mentioned: 4 Post(s)
Tagged: 0 Thread(s)
Quoted: 102 Post(s)
Liked: 25
Quote:
Originally Posted by fhoech View Post
There's the achievable number of digital levels, and the distribution of test points along the gray axis. You're right that the max number of achievable (not necessarily discernable, especially near black) digital levels in 8-bit is 255.
But when distributing test points, using dark region emphasis causes compression of the values at the low end (and expansion at the high end). Also, it would probably challenge the repeatability of display + instrument if you would use the full 255 test values along the gray axis even if not using dark region emphasis.
yes, I see your point.

Quote:
Originally Posted by fhoech View Post
When using Argyll CMS 1.6.3, it'll only influence patch size if using a perfectly black background in madTPG (because DCG 2.9.x graps the background level off of madTP, and then adds the respective dispcal/dispread -F parameter so the background level can be kept at the user set value). It should help to set background level slightly higher than zero (e.g. 1%) in madTPG before starting DCG.
Ok, I will try that.

Thank you fhoech
Pepelegal is offline  
post #3165 of 4398 Old 03-28-2015, 04:16 AM
Member
 
Join Date: Nov 2014
Posts: 129
Mentioned: 4 Post(s)
Tagged: 0 Thread(s)
Quoted: 102 Post(s)
Liked: 25
Yesterday, I changed to Argyll 1.6.3 and prepared to initiate a new profile with 2486 (Massive test with just 80 neutral patches).

I resized madTPG before and set its backgound to 1% dark. Unfortunately, even with just 1% dark, the border outside the internal area of measurment it's noticable, and when measuring the 0% black I could see the internal area pitch black and the surrounds greyed.

I canceled and started again this time with madTPG background set to 0%, and it worked
even the window size was kept between window creations.

I then let it do its work for the 2486 patches during the night.

This morning I had the popup to install the LUT showing this values:
peak err = 1.690947, avg err = 0.371527, RMS = 0.438181

Which are very similar to the ones had with my V3 version that worked.

Playing movies I didn't see any major artifacts too.

Link for the project folder: LINK

I also did run a Measurement Report (in project folder) with 493 patches and the Maximum ΔE*00 was 3.55 (on a kind of Blue pattern...)

So, for the exception of the Blue range (which I don't know what I can do to improve it) and the gamma curve that seems very erratic on the high end (as seen on Report) I think this is the best I probably can have.

Do you agree ?

Thank you.
Pepelegal is offline  
post #3166 of 4398 Old 03-28-2015, 05:45 AM
Advanced Member
 
fhoech's Avatar
 
Join Date: Apr 2013
Location: Stuttgart, Germany
Posts: 822
Mentioned: 31 Post(s)
Tagged: 0 Thread(s)
Quoted: 403 Post(s)
Liked: 262
Quote:
Originally Posted by Pepelegal View Post
Yesterday, I changed to Argyll 1.6.3 and prepared to initiate a new profile with 2486 (Massive test with just 80 neutral patches).
The logs clearly show 1.7b was used, but it's not an issue since this time it seems it ran through without hanging.

Quote:
Originally Posted by Pepelegal View Post
I resized madTPG before and set its backgound to 1% dark. Unfortunately, even with just 1% dark, the border outside the internal area of measurment it's noticable, and when measuring the 0% black I could see the internal area pitch black and the surrounds greyed.
1% gray backround shouldn't be problematic though.

Quote:
Originally Posted by Pepelegal View Post
This morning I had the popup to install the LUT showing this values:
peak err = 1.690947, avg err = 0.371527, RMS = 0.438181
Slightly lower peak than the V4 profile, and the tone response curves look smooth near black which I'd consider an improvement over V4.

Quote:
Originally Posted by Pepelegal View Post
Which are very similar to the ones had with my V3 version that worked.
Indeed.

Quote:
Originally Posted by Pepelegal View Post
Playing movies I didn't see any major artifacts too.
Gradients look very smooth through the LUT as well.

Quote:
Originally Posted by Pepelegal View Post
So, for the exception of the Blue range (which I don't know what I can do to improve it) and the gamma curve that seems very erratic on the high end (as seen on Report) I think this is the best I probably can have.
Saturated Rec. 709 blues are slightly out of gamut for your display, which you can do nothing about, but it isn't a big issue. 98% Rec. 709 coverage is a very good result.
Pepelegal likes this.
fhoech is offline  
post #3167 of 4398 Old 03-28-2015, 06:51 AM
AVS Forum Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 6,293
Mentioned: 86 Post(s)
Tagged: 0 Thread(s)
Quoted: 1314 Post(s)
Liked: 1043
@Pepelegal

CNET measured the blue primary x,y chromaticity for the EC9300 at 0.151, 0.08 and dE 6.36 so your meter is consistent with that[0.1566 , 0.076] and there is nothing else you can do to change it.
Pepelegal likes this.

Last edited by zoyd; 03-28-2015 at 06:57 AM.
zoyd is offline  
post #3168 of 4398 Old 03-28-2015, 11:39 AM
Member
 
baii's Avatar
 
Join Date: Jul 2013
Posts: 70
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 23 Post(s)
Liked: 16
What about displays(laptops/tablets) that can't be pre-calibrated to D65? (No OSD)

Back then I believe it was needed (for me) to set a target gamma curve so that it create calibration curves, then create 3dlut with vcgt tag to set thing right.
baii is online now  
post #3169 of 4398 Old 03-28-2015, 01:10 PM
Advanced Member
 
fhoech's Avatar
 
Join Date: Apr 2013
Location: Stuttgart, Germany
Posts: 822
Mentioned: 31 Post(s)
Tagged: 0 Thread(s)
Quoted: 403 Post(s)
Liked: 262
Quote:
Originally Posted by baii View Post
What about displays(laptops/tablets) that can't be pre-calibrated to D65? (No OSD)

Back then I believe it was needed (for me) to set a target gamma curve so that it create calibration curves, then create 3dlut with vcgt tag to set thing right.
Yes, I think that makes sense.
fhoech is offline  
post #3170 of 4398 Old 03-28-2015, 05:07 PM
AVS Forum Special Member
 
zoyd's Avatar
 
Join Date: Sep 2006
Location: Planet Dog
Posts: 6,293
Mentioned: 86 Post(s)
Tagged: 0 Thread(s)
Quoted: 1314 Post(s)
Liked: 1043
Ran a testchart from the options menu and the progress dialog stopped with errors messages (see below), the measurement completed fine though.

Code:
21:30:00,351 dispcalGUI: Starting interaction with subprocess
21:30:00,356 Number of patches = 750
21:30:00,357 Setting up the instrument
21:30:01,307 Product Name:      i1Display3
21:30:01,308 Serial Number:     OE-13.A-02
21:30:01,310 Firmware Version:  v1.01
21:30:01,312 Firmware Date:     12Apr11
21:30:06,458 Created MadVR window
21:30:07,278 Place instrument on test window.
21:30:07,286 dispcalGUI: Waiting for send buffer
21:30:07,351 dispcalGUI: Sending buffer: ' '
21:30:07,361 Hit Esc or Q to give up, any other key to continue:
21:30:10,564 Measured display update delay of 0 msec, using delay of 100 msec & 0 msec inst
21:30:10,567 reaction
21:30:15,657 Refresh rate = 59.994882 Hz, quantizing to 0.033336 msec
21:32:00,207 Traceback (most recent call last):
21:32:00,208   File
21:32:00,209 "C:\ProgramData\0install.net\implementations\sha1new=8c4f9609d3195274f7a51674479
21:32:00,210 5c6047e23feb8\dispcalGUI\worker.py",
21:32:00,212 line 6893, in progress_handler
21:32:00,214     lastmsg)
21:32:00,215   File
21:32:00,216 "C:\ProgramData\0install.net\implementations\sha1new=8c4f9609d3195274f7a51674479
21:32:00,216 5c6047e23feb8\dispcalGUI\wxwindows.py",
21:32:00,217 line 4566, in Update
21:32:00,218     self.gauge.Update(value, ms)
21:32:00,219   File
21:32:00,219 "C:\ProgramData\0install.net\implementations\sha1new=8c4f9609d3195274f7a51674479
21:32:00,220 5c6047e23feb8\dispcalGUI\wxwindows.py",
21:32:00,220 line 3898, in Update
21:32:00,222     raise Exception("ERROR:\n Gauge value must be between 0 and its range. ")
21:32:00,223 Exception: ERROR:
21:32:00,224  Gauge value must be between 0 and its range.
21:34:57,444 Traceback (most recent call last):
21:34:57,445   File
21:34:57,446 "C:\ProgramData\0install.net\implementations\sha1new=8c4f9609d3195274f7a51674479
21:34:57,447 5c6047e23feb8\dispcalGUI\wxwindows.py",
21:34:57,448 line 3834, in OnTimer
21:34:57,450     self._value[i] += self._update_step[i]
21:34:57,451 IndexError: list index out of range
21:35:26,247 Traceback (most recent call last):
21:35:26,250   File
21:35:26,250 "C:\ProgramData\0install.net\implementations\sha1new=8c4f9609d3195274f7a51674479
21:35:26,251 5c6047e23feb8\dispcalGUI\wxwindows.py",
21:35:26,252 line 3834, in OnTimer
21:35:26,253     self._value[i] += self._update_step[i]
21:35:26,254 IndexError: list index out of range
21:56:35,091 Patch 750 of 750
21:56:35,101 White drift was 0.221549 DE
21:56:35,106 The instrument can be removed from the screen.
21:56:35,269 Written 'madVR 2015-03-28 21 29 34 madvr_auto_verify.ti3'
21:56:35,391 dispcalGUI: Reached EOF (OK)
zoyd is offline  
post #3171 of 4398 Old 03-29-2015, 11:13 AM
Advanced Member
 
fhoech's Avatar
 
Join Date: Apr 2013
Location: Stuttgart, Germany
Posts: 822
Mentioned: 31 Post(s)
Tagged: 0 Thread(s)
Quoted: 403 Post(s)
Liked: 262
Quote:
Originally Posted by zoyd View Post
Ran a testchart from the options menu and the progress dialog stopped with errors messages (see below)
Hmm, that shouldn't happen. I've turned the exception into a warning (will only show in logs).

DCG 2.9.0.5 beta snapshot changes from 2.9.0.4:
  • Disabled adding -F parameter for dispcal/dispread when using 0% background level in madTPG if Argyll version is < 1.7b to prevent it from messing with the pattern area size
  • Changed default 3D LUT rendering intent to absolute colorimetric with white point scaling
  • Fixed saving video 1D LUT when using madTPG
  • Fixed sometimes wrong progress dialog placement
fhoech is offline  
post #3172 of 4398 Old 03-29-2015, 12:26 PM
Member
 
RajinderGill's Avatar
 
Join Date: Aug 2007
Posts: 38
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 21 Post(s)
Liked: 16
Hi Floech,

I know this may be a tall order: Would it be possible to add an option to "adjust" gamma from 1~3% in order to get some lift for earlier JVC projectors that come out of black very slowly? If one calibrates to BT.1886 using default or even 2.2, the gamma ends up a flat line and on my projector, I end up with flashing bars 17-19 being invisible to the eye. Adjusting brightness on the display does not really help and kills the contrast ratio. Spectracal are aware of this issue and actually have a function in Calman that writes directly to the projector between 1~3% to lift that side of the gamma curve without impacting everything else (they don't support all models unfortunately so I cannot make use of it). The lowest manually accessible value in the gamma editor menu for the end user is 5%, and lifting that lifts brightness at higher levels than required.

If there's anything you can suggest to help, or if some kind of gamma offset for bars 17-19 is feasible please help

-Raja
RajinderGill is offline  
post #3173 of 4398 Old 03-29-2015, 03:05 PM
Advanced Member
 
fhoech's Avatar
 
Join Date: Apr 2013
Location: Stuttgart, Germany
Posts: 822
Mentioned: 31 Post(s)
Tagged: 0 Thread(s)
Quoted: 403 Post(s)
Liked: 262
Quote:
Originally Posted by RajinderGill View Post
If one calibrates to BT.1886 using default or even 2.2, the gamma ends up a flat line and on my projector [...]
Hmm. That should only happen if the black level measures as zero, otherwise BT.1886 would have the properties you're looking for. Is that the case?
fhoech is offline  
post #3174 of 4398 Old 03-29-2015, 03:08 PM
Member
 
RajinderGill's Avatar
 
Join Date: Aug 2007
Posts: 38
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 21 Post(s)
Liked: 16
Yes, black is measuring as zero - it's below the threshold of what the i1D can measure.
RajinderGill is offline  
post #3175 of 4398 Old 03-29-2015, 03:26 PM
Advanced Member
 
fhoech's Avatar
 
Join Date: Apr 2013
Location: Stuttgart, Germany
Posts: 822
Mentioned: 31 Post(s)
Tagged: 0 Thread(s)
Quoted: 403 Post(s)
Liked: 262
Quote:
Originally Posted by RajinderGill View Post
Yes, black is measuring as zero - it's below the threshold of what the i1D can measure.
Try the following in the 3D LUT maker (not the 3D LUT tab as you can't set a custom source profile there):

  • Set source profile to the attached one. It is a synthetic profile with BT.1886-like transfer function, that has roughly a gamma of 2.0 at around 1% input level, goes through gamma 2.27 at around 10% input level and has an overall gamma of 2.35
  • Set tone curve to unmodified
  • Set target profile to the profile of your projector
Attached Files
File Type: zip Rec709_BT1886_100_0.005_BPC.icc.zip (2.6 KB, 34 views)
Pepelegal likes this.
fhoech is offline  
post #3176 of 4398 Old 03-30-2015, 02:49 AM
Member
 
RajinderGill's Avatar
 
Join Date: Aug 2007
Posts: 38
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 21 Post(s)
Liked: 16
Thanks so much - this definitely helps
RajinderGill is offline  
post #3177 of 4398 Old 03-30-2015, 09:10 AM
AVS Special Member
 
madshi's Avatar
 
Join Date: May 2005
Posts: 5,940
Mentioned: 26 Post(s)
Tagged: 0 Thread(s)
Quoted: 418 Post(s)
Liked: 421
FYI: The latest madVR v0.87.15 now has a 3dlut split screen functionality. You can activate it via keyboard shortcut (default Ctrl+Alt+Shift+3).
N3W813, |Tch0rT|, fhoech and 2 others like this.
madshi is online now  
post #3178 of 4398 Old 03-30-2015, 09:19 AM
Member
 
Francois76l's Avatar
 
Join Date: May 2014
Location: FRANCE
Posts: 197
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 77 Post(s)
Liked: 17
Great funtion Madshi, I was definitely looking for this!

HiFi:Nad C320BEE+Marantz CD-63 MkII-Ki Signature+Boston VR2+DIY cabling
HC:Onkyo TX-SR875+Boston VR2+CR8+VRC+Subwoofer MJ Acoustic Ref1 MKII
DISPLAYS:Panasonic P50ST50E/JVC DLA-X35 + HTPC (LAV+ffdshow+Avisynth+MPC-BE+MadVr)
SCREEN: Lumene Movie Palace Premium 240C + Dedicated room
Francois76l is offline  
post #3179 of 4398 Old 03-30-2015, 10:56 AM
Member
 
Francois76l's Avatar
 
Join Date: May 2014
Location: FRANCE
Posts: 197
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 77 Post(s)
Liked: 17
Quote:
Originally Posted by fhoech View Post
Try the following in the 3D LUT maker (not the 3D LUT tab as you can't set a custom source profile there):

  • Set source profile to the attached one. It is a synthetic profile with BT.1886-like transfer function, that has roughly a gamma of 2.0 at around 1% input level, goes through gamma 2.27 at around 10% input level and has an overall gamma of 2.35
  • Set tone curve to unmodified
  • Set target profile to the profile of your projector
Definitely have to try this custom profile!
I have exactly the same problem as RajinderGill. I have a JVC X35 with i1d3.
In fact all jvc owners (and maybe others projector manufacturers) calibrate with DispCalGui and i1d3 have the same "problem"
RajinderGill, what jvc model do you have?

fhoech, if the i1d3 is not accurate enough for blacks reading, what's the gamma we can expect at low ires with this custom profile?
Does it impact the gamma at higher ires?
Is it possible to have a profile for a pure power gamma curve 2.4 (ie 2.4 rel + 100% black output offset)

Thanks again!

HiFi:Nad C320BEE+Marantz CD-63 MkII-Ki Signature+Boston VR2+DIY cabling
HC:Onkyo TX-SR875+Boston VR2+CR8+VRC+Subwoofer MJ Acoustic Ref1 MKII
DISPLAYS:Panasonic P50ST50E/JVC DLA-X35 + HTPC (LAV+ffdshow+Avisynth+MPC-BE+MadVr)
SCREEN: Lumene Movie Palace Premium 240C + Dedicated room
Francois76l is offline  
post #3180 of 4398 Old 03-30-2015, 11:03 AM
Member
 
RajinderGill's Avatar
 
Join Date: Aug 2007
Posts: 38
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 21 Post(s)
Liked: 16
I have a DLA-HD990.

I don't like mentioning things like this but I made a small donation towards this software simply because it really is excellent. The kind of help we get from these guys is more than worth paying for.
fhoech and Francois76l like this.
RajinderGill is offline  
Sponsored Links
Advertisement
 
Reply Display Calibration

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