News for hackers. Stuff that matters.
Re:Google Hangouts goes HD by nrivadeneira on Wednesday August 28, 2013 @01:15PM (#6291304)
I think more interesting than the HD is the fact that they're dropping H.264 for the open sourced VP8

http://arstechnica.com/gadgets/2013/08/google-hangouts-upgra...

Re:Google Hangouts goes HD by anon1385 on Wednesday August 28, 2013 @01:34PM (#6291424)
>dropping H.264 for the open sourced VP8

You are aware that there are open source H.264 encoders and decoders?

Re:Google Hangouts goes HD by k3n on Wednesday August 28, 2013 @01:49PM (#6291514)
But not free, and thus they aren't truly FOSS...

> In countries where patents on software algorithms are upheld, vendors and commercial users of products that use H.264/AVC are expected to pay patent licensing royalties for the patented technology that their products use. [...] All other royalties remain in place, such as royalties for products that decode and encode H.264 video.

1. http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Controversies

edit: s/free/not free/

Re:Google Hangouts goes HD by anon1385 on Wednesday August 28, 2013 @02:03PM (#6291592)
By that logic Linux isn't truly FOSS either since it no doubt infringes on many software patents and users of Linux have been sued over patents[1].

This is one of the main problems with software patents: they are so broad and numerous that it's impossible to write non-trivial software without infringing on something without even realising it.

[1] http://www.digitaltrends.com/computing/google-fined-5-millio...

Re:Google Hangouts goes HD by bad_user on Wednesday August 28, 2013 @04:27PM (#6292405)
There's a difference between willful and non-intentional infringement. If you use H.264 and you get sued by MPEG LA, you can be damn sure that they'll win and that you'll pay up a fortune for it.

On the other hand, patents really aren't so broad and those that are can be and have been overturned in court for being too general - with exceptions of course, of which you hear because they are so outrageous (like Amazon's 1-click patent).

In reality, it's really hard to prove that something is infringing on a patent, if the infringement wasn't intentional. In the Oracle versus Google case, Oracle was hoping they'd get Google with copyright infringement (of APIs no less), the patents involved being just in case the copyright infringement claims wouldn't work. Google won on all fronts.

The reason for why threats of patents infringement are so dangerous is because few companies are willing to make a stand and would rather settle.

Re:Google Hangouts goes HD by ergo14 on Wednesday August 28, 2013 @02:21PM (#6291708)
sued - sucessfully? ;-)
Re:Google Hangouts goes HD by mietek on Thursday August 29, 2013 @03:50AM (#6294751)
It's not clear whether VP8 is patent-free, and it has other issues.

http://x264dev.multimedia.cx/archives/377

Addendum C: Summary for the lazy

VP8, as a spec, should be a bit better than H.264 Baseline Profile and VC-1. It’s not even close to competitive with H.264 Main or High Profile. If Google is willing to revise the spec, this can probably be improved.

VP8, as an encoder, is somewhere between Xvid and Microsoft’s VC-1 in terms of visual quality. This can definitely be improved a lot.

VP8, as a decoder, decodes even slower than ffmpeg’s H.264. This probably can’t be improved that much; VP8 as a whole is similar in complexity to H.264.

With regard to patents, VP8 copies too much from H.264 for comfort, no matter whose word is behind the claim of being patent-free. This doesn’t mean that it’s sure to be covered by patents, but until Google can give us evidence as to why it isn’t, I would be cautious.

VP8 is definitely better compression-wise than Theora and Dirac, so if its claim to being patent-free does stand up, it’s a big upgrade with regard to patent-free video formats.

VP8 is not ready for prime-time; the spec is a pile of copy-pasted C code and the encoder’s interface is lacking in features and buggy. They aren’t even ready to finalize the bitstream format, let alone switch the world over to VP8.

With the lack of a real spec, the VP8 software basically is the spec–and with the spec being “final”, any bugs are now set in stone. Such bugs have already been found and Google has rejected fixes.

Google made the right decision to pick Matroska and Vorbis for its HTML5 video proposal.

Re:Google Hangouts goes HD by ZeroGravitas on Thursday August 29, 2013 @05:45AM (#6295032)
> VP8, as a decoder, decodes even slower than ffmpeg’s H.264. This probably can’t be improved that much; VP8 as a whole is similar in complexity to H.264.

Funny that he himself wrote a ffmpeg VP8 decoder that was between 25 and 33% faster than the libvpx decoder, which had already been improved from when he reviewed it. He said at the time it was faster than ffh264 even with more work to be done.

http://x264dev.multimedia.cx/archives/499

Some recent Google tests suggests that the two ffmpeg decoders basically are the same speed when using one core (2% advantage to VP8) which rises to a 32% advantage to VP8 when using 8 cores.

http://downloads.webmproject.org/ietf_tests/vp8vsh264-decode...

Re:Google Hangouts goes HD by BitMastro on Thursday August 29, 2013 @04:38AM (#6294883)
Re:Google Hangouts goes HD by shmerl on Wednesday August 28, 2013 @08:05PM (#6293459)
You are aware that H.264 is not a free codec? The author above intended to say free (as in liberated), and said "open source".
Re:Google Hangouts goes HD by jrabone on Wednesday August 28, 2013 @01:22PM (#6291340)
...thus pissing off everyone using Hangouts for tech support to people who are only ever going to have Internet Explorer installed. Thanks a bunch, Google.

I really want to crack some skulls together over the state of video compression codecs and OS support. Same thing happened with all the circle-jerking about HTML5 video - Flash had AS STANDARD a bunch of useful codecs (eg. Screen Video) for which there is no HTML5 good replacement if you want to do a lossless screencast.

Re:Google Hangouts goes HD by soperj on Wednesday August 28, 2013 @01:25PM (#6291356)
It's a free service. They do what they want with it. I think supporting the Open Source codec is a good thing. edit: also from the article(First Paragraph) "The H.264 plugin will still be supported for browsers that do not support VP8: IE (of course), Safari, and older mobile clients." So... there's that.
Re:Google Hangouts goes HD by jallmann on Wednesday August 28, 2013 @02:32PM (#6291787)
Being "open source" has nothing to do with it. The H.264 specs are open, there are plenty of FOSS tools available, and its supported ecosystem is much more robust. The only advantage to VP8, from a developer's perspective, is in being royalty-free. But the cost borne by Google in acquiring and developing that IP dwarfs any potential royalty to MPEG-LA ($6.5mm/yr max).

Make no mistake about it, this move is a play for power under the guise of good intentions.

Re:Google Hangouts goes HD by ajross on Wednesday August 28, 2013 @03:10PM (#6292013)
That's a little disingenuous. H.264 ships with pretty much zero open source distros (the only exception I can think is the software codecs in the AOSP images -- but even there I strongly suspect it works only because Google paid a license as part of a bigger deal) because of the patent restrictions.

That's not true of VP8. So the complaint upthread (about VP8 not working on IE) flips on its head: if you care about video working out of the box on open source OSes, then H.264 is a non-starter. Maybe you don't (I can pretty much guarantee that you don't, actually -- in fact from your tone and the "side" you picked I basically assume you're running iOS and OS X exclusively).

But some of us do care, and are quite grateful for VP8 making that possible. I don't feel like getting into an argument as to whether this constitutes a "power play", but it certainly seems like "good intentions" to me.

Re:Google Hangouts goes HD by jallmann on Wednesday August 28, 2013 @03:56PM (#6292242)
> from your tone and the "side" you picked I basically assume you're running iOS and OS X exclusively

Please don't mistake technical pragmatism for ideology. I'm a big supporter of software freedom, most of my work involves codecs like these, and it's almost always on Linux, which is my daily machine. Don't get me started on how fucked up iOS is (both technically and ideologically!).

There's no argument from me that software patents are a plague, and that does make codec distribution tricky. But Google isn't doing this so users can avoid the step of apt-get'ing ffmpeg.

Re:Google Hangouts goes HD by bad_user on Wednesday August 28, 2013 @03:41PM (#6292166)
Mozilla too has fought against H.264 since the beginning. They'll be thrilled that Google is taking this new step towards VP8.

Also, it really doesn't take much brain to figure out why H.264 is dangerous:

1) no open-source software can ship with H.264 (so Firefox cannot ship with H.264, unless it fallbacks to the OS's codecs, which they now do, or if they cut a deal with MPEG LA). Also, Mozilla is lucky because they do make money and they could cut a deal, but most open-source projects don't have sponsors with pockets that big.

2) MPEG LA is not a real standards body, not like ISO. They are some firm in Denver. Those patents may be reasonably licensed (RAND) right now, but they can change those terms whenever they wish to do so. The only companies protected are those that had contributions in that pool (e.g. Apple, Microsoft)

3) See what happened with the GIF format and the LZW patent: http://en.wikipedia.org/wiki/Graphics_Interchange_Format#Uni...

And most importantly for people that care about the web - the web needs to stay open, where "open" in this case really doesn't mean open for companies and organizations with pockets full of millions of dollars.

Re:Google Hangouts goes HD by rdtsc on Wednesday August 28, 2013 @09:14PM (#6293688)
Fuck MPEG-LA, we are not paying them anything.

> The only advantage to VP8, from a developer's perspective, is in being royalty-free.

Good enough for me. Once it is in Chrome.

> Make no mistake about it, this move is a play for power under the guise of good intentions.

Make no mistake software patents are a scam disguised as way to "enhance and protect" innovation.

Re:Google Hangouts goes HD by VikingCoder on Wednesday August 28, 2013 @05:22PM (#6292771)
MPEG-LA ($6.5mm/yr max)

I presume you're getting that from here:

http://www.mpegla.com/main/programs/avc/Documents/AVC_TermsS...

But that specifically states that the maximum is per operating system.

Well, what if it turns out that's entirely too vague? What if MPEG-LA is telling Google that each ROM for each Android is a different operating system?

I don't know. Do you?

Re:Google Hangouts goes HD by wmf on Wednesday August 28, 2013 @05:59PM (#6292980)
My reading is that the cap is per company, not per OS.
Re:Google Hangouts goes HD by Shooti on Wednesday August 28, 2013 @02:53PM (#6291929)
IIRC VP8 requires less processing power at the same bitrate.
Re:Google Hangouts goes HD by jallmann on Wednesday August 28, 2013 @03:07PM (#6292000)
This wasn't the case last I checked (with x264), especially if you consider video quality. Historically VP8 has been much slower, mostly because existing H.264 tools have had more time to mature.
Re:Google Hangouts goes HD by ZeroGravitas on Wednesday August 28, 2013 @05:11PM (#6292698)
I assume they mean power to decode, which makes sense if the article talks about decoding 10 other chat participant's video streams.

I also believe, based on stuff discussed regarding WebRTC that some H.264 advantages don't apply in realtime encoding, like B-frames and so it's a much closer comparison than encoding a movie for streaming. The various submissions to the IETF mailing list arguing for one or the other on technical merit basically came down to a tie.

Re:Google Hangouts goes HD by jallmann on Wednesday August 28, 2013 @05:49PM (#6292926)
I wrote one of the first de/packetizers for VP8 RTP back when the spec was released. My impression was that the codec isn't really designed for network transmission. The probability table for the entire frame is sent up-front, so any loss of that makes the entire frame undecodable, and there's no slicing/IDR or NAL-like layer. It's fairly unworkable without a reliability or error-correction layer on top.

More competition in the codec space is a very good thing, but VP8 is a relatively weak entry IMO.

Re:Google Hangouts goes HD by ZeroGravitas on Thursday August 29, 2013 @05:54AM (#6295048)
> My impression was that the codec isn't really designed for network transmission

That seems unlikely since the major user of its predecessor VP7 was Skype (and before that VP6 was the "web codec" in Flash for a while). Maybe you could make a case that it has flaws that could make it better for this, but it seems silly to claim it was designed for a different use-case.

Re:Google Hangouts goes HD by jallmann on Thursday August 29, 2013 @01:31PM (#6297159)
VP6 in Flash was always delivered losslessly over TCP, and never used for video capture in Flash. Skype is what makes VP8's shortcomings (for video chat) even more interesting, but On2's codecs show a very clear evolutionary path even from VP3. My guess is they didn't want to deviate too much from what was tried-and-true.

Doesn't change my opinion, though -- I think it's more the case of "Well, this works well enough for video chat, if you also do this and that" rather than "We designed this from the ground-up for low-latency, unreliable operation."

Re:Google Hangouts goes HD by dannyr on Wednesday August 28, 2013 @03:04PM (#6291990)
Who would want you to have more power though? Google or MPEG-LA?
Re:Google Hangouts goes HD by pthatcherg on Wednesday August 28, 2013 @01:41PM (#6291469)
Hangouts works with all of the major browsers, including IE. What exactly is your complaint?
Re:Google Hangouts goes HD by patrickaljord on Wednesday August 28, 2013 @05:17PM (#6292747)
Read the article, they'll support both. Besides, hangouts requires a plugin already on windows so they could include vp8 in the plugin... but let's bash Google instead.
Re:Google Hangouts goes HD by devx on Wednesday August 28, 2013 @02:42PM (#6291868)
If IE will ever support WebRTC, then they'll have to support VP8, too, which is the standard codec for WebRTC.

So how about Microsoft moves quicker in adopting open standards, instead of backing proprietary ones, or dragging their feet? It took them 2 years to even decide they will use WebGL, finally. I guess it will take them another 2 years for WebRTC.

Re:Google Hangouts goes HD by masklinn on Wednesday August 28, 2013 @03:45PM (#6292190)
> then they'll have to support VP8, too, which is the standard codec for WebRTC.

It's not. There is no mandatory video codec in WebRTC at this point, only mandatory capabilities namely:

> o MUST support at least 10 frames per second (fps) and SHOULD support 30 fps

> o If VP8 is supported, then it MUST support the bilinear and none reconstruction filters

> o OPTIONALLY offer support for additional color spaces

> o MUST support a minimum resolution of 320X240

> o SHOULD support resolutions of 1280x720, 720x480, 1024x768, 800x600, 640x480, 640 x 360 , 320x240

Source: http://tools.ietf.org/html/draft-cbran-rtcweb-codec-02#secti...

Re:Google Hangouts goes HD by zanny on Wednesday August 28, 2013 @06:36PM (#6293130)
Still hoping Daala can mature and take the throne. If its mathematics truly produce a next generation of compression efficiency in video, and it is open from xiph + Mozilla, that is the biggest kind of win.
Re:Google Hangouts goes HD by pthatcherg on Wednesday August 28, 2013 @03:25PM (#6292087)
FYI, there is no official standard video codec for WebRTC. For audio, the MTI codec is opus. For video, none has been chosen. So far, the two browsers that implement the WebRTC API have choose to support VP8, but that's not mandated by the standard.
Re:Google Hangouts goes HD by ZeroGravitas on Wednesday August 28, 2013 @03:28PM (#6292099)
So far lobbying, from MSFT amongst others, has prevented VP8 being declared a mandatory codec for VP8. On the other hand, Chrome and Firefox are only implementing free codecs (which right now means VP8) so inter operability with the Billions of deployed browser endpoints will require VP8 support.
Re:Google Hangouts goes HD by leaffig on Wednesday August 28, 2013 @04:42PM (#6292511)
I guess Microsoft's main concern is opening up another vector for patent lawsuits by shipping hundreds of millions of VP8 decoders. Google doesn't indemnify against VP8 infringements so why would Microsoft pick up the tab when they're already paying for H264?(Which they got sued over by Googorola btw).
Re:Google Hangouts goes HD by hahainternet on Wednesday August 28, 2013 @04:56PM (#6292599)
As far as I am aware, Google have negotiated an agreement with MPEG-LA to ensure this.

http://blog.webmproject.org/2013/03/vp8-and-mpeg-la.html

Re:Google Hangouts goes HD by anxiousest on Wednesday August 28, 2013 @01:26PM (#6291357)
No worries, unsupported platforms will fallback to the plugin: http://gigaom.com/2013/08/28/hangouts-hd-vp8-webrtc/