Broader OGG support is now in development: https://developer.microsoft.com/en-us/microsoft-edge/platform/status/oggcontainer/
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.
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.
WebM is in development – http://dev.modern.ie/platform/status/webmcontainer/
OGG support is now in development: https://developer.microsoft.com/en-us/microsoft-edge/platform/status/oggcontainer/
Please pay attention to Ogg Chaining (Page 4 of RFC 3533). Most player implementations get that wrong initially.
Good testcases are:
- concatenate several files and check if the resulting single file can be played from beginning to end
- Go to http://dir.xiph.org and play an Ogg/Vorbis and an Opus stream that each must show "Artist - Title" info on that page. Chaining happens upon change of song, easiest visible in the changed Artist - Title. Verify that it continues playing as the song changes (the metadata will not change on the page though).
Please note that Icecast streams do NOT send a content length, as they are continuous streams of data. Seeking is not supported and content MUST NOT be cached. This is also valid for MP3 and AAC streams.