reference.dashif.org - PlayReady doesn't work
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
People
(Reporter: 08xjcec48, Unassigned)
References
()
Details
Attachments
(1 file)
|
47.09 KB,
text/plain
|
Details |
Steps to reproduce:
I can't play this example PlayReady stream. It says DRM: No license server URL specified! in the console log.
Apparently that's because PlayReady isn't working at all for me regardless of whether media.eme.mfcdm.origin-filter.enabled is set to 1 or 2. media.eme.playready.enabled is set to true.
I've found this helpful page that checks for supported codecs and DRM capabilities: https://shaka-player-demo.appspot.com/support.html
Actual results:
I get these results with both stable Firefox and Nightly:
"com.microsoft.playready": null,
"com.microsoft.playready.hardware": null,
It works on Edge, though:
"com.microsoft.playready": {
"persistentState": true,
"encryptionSchemes": [
"cenc"
],
"videoRobustnessLevels": [],
"audioRobustnessLevels": [],
"minHdcpVersions": [
"1.0"
]
},
"com.microsoft.playready.hardware": {
"persistentState": true,
"encryptionSchemes": [
"cenc"
],
"videoRobustnessLevels": [],
"audioRobustnessLevels": [],
"minHdcpVersions": [
"1.0"
]
},
Expected results:
I use Window LTSC, but I don't think this is the issue since both Edge and PlayReadyWWA JS Sample can play test streams just fine.
Comment 1•1 year ago
|
||
I can play that example when media.eme.mfcdm.origin-filter.enabled=2. Can you check your about:support again? There should be a Content Decryption Modules Information field under the media section, it will show you whether you have the PlayReady support or not. Thanks!
"com.microsoft.playready": null,
"com.microsoft.playready.hardware": null,
We don't support those, we only support com.microsoft.playready.recommendation, com.microsoft.playready.recommendation.3000 and com.microsoft.playready.recommendation.3000.clearlead.
com.microsoft.playready.recommendation
{"persistent":"Required","distinctive":"Required","sessionType":"[]","codec":{"decodingAndDecrypting":[]}}
Clear Leader: No
HDCP 2.2 Compatible: Yes
com.microsoft.playready.recommendation.3000
{"persistent":"Required","distinctive":"Required","sessionType":"[Temporary,PersistentLicense]","codec":{"decodingAndDecrypting":["h264(cenc/cbcs)","hevc(cenc/cbcs)","av1(cenc/cbcs)","aac(cenc)"]}}
Clear Leader: No
HDCP 2.2 Compatible: No
com.microsoft.playready.recommendation.3000.clearlead
{"persistent":"Required","distinctive":"Required","sessionType":"[Temporary,PersistentLicense]","codec":{"decodingAndDecrypting":["h264(cenc)","hevc(cenc)","av1(cenc)","aac(cenc)"]}}
Clear Leader: Yes
HDCP 2.2 Compatible: No
Comment 3•1 year ago
|
||
Are you running Windows 10? Based on comment 2, it appears that SL3000 is supported on your system, but SL2000 is not. We explicitly disable SL2000 on Windows 10 due to a known process leakage issue in Media Foundation. Microsoft has addressed this issue in Windows 11, but they do not plan to backport the fix to Windows 10. If that’s the case, this bug will be marked as WONTFIX. (You will still retain SL3000 support on Windows 10.)
Yes, I'm on Windows 10. Does this mean that the dash.js sample stream uses only SL2000, and Microsoft hasn't disabled it for Edge?
If so, please ask the dash.js developers to add a warning on that page for users who run Firefox on Windows 10. People are learning about PlayReady support from the Firefox release notes and trying to use that page to test it.
Incidentally, can you point me to a working demo page where users can check if SL3000 is working with no Widevine fallback?
Comment 5•1 year ago
|
||
Does this mean that the dash.js sample stream uses only SL2000, and Microsoft hasn't disabled it for Edge?
Yes, I think so.
can you point me to a working demo page where users can check if SL3000 is working with no Widevine fallback?
We usually test SL3000 directly with the content providers, this is the only public working demo I can find. Please go to "PlayReady2" > "2.15 HEVC SL3000 (PR.rec)". Per the comment2, your device is able to play HEVC on SL3000, so it should work. But not all demo can work, some of them uses the key system we don't support. In addition, remember to set the pref media.eme.mfcdm.origin-filter.enabled to 2 first.
Description
•