Slashdot Mirror
Microsoft Announces VP9 Support For Edge
An anonymous reader writes: As noted by some a few days ago, Microsoft has started development on new multimedia container and codec support for Edge. Over on the Edge development blog, Microsoft has now officially announced that "WebM/VP9 support is now in development in Microsoft Edge. VP9 is an open source codec that offers efficient compression to stream HD content at lower bitrates, and is well suited to UHD streaming. Initial support for VP9 will be available in Windows Insider Preview builds soon. This is part of our continuing effort to expand codec offerings in Windows. We continue to evaluate other formats and look forward to receiving feedback as we work on implementing them."
Microsoft's track record is excellent with this. How long before VP9/WebM is fractured and rendered untenable to SoC creators?
GNAA (GAY NIGGER ASSOCIATION OF AMERICA) is the first organization which
gathers GAY NIGGERS from all over America and abroad for one common goal - being GAY NIGGERS.
Are you GAY ?
Are you a NIGGER ?
Are you a GAY NIGGER ?
If you answered "Yes" to any of the above questions, then GNAA (GAY NIGGER ASSOCIATION OF AMERICA) might be exactly what you've been looking for!
Join GNAA (GAY NIGGER ASSOCIATION OF AMERICA) today, and enjoy all the benefits of being a full-time GNAA member.
GNAA (GAY NIGGER ASSOCIATION OF AMERICA) is the fastest-growing GAY NIGGER community with THOUSANDS of members all over United States of America. You, too, can be a part of GNAA if you join today!
Why not? It's quick and easy - only 3 simple steps!
First, you have to obtain a copy of GAY NIGGERS FROM OUTER SPACE THE MOVIE and watch it.
You can watch GAY NIGGERS FROM OUTER SPACE on Youtube.
Second, you need to succeed in posting a GNAA "first post" on slashdot.org , a popular "news for trolls" website
Third, you need to join the official GNAA irc channel #GNAA on EFNet, and apply for membership.
Talk to one of the ops or any of the other members in the channel to sign up today!
If you are having trouble locating #GNAA, the official GAY NIGGER ASSOCIATION OF AMERICA irc channel, you might be on a wrong irc network. The correct network is EFNet, and you can connect to irc.secsup.org or irc.easynews.com as one of the EFNet servers.
If you do not have an IRC client handy, you are free to use the GNAA Java IRC client by clicking here.
If you have mod points and would like to support GNAA, please moderate this post up.
This post brought to you by Penisbird , a proud member of the GNAA
G_____________________________________naann_______ ________G
N_____________________________nnnaa__nanaaa_______ ________A
A____________________aanana__nannaa_nna_an________ ________Y
A_____________annna_nnnnnan_aan_aa__na__aa________ ________*
G____________nnaana_nnn__nn_aa__nn__na_anaann_MERI CA______N
N___________ana__nn_an___an_aa_anaaannnanaa_______ ________I
A___________aa__ana_nn___nn_nnnnaa___ana__________ ________G
A__________nna__an__na___nn__nnn___SSOCIATION_of__ ________G
G__________ana_naa__an___nnn______________________ ________E
N__________ananan___nn___aan_IGGER________________ ________R
A__________nnna____naa____________________________ ________S
A________nnaa_____anan____________________________ ________*
G________anaannana________________________________ ________A
N________ananaannn_AY_____________________________ ________S
A________ana____nn_________IRC-EFNET-#GNAA________ ________S
A_______nn_____na_________________________________ ________O
*_______aaaan_____________________________________ ________C
Gary Niger gary_niger@gnaa.us GNAA Corporate Headquarters 143 Rolloffle Avenue Tarzana, C
You are all LIBVPX. Libvpx says "you cows!". MOOOO!
Just stick with a standard please. An extra few percent compression or whatever for certain specific video types in one specific browser is an irrelevant waste of time. Use your programmers effort for something more productive please MS. Bug fixing would be a good start.
VP9's main difference to VP8 is that it had a massive tradeoff between better compression, and worse encoder performance. This makes VP9 good for static video sites like youtube, but very bad for realtime applications like video chats/conferencing where you encode only once.
VP9 with webrtc is pointless, microsoft knows that. And the war over HTML5 video formats is already lost to H.264. Nobody wants to store and provide videos in two formats, even though all browsers support one.
If they actually want to support open codecs, they should add VP8 to webrtc, or their custom generalized NIH of WebRTC.
all the spy data traffic back to microsoft and the torrent-like update distribution of windows 10 will surely disrupt smooth playback of that uhd video stream.
This is just a pointless trial by ordeal entry test for microsoft to prove its serious about being in the http://aomedia.org/ gang. You know, instead of having to first post "Gay niggers rule" on slashdot for GNAA membership, or having to submit 100 squirrel baby heads in a gunnysack like for MPAA, they have to support an open codec in order to be a member.
They even provide the link to the aomedia website under the link title "Defacto standard" in the VP9 section of their support page.
> VP9 is an open source codec
No, VP9 is a video coding format. A program which can decode data in VP9 format is a "codec".
Similar to how the C Programming Language is not a compiler.
Details, bitte.
Things I can no longer do in Windows 10 without third party software:
- Browse web sites without the browser crashing after 10 minutes;
- Swipe to the right from left half of screen (but not left edge) to go back on a web page;
- Navigate various other apps properly, since apparently I have to have the task bar always open if I want a back arrow;
- Set brightness to less than 25% - which I want it to be when I'm using the tablet just before going to bed;
- Open the Options menu for apps with less than 4 movements (swipe down once, swipe down again, left-click to bring down menu, Settings - before it was one swipe to left from right edge).
Add more below!
When I look at all of the indisputably bad things to have happened to open source software within the past 5 to 10 years, Microsoft just isn't involved. In fact, the damage has been self-inflicted by those within the open source community!
Microsoft wasn't responsible for the disaster that is GNOME 3. It is the GNOME developers who are responsible for that.
Microsoft wasn't responsible for the disaster that is Firefox after version 3. It is the Firefox developers who are responsible for that.
Microsoft wasn't responsible for systemd, and how it has infected nearly every Linux distribution out there. It is the Debian, Ubuntu, openSUSE, SLES, Fedora, RHEL, Mageia, Arch Linux and other Linux developers/maintainers who are responsible for that.
Microsoft wasn't responsible for OpenSSL being full of security flaws. It is the OpenSSL developers who are responsible for that.
Blaming Microsoft for things it wasn't even involved with is just a distraction from who the real culprits are when things to sour in the world of open source; it's the open source developers themselves who are actually to blame!
A Toyota isn't a car. It's the brand name of the manufacturer. The actual car is made of metal and plastic.
Well, you have selected your opinion based on what YOU think is a disaster. Apparently so as to insist it isn't MS's fault.
GNOME3. Not linux. A DE. And only one of many scores. Compare and Contrast with iOS or Metro. If Gnome3 is a disaster, it's one all of them have entered into, so not even the fault of the linux ecosystem or FOSS in its entirety.
Firefox3. See above.
Systemd. This one is RedHat's fault, and what THEY are doing is making Red Hat more like Windows from a vendor and "trained RH engineer" POV. It isn't necessary, but it's getting harder not to use it. And that's mostly because of RH and the pointlessness of anyone trying to not use it in the face of LP's EEE strategy to ensure you pay a horrible price for apostasy.
OpenSSL runs on windows. So it's not Linux. See FF/GNOME
What about OpenDoc? C.f. MSOOXML that not even they themselves supported. Invented solely to ensure that they could continue the government contracts, deny them to OOo, and not have to do a damn thing to change.
What about the millions in "Linux" patent licensing from MS's shakedown?
What about the refusal to support omitting DRM from HTML5? What about lobbying to put it IN?
Selecting things YOU don't like about something using linux that don't involve MS doesn't prove MS isn't fucking Linux over like a wife beating psychopath.
Good to see they are getting into the game....too bad the 'edge' browser is a piece of crap that I never use...part of the fairly lame windows 10 which I have only upgraded to on one of my 9 computers...and am now waiting for windows 11 before anything more happens.
Do we really know they haven't had a hand in any of this?
They seem to have a history of paying shills to post comments and they have a well documented habit of of Tojan Horsing their own people into influential positions among their competitors. Look what Miguel de Icaza did for gnome, silverlight & OOXML and what Stephen Elop did for Nokia.
There almost certainly are more of them.
"Basically, did Microsoft have a hand? Disaster!
Were they not involved at all? Doesn't count as disaster."
Nope. Either you made that up or you're trying to change it to that.
The latter would be a goalpost shift. The former just plain-ass wrong.
GNOME3 is not a linux only disaster. Metro and iOS indicate the same "design" decisions are a disaster in all three camps.
OpenSSL is not a linux only disaster. It's available on other platforms. I wouldn't call this one a disaster either.
systemd is a linux disaster, if you really hate the systemd EEE spread. But so what? Finding one that isn't doesn't prove none are MS created or fermented disasters.
MSOOXML *is* a disaster to OOXML (see, if this isn't counted as a MS-created disaster, then neither is OpenSSL or FF3 a linux disaster)
Patent shakedown *is* a disaster to Linux. The threats continue and the unjust increase of the cost of doing business WITHOUT MS hurts anyone NOT MS. Such as Linux.
If we have two that ARE MS created, we have MS created disasters.
If we only have one, then the OP came up with at least two and probably three things that weren't Linux disasters.
In the latter case,we're 1 for 1. Rather different from the claims of the OP (you?) that none of them are MS's fault.