Quote
Thanks for the clarification. However, how does your scenario pan out when you have a graphics card with it's own HDMI or DisplayPort connector. In that case, it seems like the motherboard is out of the loop since the traffic goes from the software to the buss to the high end GPU.
That being said, there is a path from the UHD BD drive through BIOS to the buss through the chipset. Does that play into the completion of the entire path from media to display, or not?
Thanks for the clarification. However, how does your scenario pan out when you have a graphics card with it's own HDMI or DisplayPort connector. In that case, it seems like the motherboard is out of the loop since the traffic goes from the software to the buss to the high end GPU.
That being said, there is a path from the UHD BD drive through BIOS to the buss through the chipset. Does that play into the completion of the entire path from media to display, or not?
Yes. you're right. If for the discrete GPU case, the HDCP 2.2/HDR/HDMI 2.0a features are implemented by the discrete GPU.
So when NV/AMD GPU can support UHDBD, then mainboard is not required for HDCP 2.2/HDR 10/HDMI 2.0a.
But so far there's no discrete GPU that supports UHD-BD. I guess CyberLink is still trying hard to persuade NV/AMD to work with them to come up a solution.
UHD-BD DRM requirement not only requires HDCP 2.2, if you take a look at the AACS2 License agreement, you'll see there're far more requirements that need to be meet. For example, they need kernel mode processing, they need to protect the screen from being captured by 3rd party screen recorders, etc. These requires support from NV/AMDs, CyberLink can't make it on their own.
This message was edited 1 time. Last update was at Apr 24. 2017 21:51