4 ms·
Mostly static a screen recordings are pretty much the ideal content to show off H.265. The screen would be broken down into blocks, and ones that don’t contain
by KMnO4 6y ago
Mostly static a screen recordings are pretty much the ideal content to show off H.265. The screen would be broken down into blocks, and ones that don’t contain much motion or complexity would use nearly no bandwidth. This image should demonstrate that:
https://postimg.cc/D8MZyzHd https://postimg.cc/D8MZyzHd
Also, I’m not criticizing the authors English (which is much better than my Dutch), but some of those mistakes were almost poetic:
> Some more Ducking made me aware that using '-tag:v hvc1' in FFmpeg creates files that QuickTime can eat.
- Const-me 6y ago> pretty much the ideal content to show off H.265 Same applies to H.264. I think the main reason for OP’s observation, the codecs optimized for real time streaming (including the hardware codecs inside GPUs) don’t have enough time (both CPU time, and maximum allowed encoder latency) to achieve what ffmpeg does when asked to re-encode a video clip from hard drive.
- rubatuga 6y agoIngest would be a better choice