I have a laptop with HDMI output that can be set to output YCbCr444, which I assume is video (legal) level. If I generate a profile from the new patches using this video level source, why do I have to apply video scaling to the resulting LUT if using an eeColor box? Is it preferred to output PC levels, do the profile and subsequent LUT, and then do the video scaling? If so, why? Can someone explain this?

I also have a question relating to when the video scaling is done. I have always done it last, after applying any of the filters. Is this the proper way to do this?

There is no guarantee YCbCr444 is video level...
That is something you will have to verify for yourself.
This is actually true of ALL formats.

Profiling also has to be the same levels as the image path - TV legal or data.
It is critical you get that right.
(Most monitors/graphics cards do the rescaling automatically using EDID)

If the image path is video level you will need to use the VideoScale function on the LUT before exporting.
And yes, it should be done after all other functions.

Steve

Hi Steve,

I was actually emailing with Ted today with basically the same question. I had the same concern as the original poster. My display only properly supports 16-235. If I am using Ted's disk with my PS3, the patterns are 16-235 and being output 16-235 and being measured by LS. I can also output 16-235 via hdmi out of my laptop which means if i am using the internal LS patterns which i know are 0-255 they are being sent to LS as 16-235 and being measured as such. He stated that the video scale function would still need to be used in both these cases since LS always thinks/assumes the patterns are 0-255 regardless of what LS is actually measuring. He stated that the video scale function has to be completed no matter what when using the eecolor box. So i am assuming every single lut that LS creates is 0-255 no matter what patterns are being fed and that is why video scale always needs to be used?

No, the VideoScale function is to overcome a 'problem' (or rather a limitation in the way it works) in the eeColor box - it has NOTHING to do with the patch levels within LightSpace!

LightSpace is totally agnostic to Data/TV Legal levels...

Steve

Gotcha, thanks.