4 ms·
The worrying part is "x265 is still too slow to be useful in most practical scenarios" and "if your CPU usage target for x264 is anything faster than veryslow,
by acqq 11y ago
The worrying part is "x265 is still too slow to be useful in most practical scenarios" and "if your CPU usage target for x264 is anything faster than veryslow, you basically want to keep using x264, since at that same CPU usage target, x265 will give worse quality for the same bitrate than x264."
That can mean that there's a real danger that we'll get a lot of worse content in the future, as those who encode may go to use a bigger-number codec because it's assumed to be better (hey, it's newer!) Most of people never encode with different codecs every material just to compare the actual quality.
- leonatan 11y agoI'm pretty sure x265 is just not mature enough. Same thing happened with x264, where it had many issues and bugs. We all know how these fared in the long run.
- fithisux 11y agoMoreover consortium depends on GPU implementations to be available.
- IshKebab 11y ago99% of video is encode-one decode-lots. In that case encoding speed doesn't matter much. It's only for streaming (videocalls, screen mirroring, VNC) that you really need fast encoding.
- feulix 11y ago> In that case encoding speed doesn't matter much When occasionally encoding: yes. When your daily business is encoding larger batches: not necessarily. edit: Just to clarify: we've got an encoding farm which will have to be siginficantly expanded if a substantial amount of content will have to be transcoded in H.265.
- ZeroGravitas 11y agoAnd if you need to have a h.264 fallback anyway, then any alternative codec starts at a disadvantage, as it can only have marginal gains in return for the extra encoding.
- deleted 11y ago[deleted]