Re:A Sneak Peek Comparison of x264, x265, and libvpx
by clouddrover on Tuesday August 30, 2016 @02:30AM
(#12387928)
Browser support is the most important factor for web video. H.265 currently has no browser support but VP9 is supported by Firefox, Chrome, Microsoft Edge, Opera, Vivaldi, etc.
Re:A Sneak Peek Comparison of x264, x265, and libvpx
by oarsinsync on Tuesday August 30, 2016 @03:08AM
(#12388082)
Odds on Safari ever supporting VP9? Especially since Apple are already using HEVC/H.265?
Re:A Sneak Peek Comparison of x264, x265, and libvpx
by clouddrover on Tuesday August 30, 2016 @03:38AM
(#12388183)
I'd say there's a reasonable chance, and if not VP9 then definitely AV1. The next version of macOS and iOS supports WebP (a still image format based on VP8) so the VP8/VP9/AV1 family has a foot in the door:
1. http://www.cnet.com/news/apple-ios-macos-tests-googles-webp-...
Re:A Sneak Peek Comparison of x264, x265, and libvpx
by nightcracker on Tuesday August 30, 2016 @06:49AM
(#12388869)
What makes you think that 4k 60fps is even possible without hardware acceleration? That's 12.7 Gbps output bandwidth (assuming true color), barely possible even using just memcpy, let alone decoding.
Re:A Sneak Peek Comparison of x264, x265, and libvpx
by abainbridge on Tuesday August 30, 2016 @06:29PM
(#12394482)
Interesting point. However, just to be pedantic, if memory bandwidth were the only bottleneck, you'd expect video decoding to generate output faster than memcpy, since it wouldn't have to read as much :-)
My Intel NUC cost me £300 in January and is therefore a fairly low-end machine. It has 307 Gbps of memory bandwidth (2 slots of DDR4-2400). It's surprising how big that number is on a cheap machine today.
I'd love to see a profile of where the CPU time goes in a modern CPU-only video decoder. I guess I could get off my arse and do the profiling myself instead of posting this. Anyway, my guess is that the processor speed is the bottleneck, not the memory bandwidth.
Re:A Sneak Peek Comparison of x264, x265, and libvpx
by RBO2 on Tuesday August 30, 2016 @03:24AM
(#12388129)
That's mostly partial acceleration. Chips now support a lot of codecs. And aside H264/AVC chips makers cannot afford to use so much hardware surface for codecs that are not so popular.
Re:A Sneak Peek Comparison of x264, x265, and libvpx
by AstralStorm on Monday August 29, 2016 @11:30PM
(#12387321)
You must be talking about either a wimpy laptop CPU, a cellphone or a tablet.
Old desktop Sandy Bridge does 4k 60 FPS decoding with no problems, as long as output can sustain it. And integrated GPU does not. You need quite a lot of bandwidth to sustain that much image data.
Luckily it looks like most hardware manufacturers are getting on board with VP9 these days, but the current support for encoding at least is abysmal: https://en.wikipedia.org/wiki/VP9#Hardware_encoding.2Fdecodi...