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}
1 file changed
tree: 4dfd61359925ad43d4a465016e905da38d2e2f3f
  1. .gemini/
  2. .github/
  3. agents/
  4. android_webview/
  5. apps/
  6. ash/
  7. base/
  8. build/
  9. build_overrides/
  10. buildtools/
  11. cc/
  12. chrome/
  13. chromecast/
  14. chromeos/
  15. codelabs/
  16. components/
  17. content/
  18. crypto/
  19. dbus/
  20. device/
  21. docs/
  22. extensions/
  23. fuchsia_web/
  24. gin/
  25. google_apis/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. net/
  34. pdf/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .cursorignore
  54. .geminiignore
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. CRYPTO_OWNERS
  72. DEPS
  73. DIR_METADATA
  74. LICENSE
  75. LICENSE.chromium_os
  76. OWNERS
  77. PRESUBMIT.py
  78. PRESUBMIT_test.py
  79. PRESUBMIT_test_mocks.py
  80. README.md
  81. SECURITY_OWNERS
  82. WATCHLISTS
README.md

Logo Chromium

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.