How enable mp3 support in html5 for Abrowser?
- Inicie sesión ou rexístrese para enviar comentarios
Any society is composed of individuals. If the many of individuals harmed, then this is harm to the Society.
And I think you don't understand the seriousness of the consequences for the economy, if the small IT-business will be strangled.
On 10/05/13 17:08, name at domain wrote:
> Why? Are you think my country will be "infected"?
>
> I think if software patents really such bad thing for the Society,
> then countries without software patents will be have significant
> competitive advantages.
>
> If your society go mad and saw off the bough on which it is sitting,
> then it is not concern of software_patent-free societies. It is
> beneficial for software_patent-free societies. Because it would
> weaken powerful competitors, like USA.
The real problem is that enabling MP3 support in web browsers might make
the patent problem bigger, because more web developers will use it.
At the moment it seems there is reasonably equal support for Ogg vs MP3.
IE, Safari and Chrome support MP3; Firefox, Opera and Chrome support Ogg
Vorbis.
I haven't found a lot of websites using MP3, so I'm not really convinced
there is a significant demand for it as well. (There is a demand for a
universal audio format, but I don't think that should be MP3).
Andrew.
If even high-tech analog of wheel can be patented, then abandoning of MP3(and others patented formats) will not make even slight difference.
The mobile version of Firefox and upcoming versions will play H264/AAC/MP3, but will use the system codecs if installed. Since Firefox does not bundle the codecs, they should be fine right? Rumor is the GNU/Linux versions will use Gstreamer's plugins for H264 playback and the Windows versions use the built in codecs of Windows 7.
Chromium uses FFMPEG and I really like how it gives you a choice between royalty free only (chromium-codecs-ffmpeg) or not (chromium-codecs-ffmpeg-extra): http://packages.ubuntu.com/source/precise-updates/chromium-browser
El 10/05/13 17:38, name at domain escribió:
> Chromium uses FFMPEG and I really like how it gives you a choice
> between royalty free only (chromium-codecs-ffmpeg) or not
> (chromium-codecs-ffmpeg-extra):
> http://packages.ubuntu.com/source/precise-updates/chromium-browser
Giving people choice whether to be free or not is enslaving them with
their consent
--
Saludos libres,
Quiliro Ordóñez
Presidente (en conjunto con el resto de socios)
Asociación de Software Libre del Ecuador - ASLE
Av de la Prensa N58-219 y Cristóbal Vaca de Castro
Quito, Ecuador
(02)-600 8579
IRC: http://webchat.freenode.net?channels=asle&uio=OT10cnVlJjEwPXRydWU3a
Todo correo que reciba será tratado como información pública, de libre copia y modificación, sin importar cualquier nota de confidencialidad.
There's nothing inherently wrong with supporting patented formats (though in practice, I'm guessing Firefox Mobile ends up using nonfree software for the purpose), but it could be useful strategic pressure to not support certain formats.
Please don't feed the trollS
It seems almost everyone here still don't fully understand the situation. I'll try to clarify.
Firefox (Abrowser) since recently can play some patent-encumbered formats. This includes H.264 encoded videos. For example, it is able to play the MP4 videos of Youtube. Try it and you'll see it works.
Firefox plays patent encumbered formats through another software called GStreamer, a multimedia framework. Many programs on Trisquel use this framework, including Totem, which is the default player. GStreamer plays many different audio and video formats, patent-encumbered and unencumbered (free formats). In fact, GStreamer on Trisquel by default plays many patent-encumbered formats, including MP3 files.
Since Firefox plays the patent-encumbered formats through another program (GStreamer), Mozilla can't be sued for infringing those patents. GStreamer are the one at risk.
This is why Firefox does play free formats without the need of GStreamer. It supports the free formats internally, since there's no risk.
Firefox can also be made to support all other formats GStreamer provides, including MP3 files. It's not any more difficult to support those other patent-encumbered formats. Mozilla just choose not to. It's their policy.
Here Brendan Eich from Mozilla explains why they chose to enable patent-encumbered formats in Firefox: https://hacks.mozilla.org/2012/03/video-mobile-and-the-open-web/. When the article was written, Firefox supported only free formats.
Basically, he explains Mozilla tried to push free formats as much as possible, but big companies (such as Google, Apple and Microsoft) force them to support encumbered formats. If they don't support some encumbered formats they will use their influence. So they have to make a compromise.
Recently I played this MP3 in Starpage. It works perfectly without any plugin or addon in Abrowser 23.
You can try here with Abrowser 23: http://www.w3schools.com/html/tryit.asp?filename=tryhtml5_audio_all
- Inicie sesión ou rexístrese para enviar comentarios