We here at OSNews have taken somewhat of an interest in the new HTML5 video and audio tags, which should - some day - make embedding audio and video material into web pages as easy and straightforward as embedding images, allowing the web to finally remove the shackles of dreadful Flash video. Sadly, the problem with these new tags are the codecs; as it turns out, browser makers have not reached an agreement about what codecs to choose for video, with mostly Apple throwing a spanner in the works, and Microsoft shining in absence.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-03-13
@LB06: MPEG standards aren't acceptable at all. While people in places like the EU where software patents don't really exist can legally create and use software based on MPEG standards without paying any royalties, those in place like the US and Japan, where software patents DO exist have to pay royalties and deal with patents to legally implement those standards. The MPEG is a working group of the ISO. The ISO allows patented elements to be included in their standards and DOESN'T require that companies grant royalty or restriction-free licenses. A few working groups (such as JPEG folks) go above and beyond and actually create OPEN standards, but many others, like the MPEG team, essentially operate as profit generation machines for large multinational companies by working to cram in as many patent-encumbered technologies into standards as possible, thus making the implementation of those standards a sure money-maker for the various companies on the committee in the first place.
Member since:
2005-07-06
Are you saying that MPEG standards are acceptable? Because, well, AAC is defined by both MPEG-2 part 7 and MPEG-4 part 3 and by ISO.
http://en.wikipedia.org/wiki/MPEG-4_Part_3
http://en.wikipedia.org/wiki/MPEG-2#ISO.2FIEC_13818
Besides it is possible to do everything royalty-free. FAAC en FAAD (open source encoder and decoder) didn't pay a single € to anyone.