Mailinglist Archive: opensuse-factory (1029 mails)

< Previous Next >
Re: [opensuse-factory] RE: [Bug 847971] Chromium from openSUSE has MP3/MP4 support
  • From: C <smaug42@xxxxxxxxxxxx>
  • Date: Wed, 27 Nov 2013 11:49:49 +0100
  • Message-id: <CAOVv=gPEMbp-Ucmduj3+AOKjnDfUVJe_bSytCLQz6MxTaEdhFw@mail.gmail.com>
On Wed, Nov 27, 2013 at 11:21 AM, Raymond Wooninck wrote:
On Wednesday 27 November 2013 10:48:31 C wrote:

With no codec support... what's the point of building Chromium? This
is like building VLC with no codec support. It's nice and all but not
really practical for the actual end user.

It is not that there is no longer any codec support. The codecs here are
regarding MP4 and H.264. Those will no longer be supported. Other codecs
should still be supported.

Whatever happened with the whole thing of Cisco and H.264?
http://blogs.cisco.com/collaboration/open-source-h-264-removes-barriers-webrtc

I can't pretend to understand the whole legal silliness behind it all,
but... shouldn't "we" be able to use H.264?


It seems that without those two codecs, html5 starts using webm as the
supported codec. We have to see which codecs we actually really loose and
which ones are still there. The end situation will be the following:

As of this writing (May 5, 2011), Chromium supports standard the following:
Vorbis audio codec
Theora video codec
VP8 video codec
PCM 8-bit unsigned integer
PCM 16-bit signed integer little endian
PCM 32-bit float little endian
Ogg container format
WebM container format
WAV container format

Which is a list of formats that are almost (not not quite) completely
not used on the broader web. It would be nice to say, use only OGG
for audio and so on, but... in the real world, people are not doing
that. The not quite is particularly interesting for the webm format
http://en.wikipedia.org/wiki/WebM#Services


When building with the proprietary codec flag, there would also be support for
MP3 audio codec
AAC audio codec (Main only, not AAC-LC, AAC-SSR, HE-AAC)
H.264 video codec
MP4 container format

Which are the actual codecs users are very likely interested in (even
if they don't know what they are called)... and the codecs that cannot
be included because of legal requirements. We're back to the Catch-22
:-)

Can we at least still plug-in PepperFlash with this new Chromium build
with less codecs?

(I have a feeling I'll be switching to the Chrome supplied by Google
in the near future :-P )

C.
--
openSUSE 12.3 x86_64, KDE 4.11
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >