FFmpeg Now Supports HEVC/H.265 Decoding
Phoronix: FFmpeg Now Supports HEVC/H.264 Decoding
Earlier this month FFmpeg developers added a VP9 media decoder to their open-source project and now they have added a free implementation of the HEVC/H.265 codec decoder...
Netbooks and tablets will hate H265 video
That means real trouble for netbooks and older tablets without hardware H265 support if the format becomes popular for web video. My old Atom N455 machine (before PowerVR) can just barely play an H264 video in 720p at 30fps. That is in mplayer (not flash) with a downloaded file, with a non-compositing window manager saving memory bandwidth and CPU. That means the H265 codec would also be just able to be played in mplayer, but at 360p instead of 720p, for 1/4 the pixel count. If Flash starts using the codec, it would mean that the 270p videos Liveleak puts out that Pentium 4 class machines can barely play in flash would become unplayable in both netbooks and Pentium 4 class computers, which have about the same video playback capacity in my experience. I would advise webmasters not to use a codec heavier than H264 for anything larger than the tiny "mobile" format videos somewhere around QVGA, and to use it there to improve quality, not cut bandwidth further. I don't know about you but I still see a lot of Pentium 4s in use in my community and must be careful to avoid publishing video they can't play.
Originally Posted by Silverthorn
On the other hand, large format 1080p video intended only for powerful machines to play could really benefit from H265 or VP9. At 1080p, small machines can't play the file except by VDPAU anyway, but files sizes get huge. If a 1080p video already needs a fast dual core or a 4 core to play, a file size that can be reasonably downloaded but will fully load the CPU might be a good tradeoff for many users. Another and even more useful application might be video camera manufacturers, who now produce AVCHD cameras whose output files require 4-core machines to edit. That already being the case, so long as a 4-core can still play and edit the files, taking up half the space on disk for raw video clips could save a lot of money on disk arrays. It would make my 4TB setup equivalent to 8TB. I do hope we have GPU rendering in Kdenlive by that time, though!
Due to the possiblity that camera makers might use H265 for this very reason, it's good to see the ffmpeg project get ahead of the curve now with support for the codec. Besides, it probably won't be long before some commercial sites start serving H265 video, and we will all need to be able to play it because those with the Windows computers will be publishing in that codec,.
More CPU use for mainstream video means more electrical use
If people end up using a codec this processor intensive for long form HD video, electrical consumption will rise as either big multicore CPUs have to handle it, or GPU hardware decoders also have to use more power to do more. How much difference will it make in aggregate electrical use for servers to need to send half the bandwidth vs clients require 4x the processing power, assuming both servers and end user machines are NOT frequently replaced, but end users rely on GPU playback if they do upgrade and server farms also rely on best practices when they do replace equipment? Don't bet on continuing ever-smaller architectures too much longer, I hear that is nearly tapped out for silicon.
Originally Posted by TheLexMachine
Also, for the intended audience of my videos, I am looking at 10+ year hardware replacement cycles, I didn't stop seeing Pentium III's in use until 2010 or so. I have to figure anything I publish had better be playable on a core2 laptop with Linux at least to 2020 or so. Still need to be able to read H265, though, as incoming (source) material could show up in H265 at any time after it goes into use.
The final question is this: Is MPEG-LA going to try to harass the good folks at ffmpeg or at avconv in an attempt to kill compatability with their new baby?