Slashdot Mirror
YouTube Explains Where HTML5 Video Fails
awjr writes "YouTube have pretty much come down on the side of Flash having major issues with the lack of features that the HTML5 <video> tag has and may never have."
← Back to Stories (view on slashdot.org)
Without content protection, we would not be able to offer videos like this.
This rental is currently unavailable in your country.
Surprise, you aren't offering those videos.
Not trying to be confrontational but I don't understand your comment and hoped you could explain further.
I took your comment to mean that even though there were better formats available, MP3 became standard because it was open.
My confusion is thus-
1-when MP3 first started being widely used (I started using it extensively in 1997) it was competing with WAV files. There were no better formats.
2- MP3s are only 'open' in the sense that they don't have embedded DRM. It is still a proprietary format with license fees attached.
Monopolies do not exist.
MS, Intel, Apple, and Google would all like you to convince the FTC of that.
"There is no real right or wrong, just what the majority accepts at the time."
Specious argument, really.
Content "creation" with Flash is really a poor substitute for the real tools that are completely available on all the mainstream OSes- to the point of some of the better answers being available for free or next to it on all of the aforementioned.
If you're doing "content creation" on something like Haiku, I might understand slightly, but you should already understand that you might be on your own on things like this if you choose to run things like Haiku and other up-and-coming OSes.
"Creating content" is a straw man.
I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
I like the fact that I can jump to any part of the video and even direct people to that part of the video with a single url.
HTML5's <video> element supports JavaScript seeking to a new playback position. Your video page can read the fragment identifier from the URI, parse it, and then set the video element's currentTime attribute to make the player seek. The back end uses an HTTP/1.1 range retrieval, the same thing that resumable downloads use.
the video tag doesn't really do steaming in that sense.
Steaming as in a "steaming pile"?
Er... Are you implying that making a video available through a tag is somehow harder than through a flash app ? Care to elaborate what you mean by that ? Because using html5 with youtube is actually a few clicks operation : http://www.youtube.com/html5
The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
He's generalizing, but there were no other formats that could do 12:1 compression like MP3 did when it came out. Few people remember that if you wanted to rip a CD it was a 50 megabyte file. I still remember playing back a small little file with a .MP2 extension on a Dell 486 running Windows 3.1 and going WOW - thats amazing! (gives you kind of a timeline on how long ago this really was). It was some tune from Kimagure Orange Road.
ATRAC btw was only used internally at Sony for DAT and Minidisc (and later AT3 cd's) - there was never any way then to make or play back an ATRAC file on a home PC until somewhat recent history (and only then to try to lock people into using ATRAC over MP3).
HTTP lets you seek to a byte range, but how does that map to a location within the file?
Find the known timestamps before and after the desired seek point, interpolate where you would need to seek if the part between known timestamps had a constant bit rate, and seek to that part of the file. The last article about Ogg vs. MKV presented a test result that it takes on average 3.5 iterations of this algorithm to get to the right part.
This could be worked around by putting this data in the header somewhere.
AVI has such an index. Matroska (wrapper used by WebM) has an index. Ogg does not, but unless you're on a satellite link, four HTTP seeks won't kill you.
I believe in some english speaking countries businesses are considered "plural".
Funny. YouTube HTML5 streaming seems to work find for me. Also do you really need a citation for Flash's performance? Try the following... Got to any laptop and open a YouTube video. Keep an eye on CPU. Now pause it and note the CPU cycles. Now Switch YouTube to the HTML5 beta and do the same. Big difference. HTML5 video which is paused uses 4% CPU while Flash paused uses 32%. NOTE: all of the videos were complete streamed before starting the playback. Also Pause is better than Playback because nothing is suppose to be running.