Comments on: WebRTC’s Future: is it H.265 or VP9? https://bloggeek.me/h265-vs-vp9/ The leading authority on WebRTC Mon, 17 Jun 2024 11:48:40 +0000 hourly 1 By: Tsahi Levent-Levi https://bloggeek.me/h265-vs-vp9/#comment-116570 Tue, 27 Mar 2018 07:18:25 +0000 http://bloggeek.me/?p=1927#comment-116570 In reply to Carlos.

Thanks for sharing Carlos.

]]>
By: Carlos https://bloggeek.me/h265-vs-vp9/#comment-116569 Tue, 27 Mar 2018 07:13:46 +0000 http://bloggeek.me/?p=1927#comment-116569 H.265 reduces up to 50% the compression rate. However it is not assumed by the industry, because of the higher CPU and resourses consumption. However, H.265 might be faster and more efficient than VP9 if the chipset supports multithreading and code is optimized.
I think that both VP9 and H.265 has advantages and disadvantages regarding technical cand commercial criteria. The Universidad Politécnica de Madrid (Spain) has a research line just to improve H.265 behavior over smartphones.

]]>
By: David Schwartzman https://bloggeek.me/h265-vs-vp9/#comment-116566 Fri, 17 May 2013 10:25:40 +0000 http://bloggeek.me/?p=1927#comment-116566 http://m.androidauthority.com/webm-vp9-youtube-209088/

]]>
By: Nathan https://bloggeek.me/h265-vs-vp9/#comment-116565 Sat, 11 May 2013 01:22:07 +0000 http://bloggeek.me/?p=1927#comment-116565 Might want to be more accurate with the “H.264 needs a license to use and deploy”.

If you are developing an app for or a user of Windows, iOS or OSX then you don’t need a license since Microsoft and Apple have paid for it already.

]]>
By: Tsahi Levent-Levi https://bloggeek.me/h265-vs-vp9/#comment-116564 Tue, 07 May 2013 10:34:46 +0000 http://bloggeek.me/?p=1927#comment-116564 In reply to Buzut.

As far as I could discern, the quality differences are negligible and the main issue is availability of hardware coding for VP8. Oh… and there’s the patent royalties issue to deal with.

]]>
By: Buzut https://bloggeek.me/h265-vs-vp9/#comment-116563 Mon, 06 May 2013 15:15:24 +0000 http://bloggeek.me/?p=1927#comment-116563 Currently, there are two main problems with webm/VP8, first, it doesn’t have the same quality as mp4/H264, thus, it makes bigger files to have a comparable quality. Second, VP8 encoder is less efficient : with FFMPEG, in a multi-threaded environement, it can be set to use all the cores, but it doesn’t use them up to 100%, and videos take much longer to encode than with X264, which is really not convenient.

]]>
By: Lennie https://bloggeek.me/h265-vs-vp9/#comment-116562 Sun, 10 Mar 2013 18:50:23 +0000 http://bloggeek.me/?p=1927#comment-116562 In reply to Tsahi Levent-Levi.

It was all a bit unclear, but seems Google won:

http://www.osnews.com/story/26849/Google_called_the_MPEG-LA_s_bluff_and_won

]]>
By: Tsahi Levent-Levi https://bloggeek.me/h265-vs-vp9/#comment-116561 Sat, 09 Mar 2013 16:45:03 +0000 http://bloggeek.me/?p=1927#comment-116561 In reply to Lennie.

Yap… in a big way.

Monday’s post will be about this one.

]]>
By: Tsahi Levent-Levi https://bloggeek.me/h265-vs-vp9/#comment-116560 Sat, 09 Mar 2013 16:41:27 +0000 http://bloggeek.me/?p=1927#comment-116560 In reply to marcocom.

VP9 has a better future than VP8 in chipset adoption.

VP8 was out of the game for the years it took H.264 to get there. H.265 and VP9 are starting relatively at similar times, which means H.265 will probably get to chipsets first (due to its current ecosystem), but VP9 won’t be lagging behind for a lot longer.

If Google nails down VP8 as the mandatory codec for WebRTC, you will see faster and wider adoption of VP9 as well by chipset vendors.

]]>
By: marcocom https://bloggeek.me/h265-vs-vp9/#comment-116559 Fri, 08 Mar 2013 11:17:38 +0000 http://bloggeek.me/?p=1927#comment-116559 this story focuses on bit-rate, which is important, indeed, but is already sustainable. what VP9 brings with it is a much deeper feature-set than the H standard. transparency, streaming, and far smarter compression.

as you can already see, in order to make a video codec perform like flash, you need to do what flash needed to do, use that CPU…and generate some heat.

]]>