Re:Why the HTML5 ‘Video’ Element Is Effectively Unusable
by vetinari on Monday December 21, 2009 @06:52PM
(#1008931)
> Debian does, Ubuntu does, Fedora does,
They do not. For Debian and Ubuntu, it is in Multiverse (non-free) repositories. For Fedora, it in RPM Fusion repository. In other words, there is no distribution that distributes H.264 or AAC, so system decoders would not help at all.
Re:Why the HTML5 ‘Video’ Element Is Effectively Unusable
by just_the_tip on Monday December 21, 2009 @08:14PM
(#1009119)
>The browser should have ABSOLUTELY NOTHING to do with video and audio decoding.
I know! While we're at it, who had the brilliant idea to put image decoders in browsers? I say let QuickTime decode GIFs and PNGs.
Re:Why the HTML5 ‘Video’ Element Is Effectively Unusable
by chrischen on Monday December 21, 2009 @08:34PM
(#1009152)
If firfox does do it I believe they would still technically be required to pay licensing fees. The only reason they wouldn't is because mpeg la does not pursue them.
Re:Why the HTML5 ‘Video’ Element Is Effectively Unusable
by windsurfer on Monday December 21, 2009 @07:10PM
(#1008976)
We've had that kind of "standard" for embedding movies for years. The only reason you don't know that is due to it's unpopularity.
The best solution would be to simply use system decoders, like Safari does. On Windows, this would be Directshow, on Linux this would be Gstreamer, and on OS X this would be Quicktime. The browser should have ABSOLUTELY NOTHING to do with video and audio decoding.