media: Add more labels for PlayReady HRESULT in UMA Some HRESULT error codes reported for Media.MediaFoundationRenderer.PlaybackError are not labeled. This makes investigation harder. So added labels for those error codes. Source: - https://github.com/tpn/winsdk-10/blob/master/Include/10.0.16299.0/winrt/Windows.Media.Protection.PlayReadyResults.h - https://github.com/tpn/winsdk-10/blob/master/Include/10.0.14393.0/winrt/Windows.Media.Protection.PlayReadyErrors.h - \third_party\depot_tools\win_toolchain\vs_files\e4305f407e\Windows Kits\10\Include\10.0.26100.0\winrt\Windows.Media.Protection.PlayReady*.h ``` /* * MessageId: MSPR_E_INVALID_H264_CONTENT * Message Meaning: * The H264 content's slice headers are invalid and playback cannot continue. * Hex Value: 0x8004B8C2 */ /* * MessageId: DRM_E_TEE_PROXY_INVALID_SERIALIZATION_MESSAGE * * MessageText: * * Invalid TEE proxy serialization message. * */ /* * MessageId: MSPR_E_AES_SIXTEEN_BYTE_IVS_NOT_SUPPORTED * Message Meaning: * The content uses AES with sixteen byte IVs, but this is not supported. * Hex Value: 0x8004B8D2 */ ``` Bug: 448167528 Change-Id: I119ae15fc20559965323c1751f127bcc2028c9a5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7038377 Reviewed-by: Vikram Pasupathy <vpasupathy@chromium.org> Reviewed-by: Piet Schouten <Piet.Schouten@microsoft.com> Commit-Queue: Sangbaek Park <sangbaekpark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1529075}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.