Originally Posted by docker2
Darn, that prompts even more questions:
1) How can I determine whether or not my HDMI data is being output correctly?
I usually end up trusting my eyes with known good sources. I route all but my Sky box through an AV amp to the same HDMI input - so calibrate the display against a known-good HDMI source (usually my standalone Blu-ray player), and then make sure my HTPC matches it and isn't horribly crushed or sat-up.
2) I calibrated my HDTV's greyscale using 10-step IRE patterns from my MacBook Pro running Windows 7, outputting over ThunderBolt to HDMI adapter. If the HDMI data isn't being sent as limited range, will this have messed with my calibration?
Possibly... Beware as well that different video players will do different things with 16-235 sources. Some try to 'help' by doing stuff outside the domain of the drivers.
I use a Video Essentials Blu-ray for line-up usually - as well as a recording of the BBC HD Test Signal. I chose my player app, look at the configs in that for level space, and also look at the driver configs. There have been longstanding issues with some drivers in that they say one thing and do another. Similarly there was a major problem with how Windows Media Center coped with 16-235 content (you could end up with very washed out pictures as it tried to 'help') though there are registry settings (sometimes for drivers, sometimes for Win MC - depends on the setup) to sort this.
Haven't done it for a while to be honest - but there certainly were issues between HD and SD content (so you could get SD right and HD crushed, or HD right and SD sat-up in one situation)
Also - the set-up could switch depend on whether you're booted into Windows or OS X on your Mac - as the driver settings will potentially be different between OSs. (IME Macs are better at this though - as they are used every day in video editing 16-235 stuff)
It's REALLY annoying that even though 16-235 levelspace has been a standard since the very early 80s - and is used instead of 0-255 for very good engineering reasons (it avoids ringing caused by clipped overshoots and undershoots and accepts that analogue processes - and lots of broadcast TV signals still have analogue stages even in HD - are not perfect) - the handling of 16-235 video in Windows and PC drivers is woeful at times.