The AVS-HD (et. al.) disks were encoded with the assumption that "video" levels are being used. Period. One should *not* being using "PC" levels to display sources encoded with "video" levels. Period.This, I don't understand. What is the point of keeping track of expected luminance targets based on differential encoding of patterns if the end result is not to obtain similar calibrations using any of the supported test pattern sources? Let's say we know that 40% gray on AVS709 actually translates to 39% (for simplicity sake) in PC Levels due to the way it is encoded. If HCFR supports AVS709 and is aware of the way it is encoded (which it does), then shouldn't it internally determine the luminance target assuming this is a 39% gray pattern, not a 40% Gray pattern? That way, you have a much better chance of tracking correctly when switching between AVS709 and the HCFR or madTPG pattern sources. My guess is that perhaps it does this correctly for video levels and that using AVS709 v/s HCFR pattern for video levels would result in the same curve, but I have no way of testing it myself.
If you want to calibrate to "PC" levels you need to use a source pattern that was encoded at PC levels ... It should be simple to construct these targets yourself with any PC "paint" or photoshop-type program.
PS: In my earlier post, when I said "luminance level(s)," I really meant "video/stimulus" level.