PlayReady DRM Content Previously Supported on Edge 15 not working in Edge 16

Confirmed Issue #14593018

Details

Author
Ian B.
Created
Nov 9, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
16
Reports
Reported by 8 people

Sign in to watch or report this issue.

Steps to reproduce

Summary
PlayReady protected content that played successfully in Edge 15 no longer works in Edge 16. 

Reduced repro: https://s3.amazonaws.com/qa.jwplayer.com/~ian/edge-16-test.html

Notes
-Potentially related to open issue, reference ID 14554354
-Receiving error 3016 from Shaka:
The video element reported an error. 
error.data[0] is a MediaError code from the video element. 
On Edge & IE, error.data[1] is a Microsoft extended error code in hex. 

-Error.data[1] returns 80004003
-Error.data[0] returns error code 4, MEDIA_ERR_SRC_NOT_SUPPORTED

Reproduction Steps
Test Page: <redacted>

  1. Open this page in Edge 16.
  2. Wait a few seconds and the player will automatically display a {{Error loading media: File could not be played error}}.
  3. Open the same page in Edge 15 or IE 11.
  4. Witness the stream play properly.

Environment

  • Hardware/Device
    ** Lenovo Laptop / Browserstack
  • Operating System
    ** Windows 10 Fall Creators Update
  • Browser
    ** Edge 16
  • JW Player Version / URL
    ** 8.0.0 / <redacted> 

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Steps to Reproduce

      Changed Assigned To to “James M.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To to “Stephen E.”

    • Hello Ian,

      out of curiosity, what was the packager you are seeing the issue with? The same error started occuring for me with Edge 16 and IE on Fall Creators Update and PlayReady MPEG-DASH content generated by Wowza. However, for example MPEG-DASH PlayReady generated by mp4box is still fine.

      The issue is relevant to PlayReady with MPEG-DASH only as Smooth Streaming variant of the same PlayReady content plays fine from Wowza AND the same but unencrypted content works with MPEG-DASH as well. I cannot access mentioned issue #14554354. But from what I can see, it does not seem to be related directly to issue #12658991 as mentioned boxes from Wowza have “expected” order and a comment about removing clear section from the content in that ticket does not apply as well as Wowza is encrypting from the first frame.

      To reproduce with HTML5 and Silverlight player available here https://test.playready.microsoft.com/Home/Player and default license server https://test.playready.microsoft.com/service/rightsmanager.asmx?cfg=(persist:false,sl:150) :

      HTML5 & MPEG-DASH fails
      https://w01.quickmedia.tv/prtest/sample.mp4/manifest.mpd

      HTML5 & Smooth Streaming works
      https://w01.quickmedia.tv/prtest/sample.mp4/Manifest

      Decoding and decrypting in Silverlight on IE works with both protocols.

      Tomas

    • Microsoft Edge Team

      Changed Assigned To from “Stephen E.” to “Ramy W.”

      Changed Assigned To from “Ramy W.” to “Matthew H.”

    • I also have this issue with Edge 16 and IE on Fall Creators Update with YouTube Purchased Movies. It will give me the error “An error occurred. Please try again later.” I tried it on a different PC with Edge 15 and it works fine. Is there a workaround for Edge 16? The movies will play on Firefox just fine.

    • Microsoft Edge Team

      Changed Steps to Reproduce

      Changed Title from “PlayReady DRM Content Previously Supported on Edge 15 not working in Edge 16” to “PlayReady DRM Content with Key Rotation Previously Supported on Edge 15 not working in Edge 16”

      Changed Assigned To from “Matthew H.” to “David S.”

    • Since Microsoft Edge Team added the repro link back to the OP’s message, I now see that they are using Wowza as well.

      I believe that the issue is the same for both of us and that it stems from the sudden incompatibility between EdgeHTML 16 and how the content is packaged with PlayReady from Wowza. Therefore I feel that the changed title referring to key rotation might be misleading as there is no key rotation involved in our case. Our encryption key is static, because we are serving encrypted VoD content and not live.

      Can’t compare it with Youtube as another commenter added, but like I said previously, content encrypted with PlayReady in mp4box still works fine in EdgeHTML 16, so it probably is something on the box-parsing level.

      Tomas

    • The same issue is observed on our side with Playready protected streams from Wowza platform. In our case there is also no key rotation present which makes the original title of this issue more fitting.

      Would you have any update on what’s causing the issue; when this is expected to be resolved and if there may be some possible workarounds for this issue.

    • Microsoft Edge Team

      Changed Status to “Confirmed”

      Changed Title from “PlayReady DRM Content with Key Rotation Previously Supported on Edge 15 not working in Edge 16” to “PlayReady DRM Content Previously Supported on Edge 15 not working in Edge 16”

    • We are also experiencing problems using Wowza with playready on Edge. Any ETA on the fix?

    • Microsoft Edge Team

      Changed Status from “Confirmed” to “Confirmed”

    • Can we expect a fix from the Microsoft Edge team on this issue?

    You need to sign in to your Microsoft account to add a comment.

    Sign in