New issue
Advanced search Search tips

Issue 673828 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Please enable mp3 support in Chromium

Reported by tcall...@redhat.com, Dec 13 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Example URL:

Steps to reproduce the problem:
There is a chunk of ffmpeg_c_sources which, if built into Chrome/Chromium, enable mp3 support. (It starts with libavcodec/aac_ac3_parser.c and ends with libavformat/mp3dec.c).

Given that no one considers mp3 decoding to be legally encumbered anymore (see Fedora's recent inclusion), I'd like to ask that the conditional be changed to allow it to be included in Chromium builds as well. The patch is straightforward, and I can submit it through normal channels if desired, but I wanted to open an issue on it first.

What is the expected behavior?

What went wrong?
No mp3 support in Chromium builds (without lying about being Chrome).

Did this work before? N/A 

Is it a problem with Flash or HTML5? N/A

Does this work in other browsers? N/A

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 
Flash Version: 

Contents of chrome://gpu:
 
Status: WontFix (was: Unconfirmed)
You can set ffmpeg_branding=Chrome and proprietary_codecs=true within a Chromium build. I don't think we'll be changing the defaults anytime soon, but will send an e-mail to the appropriate lawyers.

Comment 2 by tcall...@redhat.com, Dec 13 2016

The idea here is that we (Fedora) cannot enable proprietary_codecs=true or ffmpeg_branding=Chrome, because of the legal reasons for all of the things... except mp3. We even have to remove the sources for the items that are conditionalized on those flags.

Nevertheless, thanks for checking with the appropriate lawyers. 

Sign in to add a comment