Skip to content

Conversation

@cjrog
Copy link
Contributor

@cjrog cjrog commented Apr 24, 2025

Update docs after support has been added for the -clearlead suffix starting in Windows 10 OS Build 19045.5796 and later.

This support has been backported from Windows 11 to support clearlead with HWDRM on Windows 10.

Update docs after support has been added for the -clearlead suffix starting in Windows 10 OS Build 19045.5796 and later.
@prmerger-automator
Copy link

@cjrog : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@riverar
Copy link
Contributor

riverar commented Apr 29, 2025

Says who?

|4 |Output Protection|hdcp |0 (off), 1 (on without HDCP 2.2 Type 1 restriction), 2 (on with HDCP 2.2 Type 1 restriction |Do all intersecting enabled displays support at least the request protection level? |Y |
|5 |General: Efficiency<sup>**</sup>|efficiency-setting |0 (off = no restriction), 1 (on = limit resolution when on battery power) |Does the user want battery life, streaming overhead, and/or download speed in preference to highest resolution?<sup>****</sup> |Y |
|6a |Decryption|encryption-type |“cenc” or “cbcs”, with optional "-clearlead" suffix. |Is this encryption type supported for decryption with the specified codec / key-system? If value is unspecified, default value of "cenc" is used. Starting with Windows Build 22621, the suffix "-clearlead" is supported. When "-clearlead" is appended to the encryption type value, support for using clear content at the very beginning of encrypted content is also requested. Clear content at the beginning of the content speeds up the time to presenting the first frame. If "-clearlead" is added to the encryption-type, the version number of the requested codec will be checked. The AV1 and VP9 codecs will be checked for major version 2, and HEVC will be checked for v2.0.53421 or greater. |N |
|6a |Decryption|encryption-type |“cenc” or “cbcs”, with optional "-clearlead" suffix. |Is this encryption type supported for decryption with the specified codec / key-system? If value is unspecified, default value of "cenc" is used. Starting with Windows 11 Build 22621 and Windows 10 Build 19045.5796 or later, the suffix "-clearlead" is supported. When "-clearlead" is appended to the encryption type value, support for using clear content at the very beginning of encrypted content is also requested. Clear content at the beginning of the content speeds up the time to presenting the first frame. If "-clearlead" is added to the encryption-type, the version number of the requested codec will be checked. The AV1 and VP9 codecs will be checked for major version 2, and HEVC will be checked for v2.0.53421 or greater. |N |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is verified to be true, we should probably flip the versioning to read more naturally here:

Suggested change
|6a |Decryption|encryption-type |“cenc” or “cbcs”, with optional "-clearlead" suffix. |Is this encryption type supported for decryption with the specified codec / key-system? If value is unspecified, default value of "cenc" is used. Starting with Windows 11 Build 22621 and Windows 10 Build 19045.5796 or later, the suffix "-clearlead" is supported. When "-clearlead" is appended to the encryption type value, support for using clear content at the very beginning of encrypted content is also requested. Clear content at the beginning of the content speeds up the time to presenting the first frame. If "-clearlead" is added to the encryption-type, the version number of the requested codec will be checked. The AV1 and VP9 codecs will be checked for major version 2, and HEVC will be checked for v2.0.53421 or greater. |N |
|6a |Decryption|encryption-type |“cenc” or “cbcs”, with optional "-clearlead" suffix. |Is this encryption type supported for decryption with the specified codec / key-system? If value is unspecified, default value of "cenc" is used. The "-clearlead" suffix is supported in Windows 10 (build 19045.5796 or later) and in Windows 11 (build 22621 or later). When "-clearlead" is appended to the encryption type value, support for using clear content at the very beginning of encrypted content is also requested. Clear content at the beginning of the content speeds up the time to presenting the first frame. If "-clearlead" is added to the encryption-type, the version number of the requested codec will be checked. The AV1 and VP9 codecs will be checked for major version 2, and HEVC will be checked for v2.0.53421 or greater. |N |

@drewbatgit drewbatgit merged commit f86bd3c into MicrosoftDocs:docs Apr 29, 2025
1 check passed
@riverar
Copy link
Contributor

riverar commented Apr 29, 2025

@drewbatgit What about the edits suggested above?

@drewbatgit
Copy link
Contributor

@riverar The existing wording matches our conventions in the documentation, so your suggested change was not adopted. "Reading naturally" is a subjective assessment. So, while we can't please everyone, we try to use consistent phrasing for things like this.

@riverar
Copy link
Contributor

riverar commented Apr 29, 2025

I find it very hard to believe that a backwards range of Windows versions matches any conventions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants