This may be of interest:
http://aomedia.org/press-release/alliance-to-deliver-next-generation-open-me...
Amazon, Cisco, Google, Intel, Microsoft, Mozilla, and Netflix are pooling resources to work on hammering out a standard, royalty-free, next-gen open video codec.
Cisco and Mozilla had already started working together, combining ideas from Cisco's Thor codec and the Mozilla-sponsored Xiph's Daala codec, but getting them together with Google's VPx team is a big happy occasion... getting Intel and Microsoft on board means probably hardware support on x86_64 chips and support in Windows and MS Edge, while Amazon and Netflix pump a lot of video volume out both to browsers and devices, so should help push adoption by ARM SoC makers.
In other words, AWESOME SAUCE!
The only missing major player looks to be Apple... so we'll see if they eventually join on or if they double down on HEVC and we keep having to play JavaScript tricks. :P
I'm subscribing to their mailing list for updates; it may be worth looking into if we can partner in or at least follow along and support stuff on our end.
-- brion
Thanks Brion.
Pine
On Tue, Sep 1, 2015 at 11:58 AM, Brion Vibber bvibber@wikimedia.org wrote:
This may be of interest:
http://aomedia.org/press-release/alliance-to-deliver-next-generation-open-me...
Amazon, Cisco, Google, Intel, Microsoft, Mozilla, and Netflix are pooling resources to work on hammering out a standard, royalty-free, next-gen open video codec.
Cisco and Mozilla had already started working together, combining ideas from Cisco's Thor codec and the Mozilla-sponsored Xiph's Daala codec, but getting them together with Google's VPx team is a big happy occasion... getting Intel and Microsoft on board means probably hardware support on x86_64 chips and support in Windows and MS Edge, while Amazon and Netflix pump a lot of video volume out both to browsers and devices, so should help push adoption by ARM SoC makers.
In other words, AWESOME SAUCE!
The only missing major player looks to be Apple... so we'll see if they eventually join on or if they double down on HEVC and we keep having to play JavaScript tricks. :P
I'm subscribing to their mailing list for updates; it may be worth looking into if we can partner in or at least follow along and support stuff on our end.
-- brion
Multimedia mailing list Multimedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/multimedia
On Tue, Sep 01, 2015 at 11:58:35AM -0700, Brion Vibber wrote:
This may be of interest:
http://aomedia.org/press-release/alliance-to-deliver-next-generation-open-me...
Amazon, Cisco, Google, Intel, Microsoft, Mozilla, and Netflix are pooling resources to work on hammering out a standard, royalty-free, next-gen open video codec.
Y'know, they say "open", but seeing Amazon and Netflix on the list, smart money says they'll include DRM in the specs somehow.
I won't hold my breath for this one...
<quote name="Mark Holmquist" date="2015-09-01" time="14:52:20 -0500">
Y'know, they say "open", but seeing Amazon and Netflix on the list, smart money says they'll include DRM in the specs somehow.
You mean EME, right? ;)
Greg
On Tue, Sep 1, 2015 at 12:52 PM, Mark Holmquist mtraceur@member.fsf.org wrote:
On Tue, Sep 01, 2015 at 11:58:35AM -0700, Brion Vibber wrote:
This may be of interest:
http://aomedia.org/press-release/alliance-to-deliver-next-generation-open-me...
Amazon, Cisco, Google, Intel, Microsoft, Mozilla, and Netflix are pooling resources to work on hammering out a standard, royalty-free, next-gen
open
video codec.
Y'know, they say "open", but seeing Amazon and Netflix on the list, smart money says they'll include DRM in the specs somehow.
I won't hold my breath for this one...
DRM's done on a separate layer from the codec these days, and (for better or worse, probably worse) browser makers have already caved on that front... The 'encrypted media extensions' module interface is already there for H.264, VP8, and VP9, and can be expected to stay around and be used with future codecs -- whether they're patented hellholes like HEVC or royalty-free and open like VP9.
Personally, I'm willing to put up with the existence of DRM-encumbered media in the universe as long as non-DRM-encumbered media continues to work -- and moving away from the patent hell of MPEG-LA and the two competing HEVC patent pools is a Good Thing if it puts high-performance, native support for royalty-free, open codecs into over a billion peoples' hands.
(That said, DRM pisses me off too. :)
-- brion
A presumably related development: Microsoft Edge dev team has announced they're working on native WebM VP9/Opus support:
http://dev.modern.ie/platform/status/webmcontainer/ http://dev.modern.ie/platform/status/vp9videocodec/ http://dev.modern.ie/platform/status/opusaudiocodec/
Ball's in your court, Apple. ;)
-- brion
On Tue, Sep 1, 2015 at 11:58 AM, Brion Vibber bvibber@wikimedia.org wrote:
This may be of interest:
http://aomedia.org/press-release/alliance-to-deliver-next-generation-open-me...
Amazon, Cisco, Google, Intel, Microsoft, Mozilla, and Netflix are pooling resources to work on hammering out a standard, royalty-free, next-gen open video codec.
Cisco and Mozilla had already started working together, combining ideas from Cisco's Thor codec and the Mozilla-sponsored Xiph's Daala codec, but getting them together with Google's VPx team is a big happy occasion... getting Intel and Microsoft on board means probably hardware support on x86_64 chips and support in Windows and MS Edge, while Amazon and Netflix pump a lot of video volume out both to browsers and devices, so should help push adoption by ARM SoC makers.
In other words, AWESOME SAUCE!
The only missing major player looks to be Apple... so we'll see if they eventually join on or if they double down on HEVC and we keep having to play JavaScript tricks. :P
I'm subscribing to their mailing list for updates; it may be worth looking into if we can partner in or at least follow along and support stuff on our end.
-- brion
This is already bearing fruit: current Windows Insider builds of MS Edge include support for VP9 video in WebM container via MSE playback (Media Source Extensions).
I've confirmed this works with one of our random VP9 uploads:
- https://brionv.com/misc/msetest/ - https://www.youtube.com/watch?v=nEYrh2SKTwU&feature=youtu.be (screen cap)
Once Opus audio support is added as well (and/or I figure out a way to separately decode the audio via ogv.js and keep them still in sync!) we can look into native WebM VP9 playback on MS Edge, and it'll add some more urgency to getting VP9 transcodes done. Awesome!
Tracked on: https://phabricator.wikimedia.org/T114316
-- brion
On Tue, Sep 1, 2015 at 1:51 PM, Brion Vibber bvibber@wikimedia.org wrote:
A presumably related development: Microsoft Edge dev team has announced they're working on native WebM VP9/Opus support:
http://dev.modern.ie/platform/status/webmcontainer/ http://dev.modern.ie/platform/status/vp9videocodec/ http://dev.modern.ie/platform/status/opusaudiocodec/
Ball's in your court, Apple. ;)
-- brion
On Tue, Sep 1, 2015 at 11:58 AM, Brion Vibber bvibber@wikimedia.org wrote:
This may be of interest:
http://aomedia.org/press-release/alliance-to-deliver-next-generation-open-me...
Amazon, Cisco, Google, Intel, Microsoft, Mozilla, and Netflix are pooling resources to work on hammering out a standard, royalty-free, next-gen open video codec.
Cisco and Mozilla had already started working together, combining ideas from Cisco's Thor codec and the Mozilla-sponsored Xiph's Daala codec, but getting them together with Google's VPx team is a big happy occasion... getting Intel and Microsoft on board means probably hardware support on x86_64 chips and support in Windows and MS Edge, while Amazon and Netflix pump a lot of video volume out both to browsers and devices, so should help push adoption by ARM SoC makers.
In other words, AWESOME SAUCE!
The only missing major player looks to be Apple... so we'll see if they eventually join on or if they double down on HEVC and we keep having to play JavaScript tricks. :P
I'm subscribing to their mailing list for updates; it may be worth looking into if we can partner in or at least follow along and support stuff on our end.
-- brion
On 30 September 2015 at 14:46, Brion Vibber bvibber@wikimedia.org wrote:
This is already bearing fruit: current Windows Insider builds of MS Edge include support for VP9 video in WebM container via MSE playback (Media Source Extensions).
I've confirmed this works with one of our random VP9 uploads:
- https://brionv.com/misc/msetest/
- https://www.youtube.com/watch?v=nEYrh2SKTwU&feature=youtu.be (screen
cap)
Once Opus audio support is added as well (and/or I figure out a way to separately decode the audio via ogv.js and keep them still in sync!) we can look into native WebM VP9 playback on MS Edge, and it'll add some more urgency to getting VP9 transcodes done. Awesome!
Tracked on: https://phabricator.wikimedia.org/T114316
Nice to see. Thank you for the update, Brion.
J.
multimedia@lists.wikimedia.org