Web Audio API fails with MF_E_TOPO_CODEC_NOT_FOUND for WebM Vorbis

Fixed Issue #15935876

Details

Created
Feb 13, 2018
Privacy
This issue is public.
Found in build #
16.16299
Fixed in build #
17.17616
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

After installing “Web Media Extensions” from the Windows Store with Edge 16 (build 16299), WebM Vorbis based format can play with HTML5 audio, but not with the Web Audio API (via decodeAudioData()).

Repro URL: https://www.scirra.com/labs/audioCodecTests/

Steps to reproduce:

  1. Find the format (WebM Vorbis) to test in the list
  2. Verify “HTML5 audio support” says "probably", and that it can play with the audio element, indicating the format is supported
  3. Inspect the text after “Web Audio API decodeAudioData() support”

Observed result:
HTML5 audio indicates support (detected via canPlayType), and playback works with the audio element. However passing it to the Web Audio API’s decodeAudioData() method results in an EncodingError exception (MF_E_TOPO_CODEC_NOT_FOUND).

Expected result:
decodeAudioData() should be able to decode the same formats as the audio element.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brian B.”

      Changed Status to “Confirmed”

      Changed Title from “Web Audio API fails with MF_E_TOPO_CODEC_NOT_FOUND for WebM Vorbis” to “Web Audio API fails for WebM Vorbis”

      Changed Status from “Confirmed” to “In progress”

      Changed Title from “Web Audio API fails for WebM Vorbis” to “Web Audio API fails with MF_E_TOP_CODEC_NOT_FOUND for WebM Vorbis”

      Changed Status from “In progress” to “In code review”

      Changed Title from “Web Audio API fails with MF_E_TOP_CODEC_NOT_FOUND for WebM Vorbis” to “Web Audio API fails with MF_E_TOPO_CODEC_NOT_FOUND for WebM Vorbis”

      Changed Status from “In code review” to “Fixed”

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

    Sign in