Slashdot Mirror
YouTube Offers Experimental Opt-In HTML5 Video
bonch writes "YouTube is now offering the experimental option to view all YouTube videos using HTML5 in H.264 format. Supported browsers are Chrome, Safari, and the ChromeFrame plug-in for Internet Explorer. Captions, ads, and annotations aren't yet supported but are coming soon."
Well, you could sign into an account on YouTube and turn them off.
Here
The three most annoying features of YouTube won't display? Where do I sign?
Captions? They are opt-in, and they can be very useful for hard of hearing people (if the video creators do add them, that is...)
Agreed on the others, though.
Firefox supports the video tag. The h.264 support can be added by installing mplayer browser plugin or xine browser plugin.
The largest prime factor of my UID is 263267.
Even with h264 support (through gecko-mediaplayer), Youtube tells me "Your browser does not currently recognize any of the video formats available.".
This
Most video chipsets these days are including hardware support for H264 decoding. This includes the chipsets in devices like mobile phones, MP3 (portable media) players, and set-top boxes.
Well, you could sign into an account on YouTube and turn them off.
And let them track how many cute, fluffy kitten videos I watch? Er, I mean how many boob videos I watch? And car crashes. And explosions! People falling off skateboards. Grr, manly videos! That's right. Anyway, I think not.
Kwisatz Haderach
Sell the spice to CHOAM
This Mahdi took Shaddam's Throne
No. Firefox video tag is free formats only. Tools like mplayer are a cesspool of security holes— they aren't designed to be exposed to hostile content. The video tag requires pretty deep browser integration, ... only apple supports using the native infrastructure and even they disable 99% of their features for security reasons (e.g. try a mov with hyperlinks in it).
Mozilla is committed to an open web, and you can't get their with a wink and a nod and asking users to install codec software which is illegal everywhere in the developed world. (Including europe. I'm so tired of seeing people characterized codec licensing as a US thing— there are more European patents on codecs than US patents)
H.264 is the codec used in youtube when you play videos with the flash player. This HTML5 video viewer just reuses theses videos, only the html client code changes. Using other codec means reencoding all their videos in a different video format, which must not be easy. Specially when the alternatives are worse (theora) or not ready (dirac).
Using Safari/OSX (latest version of each) on a first generation Core2 Duo laptop (2.33 GHz), I tried watching the same video (containing no ads, annotations, etc) at the same size using both the default Flash option and the beta HTML5 option. CPU use was a steady 33-34% during playback in Flash. A steady 12-13% in HTML5. Seems like a winner to me.
I though the OP was referring to the crappy popup that video publishers can pepper YouTube videos with "LOLOLOLOLOLOL TEH NXT BIT IZ TEH PHAT!!!!!"
Theorarm decodes Theora full screen video at about 110 FPS on my jailbroken iphone. The hardware support thing for h264 is mostly an issue because of h264's utterly obscene cpu consumption, Theora is much more thrifty. The "doesn't work" thing is entirely manufactured by the device makers (e.g. Apple) having a direct monetary interest on a format that they get royalties for being adopted.
Mozilla doesn't just refuse. Legal licensing of the codec would be 10% of their annual budget. Do you really want 10% of Mozilla's budget to just be flushed on a single media codec? (and then more needed for AAC.). For that kind of money Mozilla could employ an entire codec development team.
No one huh?
> and ffmpeg being free and with H.264 support
Free in what sense? You can use their code in your code. Your code would then not be able to be distributed to users unless you pay the relevant patent licensing fees. The Mozilla Corporation could do that, but then any other Firefox distributors (e.g. Linux distributions) would not be able to distribute Firefox without either removing this functionality or paying the relevant patent licensing fees. Anyone doing a custom build of Firefox and distributing it could be sued by MPEG-LA to recover the money due them.
Effectively, Firefox stops being "free" for practical intents and purposes. It's still "open source", but the only thing you can really do is contribute patches back to the main repository, unless you pay up the patent fees.
That's not exactly a desirable situation. We might end up there, but as a first cut trying to avoid it is a good thing.
Yeah I tried that. I had to move back down to 10.0 because while the performance was better, videos looked like crap because hey, guess what, 10.1 doesn't have nice-looking video scaling! I'm sorry, but I'd rather have Flash eat my CPU alive than feel like gouging my eyes out due to uneven pixelation.
--- Mr. DOS
Why throw around bullshit claims based on nothing more than your vague and absurd assertion that "every time you hear..."? You can easily search for that info yourself, which would take less time than it took to post to slashdot. For example, you have this purely subjective analysis which was done by encoding Theora and h.264 files with equivalent size and then having a dude claim what image he preferred. Although he claimed that h.264 was better according to his own personal tastes, you can easily see for yourself that, when comparing Theora and h.264, you get pratically the same quality with the same file size. It's the same bandwidth, same size, practically (and in some cases) indistinguishable quality and although Theora's developers had to intentionally avoid more efficient algorithms due to patents.
So who exactly is spewing those bullshit, FUD claims of "Theora needs triple storage capacity and wastes twice as much bandwidth"?
Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
It's not just a matter of money. It's a matter of Firefox not being able to be redistributed by downstream distributors unless they _also_ buy the license. As in, it would effectively stop being free software in the "can modify and redistribute" sense.
Yes they can! All the have to do is wrap the platform native playback capabilities (or one of them on Linux). Every major platform has a media framework that can be made to support h.264.
Old technology? Since when is technology's age any relevant to it's value? Electricity was discovered centuries ago and we still rely on it up to this day. Do you believe that just because it's old technology it should be simply be abandoned without any relevant and rational reason to justify it?
And for your information, Theora is on par with other formats such as h.264 in all relevant categories such as file size, bandwidth and encoding quality. So, that's also not it.
Regarding that "hardware accelerated" bit, do you know what it takes for a codec do be "hardware accelerated"? It only takes the will of the manufacturer to offer hardware support for a specific format. The h.264 codec isn't magical nor is the Theora codec cursed. In fact there are Theora hardware decoders in the market already.
So please refrain from spewing ignorance and/or FUD. Theora may eventually stumble on relevant shortcomings but hard
Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
Trying out with chromium (binary package) at the moment, does not work, neither do firefox 3.5. :(
"Your browser does not currently recognize any of the video formats available.
Click here to visit our frequently asked questions about HTML5 video."
Being a codec snob is trendy.
The reality of it is much less exciting.
Youtube already supports several versions of the files, they could probably drop the flash 7 compatibility in exchange for Theora. In terms of numbers of client Ogg/Theora for firefox is probably a better deal than flash 7. Adding one more to a half dozen isn't a tripling.
Part of the problem is that h264 licensing fees are generally hidden. You don't pay for a license, your hardware/software vendor does. Apple and Microsoft and Google all buy the licenses for you and include them in their products. It's hard to convey the importance of the licenses for non-free codecs if they seem to be free.
From the VLC FAQ:
Is VLC legal in all countries?
Probably not. Specially DeCSS module might violate DMCA (and similar laws) and some codecs would require licenses for personal/commercial use. There haven't been any court cases related to VLC but specially companies should make sure they pay license fees to license holders if they use VLC commercially and use patented formats or codecs.
Essentially the licence is not for implementing the codec, but for using it. If you use VLC to encode video, then broadcast that video (including on the Web), then at least in some countries, you have to pay the patent holders.
you don't need flashblock, noscript blocks flash just fine. Just tell it to block flash and to apply restrictions to trusted sites as well.
Climate Progress - Hell and High Water
That's been seriously considered. The reason it's not being done (yet?) is described at http://weblogs.mozillazine.org/roc/archives/2009/06/directshow_and.html
That comparison is ancient. Theora has come a long way since then.
.Some of us are deaf, and would much rather Youtube caption their videos. You don't HAVE to watch it. That's why it's called CLOSED CAPTIONING. Don't like it? TURN IT OFF.
YouTube has closed captioning? I thought all they had were stupid popup captions that are manually added by video uploaders. Google Voice has quite a bit more training to do before closet captioning is anything like automatic or pervasive on YouTube.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
Well technically yes. Theora produce slightly more blurry frames for an equivalent bitrate.
Now the big question: do we *really* need the added quality of H.264 ?
For fuck's sake, it's Youtube we're speaking about.
The website filled with small home-made video done using crappy webcams. Or feature botched TV-grabs. Where the people who upload video don't actually really have a clue about codecs and thus their creations have been through several conversions, each time with the corresponding drop of quality.
Arguing whether H264 or OGG/Theora is better for streaming HTML5 videos means arguing which codec will be the best to faithfully convey all the artefacts contained in video produced by clueless users. Given the average, both formats are already*good enough*. In fact the older MPEG-4/DivX/Xvid would probably be already good enough.
We're not talking about the best way to bring 1080p commercial movies to Youtube, we're talking about videos of dancing kittens filmed with a smart-phone's embed cam.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
As long as Theora isn't implemented in video chipsets, it is irrelevant. I think more people care about decent performance than RMS-approved GNU/Freedom (Free as in beards).
I think you misunderstand. The HTML5 standard does not specify a codec to be used in the <video> tag; just like the standards don't specify what image formats are to be used in the <img> tag.
Arguing that "it's not HTML5" because your browser (presumably, firefox) doesn't support h.264 would be no different to an Internet Explorer user saying "it's not HTML4.1" when a website uses PNG images.