Slashdot Mirror
Firefox 3.5 Beta Boosts Open Video Standard
bmullan writes "Dailymotion, one of the world's largest video sites, announced support for Open Video. They've put out a press release, a blog post on the new Open Video site, and an HTML 5 demo site where you can see some of the things that you can do with open video and Firefox 3.5. (You can get the Firefox 3.5 beta here.) Dailymotion is automatically transcoding all of the content that their users create, and expect to have around 300,000 videos in the open Ogg Theora and Vorbis formats."
There are some other sites which have had <video> support for a while now, such as omploader. It would be nice if some big sites like youtube get rid of flash too, but I'm not holding my breath.
Disclaimer: it's my site
Hi there
Firefox 3.5 Beta Boosts Open Video Standard
Well, bye bye karma... but..
How is this a Linux story/Firefox story? It's a new HTML standard. All browsers will support it, eventually.
Opera has supported for a while now. Stupid site says I'm not allowed to open it cause I'm not using Firefox.
Hmm, does this seem familiar to anyone?
How does the open video format handle styling the UI? One of the reasons sites love flash for video so much is that it gives them complete control over how the video is presented, e.g. available controls, positions, colors and themes to match the rest of the page, etc. Then you have the more intrusive things, like Youtube's overlay ads, text captions, and suggested videos after playback finishes.
If open video means a widget that site owners have no control over, like Quicktime video embedding, then commercial site operators aren't going to be too keen on it.
The h.264 codec that is used to stream their content is far and away better than that Theora garbage format.
The version of Theora that was in ffmpeg2theora 0.19 sucked. But Theora has come a long way since then, coming much closer to x264's fidelity.
If open video means a widget that site owners have no control over, like Quicktime video embedding, then commercial site operators aren't going to be too keen on it.
HTML 5 Video states that a page can ask the user agent to show a built-in control widget (by providing a controls attribute) or hide it and provide its own widget that controls the video player through its DOM (by omitting the controls attribute).
I would assume that most users would prefer not to have to download Flash plugins..
Most users are probably more inclined to download the flash plugin that happens automatically for them versus downloading a whole new browser to get HTML5 video tags to work.
Theora is great for embedded devices like cell phones since it is "cheap" when it comes to cpu cycles. For top quality video, Dirac should be used. I wonder when Firefox, Opera or Konqueror will have native support for Dirac.
In particular, the reference Theora encoder has inferior picture quality and network frame rate control as of 2008.
But as of 2009, Thusnelda is coming soon. The Thusnelda encoder has already fixed some of the problems that Theora inherited from On2's VP3, thanks in part to the flexibility that Xiph added to the Theora bitstream format. Sure, it's still inferior to x264 (50% bigger rate for same distortion as of about a month ago), but it's improving.
Why not wait until the standard is "up to par" with the likes of Microsoft's Silverlight or Adobe's Flash?
Because sometimes worse is better. For example, worse can be better because it's Free and thus more available for deployment on devices other than PCs.
As soon as major sites such as youtube adopt this standard and drop that PoS adobe flash then flash will be practically relegated to crappy early 90s sites and annoying ads, which means that removing the flash plugin from any system will vastly improve your web experience. Good riddance.
Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
The video tag is great, but it has a fatal flaw (actually two fatal flaws, but one is much more important.) The attempt to standardize on a single codec was correct, but now that it has failed the video tag becomes much less useful. At least with flash you can host a video and be sure that most of your audience will be able to view it. With the video tag, even when browsers that support it become widely available, which codec do you encode the video in? Already the browsers are going in different directions, with Safari using Quicktime to play h.264.
Hopefully it gets sorted out soon. Personally I would like to see h.264 adopted if the licensing issues can be sorted out.
I blogged about this issue a couple of days ago, if anyone is interested in a longer version of this comment.
(The other fatal flaw is that the video tag makes it easy for people to download the original video file - something none of the big content providers want. Yes, everyone knows how to do this with Flash videos, but the illusion of content protection is there.)
sheep.horse - does not contain information on sheep or horses.
The meaning of "3 dB" is "twice". Decibels are a logarithmic system, used for two reasons: 1) because for large & weird systems it's easier to say "120 dB" then "a trillion" (of course, this works in certain sciences only), and 2) because our sensitivity to light, sound and probably other sensory input is logarithmic so yes, "3 dB" taken in this context can intentionally be parsed as "small". But for pre-set algorithms (i.e. made to a predefined spec), "two times" is actually a lot of space to fuzz over. You can only do so much before you need to change the very spec that makes Theora - Theora.
-- Sig down
While I am happy to see that Mozilla and Firefox are setting the standards, let me remind readers that previous evaluations have found the Theora encoders inferior compared to contemporary video codecs. In particular, the reference Theora encoder has inferior picture quality and network frame rate control as of 2008.
The important thing is that we move toward open standards, away from proprietary solutions, because open standards allow us to do more cool stuff with them.
Remember RealPlayer? Remember all the bitching about what a piece of crap it was? People had to have it, even though it sucked, because a lot of content was only available in RealAudio format. Today, RealPlayer is all but gone, and you can play the same type of content using whatever software you like. Why? Because when Apple added Podcast support to iTunes, Podcasts suddenly became hugely popular, and virtually all of the content providers that used to offer only RealAudio now offer Podcasts instead. This means that users are free to choose whatever software they want, and competition will drive the software to improve.
In the same way, if web sites move away from Flash video players to using HTML5's video tag, it will mean users will no longer be dependent on Adobe's plugin to access the content. Unfortunately we still have patent issues to deal with; Ogg is unencumbered, but better quality codecs will be supported by most browsers, and if we can get content providers to get used to the idea of making their video content freely available (instead of wrapping it up in Flash), there can be competition among codecs too.
It's not a perfect world, but it's one step closer.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;