5 ms·
> In one of the tests rav1e encoded 1080p source at 0.013fps (i5-7600K @5GHz). That's half a year for a 2 hour movie This is easily explained by 1) no hardware
by earenndil 8y ago
> In one of the tests rav1e encoded 1080p source at 0.013fps (i5-7600K @5GHz). That's half a year for a 2 hour movie
This is easily explained by 1) no hardware acceleration, and 2) the reference implementation is currently intended for clarity and ease of changing, not efficiency or speed. After the bitstream solidifies, both problems will be solved.
> Private torrent communities are already reluctant to use x265 which provides marginal gains compared to x264 at a great increase in encoding time
Because there would be a clear quality loss. The websites they're ripping from (amazon, netflix, whatever) are using H.264, and to recode into H.265 would lose significant quality.
- BTeam 8y agoNetflix and Amazon also already encode in HEVC, they stream it to compatible players/hardware
- puzzlingcaptcha 8y ago>Because there would be a clear quality loss. The websites they're ripping from (amazon, netflix, whatever) are using H.264, and to recode into H.265 would lose significant quality. This is wrong for two reasons: the source codec doesn't matter (it gets decoded to raw yuv420 first anyway), and netflix/amazon/UHD BluRays already use HEVC for 4K which I alluded to earlier.