How can we improve the Microsoft Edge developer experience?

Ogg Vorbis and Opus audio formats support [Firefox and Chrome support it]

Ogg Vorbis and Opus are free and open-source audio codecs with great quality. They are developed by Xiph.Org Foundation and IETF.

Opus codec provides the best quality (latest listening tests: http://listening-test.coresv.net/results.htm for 96 kbps and http://listening-tests.hydrogenaud.io/igorc/results.html for 64 kbps) and very low latency (http://opus-codec.com/comparison/ ). More information: http://en.wikipedia.org/wiki/Opus_%28audio_format%29 . Support status: http://caniuse.com/#search=opus .

Ogg Vorbis also provides good quality. It is an old audio format and you can find many of Ogg Vorbis files in the web. Ogg Vorbis is very popular in the Linux world. More information: http://en.wikipedia.org/wiki/Vorbis and http://vorbis.com/ . Support status: http://caniuse.com/#search=ogg .

6,058 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Evgeny Vrublevsky (VEG)Evgeny Vrublevsky (VEG) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    37 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • damastadamasta commented  ·   ·  Flag as inappropriate

        Ogg container with opus and vorbis codec support are the 6. and 7. most voted for features for Edge on uservoice. Please do not continue to ignore these requests. And please don't forget Edge on Mobile. For a mobile device, It is an excellent browser and handles other video and audio brilliantly. Streaming h.264 or h.265 to the recent Lumias is super energy efficient - 45 minutes of full-HD only "cost" about 15% battery on my 950XL. If that could be extended to truly open HTML5 standards, edge would seriously rock.

      • Evgeny Vrublevsky (VEG)Evgeny Vrublevsky (VEG) commented  ·   ·  Flag as inappropriate

        This ticket is about Ogg Vorbis and (Ogg) Opus. It means that support of the Ogg container is mandatory. Support of this container requires just a small amount of code. It worth almost nothing to support it. Just please!

      • TonyTony commented  ·   ·  Flag as inappropriate

        I would like to see Opus & .wav audio-tag support added to IE11 - which is a surprisingly good browser now (for both user and web-developer).

        Microsoft & IBM developed the .wav format, so licensing should not be a problem. It may not be optimal for the web but we use.wav for telephone announcements and we cannot use other formats (external dependency). To find that FF & Chrome can support .wav but IE11 cannot is both disappointing and frustrating.

      • Evgeny Vrublevsky (VEG)Evgeny Vrublevsky (VEG) commented  ·   ·  Flag as inappropriate

        Thomas Ruecker, I'm the author of this ticket and I meant support of the Ogg Vorbis and Opus in the <audio> tag. It is absolutely useless for a general web-developer when it is supported only for WebRTC connections.

      • Alice WonderAlice Wonder commented  ·   ·  Flag as inappropriate

        I wonder if Opus plays in Edge now if put in a mkv container and called WebM? I seem to recall that if you installed the fluendo codecs in Win 7 and WebM support in IE in Windows 7 that you could get it to play Ogg Vorbis that way.

      • Alice WonderAlice Wonder commented  ·   ·  Flag as inappropriate

        Hi, I would not object to Ogg Vorbis support but Ogg Opus is what I really want to see supported.

        I run a website that provides audios (spoken content) and I do use HE-AAC which allows for considerable compression but Ogg Opus provides for even better compression at the same audio quality.

        Where bandwidth isn't an issue it doesn't matter, but for users who either pay for bandwidth or who have poor Internet connections, the smaller file size of Ogg Opus is a benefit to them. Right now they can get that using Chrome or FireFox but if Edge is the browser they prefer, I believe they should be able to get it in Edge too.

      • Thomas Ruecker (TBR)Thomas Ruecker (TBR) commented  ·   ·  Flag as inappropriate

        Evgeny, as much as I want to see Ogg support, I have to defend them on this one.

        They only implemented the Opus codec, not the Ogg container. Probably to just get WebRTC working better. There Opus is sent unencapsulated as real time VoIP data.

        So, yes, those files won't play, until they also implement Ogg container support. Let's hope, that this will happen soon. Then proper and full Opus support will be possible.

      • Evgeny VrublevskyEvgeny Vrublevsky commented  ·   ·  Flag as inappropriate

        Good news, thanks! Please don't forget about the Ogg Vorbis support. This format is very popular on the Wikipedia, for example.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Would the support be extended to the Operating System also? I can't see to get any metadata via explorer.

      • Thomas Ruecker (TBR)Thomas Ruecker (TBR) commented  ·   ·  Flag as inappropriate

        As commented on the other Ogg suggestion. Please pay attention to Ogg Chaining (Page 4 of RFC 3533).
        This also affects Opus audio files and streams.

      • Techie007Techie007 commented  ·   ·  Flag as inappropriate

        Oh great! I wasn't sure if Microsoft was going to do this. They are even planning to support Vorbis. This is exciting! With the latest improvements in HTML5 support in Edge over the last week, it looks like Microsoft may actually be serious about competing at the level of Chrome and Firefox.

        @Jay Tuckey: They are doing exactly that:
        Opus support reads "Roadmap priority: High — We intend to begin development soon", while
        Vorbis support reads "Roadmap priority: Medium — Development is likely for a future release."

      • Jay TuckeyJay Tuckey commented  ·   ·  Flag as inappropriate

        Please prioritize opus over vorbis. Opus will be used much more in the future, and people can transcode from vorbis to ogg to get support in IE.

      • Ivan PrivaciIvan Privaci commented  ·   ·  Flag as inappropriate

        This is excellent news, and will make legally-free top-quality audio available on around 90% of web-browsers, I believe.

        I wonder about this though: http://dev.modern.ie/platform/status/oggcontainer/

        It says low priority and no development. ".opus" is opus-in-ogg. What's the plan here? "WebM Audio" (which I've never encountered "in the wild" except for a single test file I made myself)?

        (Personally, I *much* prefer ogg's more flexible and simple metadata - webm has the same "70 or so special little differently formatted binary fields" limitation going on that mp3's "IDv2" does. I think .ogg is hypothetically better for streaming, too, but I'm not certain about that.)

      • ZeekZeek commented  ·   ·  Flag as inappropriate

        Well done. But more importantly: we need .WAV support too - .wav is a Microsoft/IBM format after all! Although not compressed, it is what our external hardware requires us to manage. To have this supported by most browsers but not supported by Microsoft IE is frustrating and incomprehensible.

        Perhaps intended to prop up/force use of Microsoft Media Player, which is poorly integrated & therefore impractical for us to support for external customers.

      ← Previous 1

      Feedback and Knowledge Base