4 ms·
Almost nobody builds Chromium without trivially linking in ffmpeg. In the real world, Chromium supports every damn codec and container format. All of them. Saf
by blasdel 17y ago
Almost nobody builds Chromium without trivially linking in ffmpeg.
In the real world, Chromium supports every damn codec and container format. All of them. Safari has identical support with Perian installed, and Opera does too with gst-ffmpeg.
The official Chrome supports Theora, Vorbis, H.264, AAC, MP3, and WAV in all reasonable container formats. Mozilla only supports Theora and Vorbis in ogm containers, plus WAV/RIFF for <audio>.
- vetinari 17y agoGood luck with redistributing that ffmmpeg-linked build of Chromium. Or do you think that end-users are going to compile their browser?
- blasdel 17y agoChromium always links with ffmpeg to support video, the question is whether you disable patented codecs in a fit of spite. Ubuntu distributes both those options: https://launchpad.net/~chromium-daily/+archive/ppa/+build/1464626 https://launchpad.net/~chromium-daily/+archive/ppa/+build/14... There's some preemptive wankery in labeling the useful version of the ffmpeg plugin package as 'nonfree' despite the fact that Ubuntu's normal ffmpeg package in multiverse ships with all the Decoders enabled (though there's a separate 'nonfree' ffmpeg with all the Encoders enabled)