ogg in html5? not so much
Jen Simmons
Jen Simmons
jen@jensimmons
http://jensimmons.com
http://milkweedmediadesign.com
917-455-0022
skype: jensimmons
ryanne hodson
how can they do that?
what can we do to stop them?
am i understanding this correctly?
http://twitter.com/Ryanne
Documenting Green ---->http://RyanIsHungry.com
Educate ----> http://FreeVlog.org
iChat/AIM ----> VideoRodeo
Jay dedman
yeah, there's a lot of uproar in the FOSS community about not
including Ogg/Theora in the new standard.
lots of paranoia/fear/reality now.
there are rumors that wesbites will need to license H264 for playback
on their sites. people are predicting the end of free video hosting in
the next couple years.
who knows what is true...but its not a good sign that openess seems to
be closing.
we should be worried because the codecs that seem free now could
become "pay per use" to the user.
and closed codecs mean that DRM can be in full effect.
jay
--
http://jaydedman.com
917 371 6790
Video: http://ryanishungry.com
Twitter: http://twitter.com/jaydedman
Photos: http://flickr.com/photos/jaydedman/
RSS: http://tinyurl.com/yqgdt9
Michael Verdi
billion dollar investment. Also, Apple might have something to say
about it.
Also the way I understand the HTML 5 thing, is that it won't be
supported like you wont just be able to write a simple embed tag or
something. Everything we're doing today will still work. Please
correct me if I'm wrong.
- Verdi
--
http://michaelverdi.com
http://freevlog.org
http://nscape.tv
Chris Double
Vorbis was changed to:
"It would be helpful for interoperability if all browsers could
support the same codecs. However, there are no known codecs that
satisfy all the current players: we need a codec that is known to not
require per-unit or per-distributor licensing, that is compatible with
the open source development model, that is of sufficient quality as to
be usable, and that is not an additional submarine patent risk for
large companies. This is an ongoing issue and this section will be
updated once more information is available."
I'm disappointed that the recommendation was removed, because I
support free codecs and am working on an implementation. I do
understand why the text was changed though. This wasn't so much a
removal of support for the Ogg codecs but an update to reflect the
fact that the situation is currently undecided. The previous text gave
the impression that a decision had been when, when it hadn't. The
various groups are investigating options and will settle on a
solution. This is a solution that has to work for Open Source, as well
as for commercial developers. I write about the various factors
affecting it here:
http://www.bluishcoder.co.nz/2007/12/video-element-and-ogg-theora.html
As has been written in this thread, there are a lot of rumors, fear
and uncertainty being spread around. The fact is nothing has changed,
browsers are still implementing video support, and the decision on a
baseline codec is being worked on.
Two browsers currently have experimental support for Theora (Opera and
Firefox). One has support for codecs that quicktime handles (Apple).
The latter supports Theora with the XiphQT plugin.
For those wondering about the need to license H264 for playback on
their sites, you might want to read the terms for licensing H264/AVC:
http://www.mpegla.com/avc/AVC_TermsSummary.pdf
From 2010 there will be royalty payments required to stream content.
It also outlines the payments required for encoders, decoders, etc.
Just because there are open source libraries and programs to encode,
decode and view H.264 content doesn't mean that use of that is free.
You may still be liable for the license payments. This is the reason
why we don't support H.264 playback natively in Firefox with the video
element, and is the reason why the standard doesn't suggest H.264 as
the baseline codec.
Hope that helps clear some things up and if you have any questions
feel free to ask here.
Chris.
--
http://www.bluishcoder.co.nz