More detail here:Google's VP8 codec license is OK after all. Google caused confusion with talk of patents, but it turns out company's VP8 video codec is safe for open source use.
http://www.infoworld.com/d/open-source- ... all-219673
More detail here:Google's VP8 codec license is OK after all. Google caused confusion with talk of patents, but it turns out company's VP8 video codec is safe for open source use.
So while now-VP9 may be the codec of choice for the CWE client, it appears HEVC may be viable as well. That is, if it is open source. I haven't read far enough into it to know whether it is."European and French law does not consider 'software-only' patents as valid," said Jean-Baptiste Kempf, president of the VideoLAN Organization, told CNET. "As we are doing software only, not hardware, and we don't make money, we don't license those."
Did we know this?Google and Mozilla banded together to back Google's VP8 for Web video, but the alliance was frayed when Google decided not to keep a promise to remove H.264 support from its Chrome browser.
The instructions for building webm(http://www.webmproject.org/code/build-prerequisites/) actually lists vs2003 as possible option and current configuration output shows it as option so that shouldn't be a problem. Opus which we use for the audio only has a project for vs2010 so that will need some work.Mac_Fife wrote:Great effort!
From an ease of Cyan adoption point of view, anyone able to comment on build prospects on VS2003 as opposed to VS2013?