An issue was raised recently on the CEDIA Community Forum concerning 4K content which either doesn’t work or flashes on and off when used through an HDMI splitter, questioning whether HDCP 2.2 is stable and governed by a standard.
HDCP 2.2 should be very stable and seamless, but is reliant on a quality link to ensure things go smoothly. Kind of sounds obvious, huh? HDCP 2.2 uses tougher security and a different continuous check system throughout transmission than was used in HDCP 1.x (version 1.3 or 1.4), making link quality even more important. But since you’re wanting to push at least double the bandwidth down the pipe for 4K, the use of high quality connectivity is already considered a best practice.
As for whether HDCP 2.2 is officially specified, the answer is yes. There are actually seven separate specifications for HDCP 2.2; one catch-all version, plus six others for specific interfaces including HDMI. Contrary to popular belief, HDCP 2.2 interfaces seamlessly with HDCP 1.x, the older copy protection system used for 1080p and below.
Every link between devices in a system authenticates separately. For example, an Ultra HD Blu-ray player which is HDCP 2.2 connected to an AV receiver will always try to authenticate using HDCP 2.2. If it fails, perhaps because the AV receiver doesn’t support 2.2, it will fall back to HDCP 1.x to establish a successful link. Most 4K content is flagged with a “Stream Type” bit – Type 1 requires mandatory HDCP 2.2 and will not pass over an HDCP 1.x link, whereas Type 0 can pass over any version of HDCP. All 1080p content is type 0.
The output side of the AV receiver will establish a separate authenticated link with the next device downstream, resulting in either HDCP 2.2 or 1.x depending on the two devices’ capabilities. However, the source continues to manage the content at all times.
Regarding the challenge of 4K content failing, or appearing unstable or intermittent, this really comes down to link integrity or HDCP 2.2 protocol issues. Link integrity means the whole signal path including device circuits and cabling, with just as much importance on the high speed AV channels as on the “slow” auxiliaries. 4K needs a lot more bandwidth than 1080p- two to four times more in fact. Keep in mind that losses can be cumulative; the longer the HDMI cables, and more hops and complexity in the system, the more chance of things going wrong and the harder the issue becomes to diagnose. The DDC wires in HDMI carry the EDID (Extended Display Identification Data) from TV to source, but they also handle all the HDCP authentication as well, and once established are responsible for the “Link Integrity Check” to monitor the successful decryption of content at the display. Simply put: Bad link = shaky result.
HDCP 2.2 Protocol
There’s a few separate considerations here:
- System size – HDCP 2.2 is limited to 32 devices over four repeater levels. That means the source device, four repeater levels (switcher, splitter, AV receiver, audio breakout/embed, etc.) and then the display.
- Locality Check - During authentication a ping sent by the source requires a round-trip response time less than 20ms across the whole system – which shouldn’t really be an issue in HDMI & HDBaseT systems as this check is really designed to exclude WAN applications.
NOTE: HDMI 2.1 was announced in Nov 2017, allowing for 8K & 10K video. With it HDCP 2.2 will become even more widespread, but there’s no change to how it works.
David Meyer is the CEDIA® Director of Technical Curriculum. For more advice on topics like this one, check out the Online Community
-- it's free for members.