-
Notifications
You must be signed in to change notification settings - Fork 469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
widevine: Breaking manifest change (VP9 version string) with v4.10.2209.0 #3138
Comments
widevine: Fix VP9 version string for v4.10.2209.0 (fixes issue #3138) → <<cset b7ef08ca84cb (bb)>> |
|
widevine: Fix VP9 version string for v4.10.2209.0 (fixes issue #3138) → <<cset ad7b8d9a08a0 (bb)>> |
widevine: Fix VP9 version string for v4.10.2209.0 (fixes issue #3138) → <<cset 18455833f1dc (bb)>> |
robincarlisle
pushed a commit
to robincarlisle/cef
that referenced
this issue
Apr 28, 2023
filipnavara
pushed a commit
to emclient/cef
that referenced
this issue
Dec 26, 2023
filipnavara
pushed a commit
to emclient/cef
that referenced
this issue
Dec 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original report by me.
Widevine CDM version 4.10.2209.0 is required starting May 31st (see attachment). This version of the CDM includes a manifest change that is incompatible with current CEF manifest parsing logic:
The temporary workaround is to rewrite the manifest file to use the currently supported version string (e.g.
vp09
=>vp9.0
).The longer-term fix is to update the code in CEF to support the more robust manifest parsing logic that now exists in Chromium.
The text was updated successfully, but these errors were encountered: