Hi Mike, the User Guide can be downloaded fro the eeColor page of the website.

Have a look - I'm out of the office at the moment...

;)

Steve

Steve,

I downloaded and looked through the "TruVue eeColor Application User Guide.pdf" (Revision 10.0 / March 14, 2011), I did not find the statement you made 3 posts ago... I also did not find any additional information regarding max bitrate support... I just contacted them directly, I'll post here if they answer...

Also, wanted to ask you: Can you post the display manufacturers that currently support LightSpace CMS via Direct Display calibration ?

You mentioned Penta (already added LS support) and FSI (currently adding LS support)... Anybody else ?

Thanks.

- M

Last paragraph of last page...

The only display manufacturer that presently uses LightSpace CMS for internal calibration is the Penta.
The old Cine-tal did as well.

FSI are working on it, as are iKan and Small HD.

Steve

hah ! you referred to the guide on YOUR website, while I was looking at the old, outdated guide on eeColor.com..

Anyways, as the guide states and as Thomas from eeColor who just got back to me confirmed: it is 10-bit @ 1080p - he has a HP DC and will test if output is progressive RGB, so that the DC displays 10-bit...

I will update.

Thanks.

- M

We tried to do calibration (without the Lighillusion software but does not matter) with special patch in order to help the monitor when changing patch to avoid the automatic gain from kicking in.

We build a set of graypatch that cover only a small portion of the screen and we where using the CS200 minolta that can have a very small area of measurement, then around that graypatch we tried with a 75% gray field and keep that uniform. That helped to minimize the automatic gain having most of the field a uniform brightness.. I think we tried a 50% as well but I do not remember.

That improved the situation a bit.

i do not know with broad reading probes if this is doable.

Walter

We have developed a process of using a grey ramp image to calculate the ideal patch size for any given plasma, as different display have different requirements.

Use a Grey-scale Ramp image.

Then measure the overall brightness of the screen (with the probe covering all the screen - moving back and forward to get the peak reading).
Just looking for Luma not colour readings.
Then make a calibration patch window with 50% white and size it to get a similar Luma reading with the probe in the same place.
Use that patch size for the profiling (moving the probe to the correct distance for the patch size).

There is some discussion the best profiling to use - Quick Profile or a Full Profile.
Both can work, but after a LOT of testing we do now see benefit with a Full 17 point cube.

Steve

Steve

Hi Steve,

When you say measure overall brightness of the screen using a grey scale ramp, what does that exactly mean?. I'm trying to figure out what you have meant but finding it a bit difficult to do so. How do you measure peak value other than putting the probe at the right corner of the screen with a grey-scale ramp? I can't see the relationship between the overall brightness and the grey-scale ramp and then measuring the peak value going back and forward..


I've tried calibrating my Panasonic BT300 plasma using 17pt & 10pt profiling. After loading the 3D LUT my blacks gets crushed. Any idea why?

Cheers.

Din

Hi Din,

Put the grey ramp image up on the screen and make sure the probe is covering/measuring as much of the image as possible.
This will give you the average brightness value.

Then make a standard 50% white patch the size needed to replicate the value.
This gives you the best size patch, and has nothing to do with the 'peak' value.

Then profile the screen as normal.

As for the LUTs crushing, you are probably doing something wrong.

Bets to send me the .bcs file (the profile data) to look at.

Steve

Steve

Steve,

I get it. So you meant average reading when you said 'peak reading'?

Do I calculate average value manually? As in do the math while noting down the values and dividing by the number of readings or is there a setting on LS CMS to do it automatically?

Will email you the profile data. I'm sure I'm doing something wrong...

Thanks

Din

No, I mean the 'peak' reading from the probe when measuring the whole of the ramp image.
That is the 'peak' value from the probe with the ramp displayed, and has nothing for a the peak from the probe when measuring 'white'.

Make sense?

This 'peak' reading is then the average for the ramp image, which is what you want.

Steve

Steve

Hi Steve,

I think I understand but still a bit confused. When the grey ramp is on the display, isn't the right most area going to give you the 'peak' reading? I understand that by using a grey ramp you're trying to get a reading of average peak brightness and do see the relationship between the final white patch size. But still don't understand why you have to take readings from all over the screen as the peak reading for the grey ramp is going to be on the right side..

This is the confusing bit...

Din

Ah - I see what you mean.

But no, as you are measuring the whole ramp image you are looking at the average peak reading.
Moving the probe further away from the screen will eventually read lower values as you will be reading outside the ramp image, so you need to get a bit closer... the average 'peak' reading is to get the correct distance from the screen.

If you are only measuring a section of the ramp image your are doing things wrong...

Hi All,

I have a pana th 42 bt300er. I am measuring a tiny area from 60cm distance with a jeti 1211 and the average low light function.using the resulting quick profile for remeasure I gives a 99% result. Wasn't able to get my notebook to show the 3D cube, but the graphs look good.
Does this make sense?

Btw, I get also a 99% with an eizo cg243w, but in comparison the pana has a pink and the eizo a green cast to it. I read someone had spoke of this pink cast as well. Schouldn't 2 displays with a 99% 64-Lut look alike?
Thanks,
Nepomuk

99% is what I would expect. The final 1% is just about impossible to get due simple to the maths functions being used.

If you measure the same patch colour (grey) on both displays what colour value do you get?
Does the probe see the colour cast variation?
It may be you are at the limit of different display technology and probe combination.

And what do you mean you couldn't see the 3D cube?
That's not right, and is something I've never heard of before.

Steve

Hi Steve,

measuring 127 grey:
plasma (native, temp set to warm, which is closest): x:0,3131; y:0,326
(bit jumpy)

cg243w: x:0,3124: y: 0,328
(perfectly stable)

My eyes see the difference clearly. Well the spectra a very different and a mess! No wonder. The spectrum of the plasma is much simpler, so more to trust? Red is probably not reference level because it consists of 2 peaks, one at 620 and 700 nm.

My x-series thinkpad, I run lightspace on, has a mobile intel 965 express chipset for the graphics. Probably not compatible to lightspace's 3d? Driver says it can gl, and directx is also installed.

Thanks,
Nepo