Timeline for H265 - a codec only for powerfull computers?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 13, 2020 at 20:45 | comment | added | Fox | @Make42 yes, software decoding is going to use CPU time to compute what the hardware would if it were available. but since H.265 hardware decoding didn't exist when your computer was built, you're stuck with that | |
| Nov 13, 2020 at 20:19 | comment | added | Make42 | @ArtemS.Tashkinov: Which command returns the information that is useful for this question? | |
| Nov 13, 2020 at 20:05 | comment | added | Artem S. Tashkinov | So: Is H265 too demanding for me, since my computer (from 2013) is too weak? Yes, it is. If you specified your CPU it would be easier to answer. Also read this: switchboard.live/blog/… restream.io/blog/hardware-encoding-vs-software-encoding macxdvd.com/mac-video-converter-pro/… | |
| Nov 13, 2020 at 19:58 | comment | added | Make42 | @Fox:Ok, should I rather ask at superusers? Also: I am not sure I understand what you mean: I can display the H265-videos, but they just eat a lot of CPU power. What is hardware decoding? Is it that H265 is decoded closer to the hardware and because my computer is too old, so it might not have it and needs to do it all in software, which is expensive? | |
| Nov 13, 2020 at 19:55 | comment | added | Fox | this isn't a unix question. but hardware decoding is a powerful thing, and it isn't going to exist in hardware older than the format | |
| Nov 13, 2020 at 19:32 | history | asked | Make42 | CC BY-SA 4.0 |