mashable.com— YouTube has just revealed that it is rolling out a new video player that supports HTLM5, one that can be accessed via YouTube’s TestTube idea incubator.
Jan 21, 2010View in Crawl 4
Wake me when they actually finalize html5, this matures and standardizes on a codec. If I have to keep fishing around ala 1995 for this or that codec and installs to make this work in a browser I can wait.
actually it's the other way around potentially Firefox could lose a lot of users to Chrome and Safari simply because of this missing feature. As this becomes the default player Firefox has 2 options get on board or tank.
what I don't get is why they don't support specific formats based on certain browsers,it would fragment parts of the web, sure, but on a mostly platform specific basis.Chrome can do H, firefox and linux stuff will probably do ogg, and phones besides ones built for ogg will do h, thus just convert the music/video into two formats and either A) give users a choice, or B) just put H on mobile and do ogg for pc, considering chrome can do ogg, and safari and the iPhone are pretty much the same format wise, and if IE ever supports the audio tag, it will probably be mostly through some version of windows media player, scaled down for size. so thats another format devs will be rushing to, unless IE supports the H one as well.(yes. I did just abbreviate H.264 because I'm lazy)
Since a codec is going to be all native code, unless it is inherent feature of the OS - probably makes more sense to implement it as a plugin. Plugins are native code.
stockjonesJan 22, 2010
Wake me when they actually finalize html5, this matures and standardizes on a codec. If I have to keep fishing around ala 1995 for this or that codec and installs to make this work in a browser I can wait.
magnesJan 22, 2010
No, it won't. IE is dead already. It was dead the minute Google decided to release Google Chrome.
altanarJan 22, 2010
Have you tried using the Windows Firefox under Wine? I've heard that it seems to work better for those people having troubles.
ichopprydeJan 23, 2010
actually it's the other way around potentially Firefox could lose a lot of users to Chrome and Safari simply because of this missing feature. As this becomes the default player Firefox has 2 options get on board or tank.
atomic1fireJan 27, 2010
what I don't get is why they don't support specific formats based on certain browsers,it would fragment parts of the web, sure, but on a mostly platform specific basis.Chrome can do H, firefox and linux stuff will probably do ogg, and phones besides ones built for ogg will do h, thus just convert the music/video into two formats and either A) give users a choice, or B) just put H on mobile and do ogg for pc, considering chrome can do ogg, and safari and the iPhone are pretty much the same format wise, and if IE ever supports the audio tag, it will probably be mostly through some version of windows media player, scaled down for size. so thats another format devs will be rushing to, unless IE supports the H one as well.(yes. I did just abbreviate H.264 because I'm lazy)
johnnysoftwareJan 28, 2010
Since a codec is going to be all native code, unless it is inherent feature of the OS - probably makes more sense to implement it as a plugin. Plugins are native code.
joetacoFeb 4, 2010
I'm in the same boat as OP here. My PC has the codec, it can decode h.264 just fine in WMP/VLC/whatever, why not in <video> tags?
stockjonesFeb 4, 2010
Netscape 2 or 3 that was around 95/96 me thinks. Its been awhile.