WebM Opus support not indicated & truncates audio file

External Issue #15043862

Details

Author
Ashley G.
Created
Dec 10, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
16.16299
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Repro URL: https://www.scirra.com/labs/audioCodecTests/
Note: “Web Media Extensions” are not installed.

The URL tests a range of audio formats with HTML5 audio, Web Audio, and MSE. Tested in Edge 16 (build 16299).

Steps to reproduce:

  1. Open the URL in Edge
  2. Play the WAV version of the sound effect, listen to how it sounds
  3. Scroll down to the “WebM Opus” section
  4. Observe “HTML5 audio support” line
  5. Try playing the WebM Opus sound with either HTML5 audio or Web Audio

Observed result:
a) HTML5 audio support says "no (empty string)", because canPlayType returned an empty string, indicating the format is not supported.
b) Playing the audio truncates the first section of the sound

Expected result:
a) canPlayType should return “maybe” or "probably", to indicate the format is supported
b) the format should decode properly, including the start of the sound, so it sounds similar to the WAV version (or WebM Opus playback in Chrome/Firefox).

Copied from Description when changed from Task to Bug

Copied from Repro Steps when changed from Bug to Task

Repro URL: https://www.scirra.com/labs/audioCodecTests/
Note: “Web Media Extensions” are not installed.

The URL tests a range of audio formats with HTML5 audio, Web Audio, and MSE. Tested in Edge 16 (build 16299).

Steps to reproduce:

  1. Open the URL in Edge
  2. Play the WAV version of the sound effect, listen to how it sounds
  3. Scroll down to the “WebM Opus” section
  4. Observe “HTML5 audio support” line
  5. Try playing the WebM Opus sound with either HTML5 audio or Web Audio

Observed result:
a) HTML5 audio support says "no (empty string)", because canPlayType returned an empty string, indicating the format is not supported.
b) Playing the audio truncates the first section of the sound

Expected result:
a) canPlayType should return “maybe” or "probably", to indicate the format is supported
b) the format should decode properly, including the start of the sound, so it sounds similar to the WAV version (or WebM Opus playback in Chrome/Firefox).

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Nishant N.”

      Changed Status to “External”

    • Hi again Ashley! I resolved this bug as duplicate of another bug that I fixed last night. The fix will be in the RS4 release. Thanks again for providing feedback - it was very helpful!

    • Awesome, thanks!

    • Changed Status from “External”

    • Hi Brian, I’ve tested Edge 17.17115 and the WebM Opus sample plays with HTML5 audio, but fails with decodeAudioData (EncodingError). Is it fixed but not in build 17115 yet, or does this need looking in to again?

    • I tested with 17.17120 and everything works fine now! So this can be closed, it’s all working as expected. I guess it just takes a while for fixes to reach the slow ring.

    • Microsoft Edge Team

      Changed Assigned To to “Gurpreet V.”

      Changed Assigned To from “Gurpreet V.” to “Angelo L.”

      Changed Steps to Reproduce

      Changed Assigned To from “Angelo L.” to “Gurpreet V.”

      Changed Status to “External”

    • Hello,

       

      Thank you for
      providing this information about the issue. We
      have confirmed the problem, and are considering a solution for a future build
      of Edge.
      We are resolving this issue as a duplicate of an existing
      feature request. We look forward to additional feedback you may have on how we
      can improve Microsoft Edge.

       

      Sincerely,

      The MS Edge Team

    • This issue has been resolved External. This means this issue may require a new feature to be implemented or other work that is more significant than a typical bug. You may be able to find more information on this issue by searching for related features on status.microsoftedge.com and uservoice.microsoftedge.com.

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

    Sign in