Originally posted by XorEaxEax
View Post
Announcement
Collapse
No announcement yet.
Google Gets Ready With VP9 Codec
Collapse
X
-
Originally posted by gigaplex View PostMP4 container? WebM is based off Matroska.
Originally posted by jrch2k8 View Posta. you are trolling
Originally posted by jrch2k8 View Postb. you doing it wrong [TM]
Originally posted by jrch2k8 View Postc. you are using really old software
Originally posted by jrch2k8 View Postd. you hit some really nasty bug
Originally posted by jrch2k8 View Postyes x264 is awesome too
Comment
-
Originally posted by pdffs View PostPlease, please, tell me how - I would love to support libvpx in realtime on common (or at worst, high-end, modern) hardware.
Given that this is an area where vp8 (and I assume also vp9) is supposed to shine, I'm certain you can get information on how to best yield quality output in a real-time setting, I mean this is what the whole 'hello Chrome/Firefox' WebRTC announcement showed off:
Mozilla is excited to announce that we’ve achieved a major milestone in WebRTC development: WebRTC RTCPeerConnection interoperability between Firefox and Chrome. This effort was made possible because of the close ...
For the first time, Chrome and Firefox can “talk” to each other via WebRTC . WebRTC is a new set of technologies that brings clear crisp voi...
I am also assuming that we are talking about VP8 here, VP9 isn't yet finalized and serious optimization work on is unlikely to happen until it's features are finalized.
Comment
-
Originally posted by 89c51 View Posti have the suspicion that the main problem with the adoption of vp8 is HW acceleration. And this shouldn't be the case with vp9 if google wants it to succeed.
Could do a lot for HW acceleration.
Comment
-
Originally posted by Kivada View PostBeat H.265 to market and force all Android phone makers to support it.
2: VP8 was never even competitive to decent AVC encoders. Maybe VP9 will catch up with AVC but no way with HEVC.
3: On2, the company Google bought for VP8, has a long history of flat-out lying about their codecs? quality.
Originally posted by RahulSundaram View PostWebM is a container flexible enough and was designed to support multiple codecs since Google has been planning to update VP8 all along. This will happen as VP9 gets finalized. No need for WebM2.
Comment
-
Originally posted by Awesomeness View Post1: There is nothing to beat to the market. HEVC is done and the Samsung Galaxy 4 already supports it.
2: VP8 was never even competitive to decent AVC encoders. Maybe VP9 will catch up with AVC but no way with HEVC.
3: On2, the company Google bought for VP8, has a long history of flat-out lying about their codecs? quality.
WebM is no container. It's just Matroska with another file extension.
Comment
-
Originally posted by Marc Driftmeyer View PostThere is no way in hell VP9 supplants H.265 in any market form, period. End of story.
Whilst we can (and do) compare codecs side by side, given that we don't watch and compare videos most of the time (cinema, youtube, TV, Laserdisc...), I suspect the quality difference might not be as significant as it appears when comparing side-by-side.
Comment
-
Originally posted by Marc Driftmeyer View PostGoogle is great for people deluded into thinking they give a rat's ass about you.
There is no way in hell VP9 supplants H.265 in any market form, period. End of story.
But if VP9 is better than VP8 then that's still great.
Comment
Comment