Announcement
Collapse
No announcement yet.
FFmpeg Now Supports HEVC/H.265 Decoding
Collapse
X
-
I was under the impression Lithuania had very fast internet? Wikipedia says you have the 2nd fastest down pipe and the fastest up pipe.
-
Originally posted by GreatEmerald View PostMeanwhile I'd enjoy having 1080p videos that you wouldn't actually need to wait half an hour to buffer.
Also for... buffering? First off... who buffers? Download the damned thing. You can download an entire movie in considerably less time than that. Or are you downloading via smoke signals?
Leave a comment:
-
Originally posted by droidhacker View PostSo sounds like this really doesn't matter one tiny bit. I sure don't want to turn my 6 or 8 core desktop into a vacuum cleaner just to annoy myself playing videos at a resolution for which nobody even has a display capable of viewing.
Leave a comment:
-
So sounds like this really doesn't matter one tiny bit. I sure don't want to turn my 6 or 8 core desktop into a vacuum cleaner just to annoy myself playing videos at a resolution for which nobody even has a display capable of viewing.
Leave a comment:
-
More CPU use for mainstream video means more electrical use
Originally posted by TheLexMachine View PostNobody is likely going to be using h.265 on the web for a few more years. It isn't done cooking and the hardware for decoding it isn't ready yet except in set-top box and mobile hardware markets, which already have decoders available. PCs need GPU-based ASICs for basic h.265 decoding before it will be viable for websites to deploy, as CPU-only decoding of high resolution h.265 - which is what h.265 is designed for - requires a high-end multi-core CPU, which most people don't have and won't get in the hardware they buy.
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?
Leave a comment:
-
Nobody is likely going to be using h.265 on the web for a few more years. It isn't done cooking and the hardware for decoding it isn't ready yet except in set-top box and mobile hardware markets, which already have decoders available. PCs need GPU-based ASICs for basic h.265 decoding before it will be viable for websites to deploy, as CPU-only decoding of high resolution h.265 - which is what h.265 is designed for - requires a high-end multi-core CPU, which most people don't have and won't get in the hardware they buy.
Leave a comment:
-
Netbooks and tablets will hate H265 video
Originally posted by Silverthorn View PostI read an article about it yesterday and as far as I remember...
With equal quality you will get half the file size. To decode it you will need 4 times more computational power.
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,.
Leave a comment:
-
Originally posted by droidhacker View PostHow is it in terms of cpu efficiency? I.e., does "double" the coding efficiency mean that it compresses data twice as far, or uses half the CPU to obtain the same results? If twice the compression, does that translate to twice the CPU? 10 times the CPU? H264 is already tough on CPU, and this new stuff obviously can't be decoded by legacy hardware decoders.
Could anyone please tell me whether it's possible to improve libva to support HEVC?
Leave a comment:
-
Originally posted by droidhacker View PostHow is it in terms of cpu efficiency? I.e., does "double" the coding efficiency mean that it compresses data twice as far, or uses half the CPU to obtain the same results? If twice the compression, does that translate to twice the CPU? 10 times the CPU? H264 is already tough on CPU, and this new stuff obviously can't be decoded by legacy hardware decoders.
Also from what I understand the algorithms are heavily optimized for 1080p and upwards, so for 480p/720p content it is likely not as competitive with something like h264.
Anyway it's great to have HEVC and VP9 decoding in ffmpeg now as it means decoding these formats will work on a wide range of software all of a sudden.
Leave a comment:
-
Originally posted by droidhacker View PostHow is it in terms of cpu efficiency? I.e., does "double" the coding efficiency mean that it compresses data twice as far, or uses half the CPU to obtain the same results? If twice the compression, does that translate to twice the CPU? 10 times the CPU? H264 is already tough on CPU, and this new stuff obviously can't be decoded by legacy hardware decoders.
With equal quality you will get half the file size. To decode it you will need 4 times more computational power.
Leave a comment:
Leave a comment: