Opera Supports Google Decision To Drop H.264
An anonymous reader follows up to yesterday's Google announcement that they would drop H.264 support from Chrome. "Thomas Ford, Senior Communications Manager, Opera, told Muktware, 'Actually, Opera has never supported H.264. We have always chosen to support open formats like Ogg Theora and WebM. In fact, Opera was the first company to propose the tag, and when we did, we did it with Ogg. Simply put, we welcome Google's decision to rely on open codecs for HTML5 video.'"
It would be very strange indeed if, in year 2020, radio is using this codec and television is using this codec and cable is using this codec and DVRs are using this codec and Blurays are using this codec...... but the internet did not. The web would be the odd man out.
My AC stalker: " I personally agree with your posts most of the time, but that won't keep me from modding you troll"
I wish software developers would stop playing politics with software and just deliver products that work
what part of the word 'politics' didn't you understand?
::sigh:: I write free software, for free. While I try to "just deliver products that work" by ensuring cross platform compilations work, and adding features users request, I am not always CAPABLE of complying due to patents.
I was going to add support for H.264 encoding and decoding to one of my projects, but I simply can't afford the license fees or to charge the users for each copy.
So, I'm faced with -- use external libs which is not exactly "just works" if you don't have the lib installed, eh?
For the video conference feature I chose to write my own codec to avoid all these "politics", sure, it's re-inventing the wheel, but screw it, I want my product to just work...
As it turns out, H.264 and other codecs have patented such obvious solutions that my "clean room, from scratch, never have looked at any other codec source" code infringes upon H.264 patents...
It would be great to just say, "Hey, I wrote all this code myself, it just works, everyone can use it for free", unfortunately, patents prevent me from doing so.
Don't blame the developers. The users aren't willing to foot the legal bills and chance getting sued by Apple, MPEG-LA, etc, neither am I. Software Patent's Suck!
JPEG, GIF and MP3 all have/had encumbered with licenses yet they are still to this day, web standards. I never hear anyone complain about seeing JPEG's on their web page be it web developer or end user. It's only an issue to people who place ideals over practicality. People are listening to billions of AAC and MP3 files on a daily basis without complaint (and with hardware support).
Which leads me to the next point. What practical reason do I have for wanting h.264 support in a browser? Because I get hardware-based decoding with h.264. It saves my battery time and leaves my CPU free to do other more important tasks. With WebM or Theora I get software decoding and thus a less responsive machine with a shorter battery life.
Perhaps most importantly, the MPEG group have time and time again have brought us the best codecs for digital media. Given Theora's performance compared to WebM and h.264, I certainly hope Ogg isn't responsible for pushing r&d into codecs for the future. Open source is great. I use it every day and can't imagine how much more difficult computing would be without it but the great bulk of its work has been with reproducing free/open versions of existing products and paradigms, not at pushing the boundaries of research and development.
You know, we complained endlessly when Microsoft fragmented the web user experience for years...why are some of us giving Mozilla and Google a free pass when, however noble the motivation, they are trying to do the same thing?