620754 - support vp8 muxed in ogg

Status: VERIFIED WONTFIX

(Core :: Audio/Video, enhancement)

Description

[Alexey Fisher]

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0b9pre) Gecko/20101221 Firefox/4.0b9pre Firefox-4.0/4.0b9pre
Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b9pre) Gecko/20101221 Firefox/4.0b9pre Firefox-4.0/4.0b9pre

Mozilla core support vp8 and ogg, but current Firefox/4.0b9pre can't play vp8 muxed in ogg. I think it should be easy to fix.

Reproducible: Always

Comment 1

[Alexey Fisher]

Attachment: vp8 in ogg sampe file

Comment 2

[Boris Zbarsky [:bzbarsky]]

I believe this is actually on purpose.  We support vp8 as part of WebM, not in general.

Comment 3

[Dave Garrett]

(In reply to comment #2)
> We support vp8 as part of WebM, not in general.

In which case this is an enhancement request for vp8+ogg support.

Not confirming, though, as I don't know if we actually want this or not. I can see the argument for supporting all of the various supported codecs in all of the various supported containers, but I can also see the argument for forcing conformance to the WebM standard and not supporting unusual combinations in order to make sure WebM is properly adopted.

Comment 4

[Boris Zbarsky [:bzbarsky]]

Precisely.  The codec landscape is insane enough as it is, without adding more codec fragmentation to it...

Comment 5

[Alexey Fisher]

WebM was created to simplify matroska. I can understand the reasons for it.
http://www.webmproject.org/code/specs/container/

Ogg was designed to be advanced container for free/open codecs to work on embedded devices. Ogg collected more experience to work in Internet than WebM.

For me, the biggest advantage of Ogg over WebM is metadata (i mean not seample Tags)... XMP, CMML.
http://wiki.xiph.org/Metadata

I wonder why so big metadata freak like google create container which do not really care about it.

So the discussion about ogg/theora or webm/vp8 is a bit confusing. With ogg i have advanced metadata but loend codec, and with webm i have almost no metadata but good codec. Or may be, we should use the best from two sides? ogg+vp8?

Comment 6

[Boris Zbarsky [:bzbarsky]]

Alexey, the ogg container format has some pretty serious issues for actual media playback, especialy for streaming.  So there are in fact good reasons to discourage it for that use case.

Comment 7

[Alexey Fisher]

Do you mean issue which skeleton 4 tries to fix?
http://wiki.xiph.org/Ogg_Skeleton_4

If i understand correctly WebM or Matroska or Ogg are not good for streaming. If we need streaming, we need RTP, is it correct?

Comment 8

[Dave Garrett]

Is there any possibility of just extending the WebM format to add CMML support?
(I'd guess no, at least for now, but maybe for some point in the future?)

Comment 9

[Matthew Gregan [:kinetik]]

(In reply to comment #8)
> Is there any possibility of just extending the WebM format to add CMML support?
> (I'd guess no, at least for now, but maybe for some point in the future?)

The best place to discuss that is on the webm-discuss mailing list: https://groups.google.com/a/webmproject.org/group/webm-discuss/topics?pli=1

I'm marking this bug WONTFIX since we're not planning to do this.