| 88 | | `-row-mt 1` enables row-based multi-threading which maximizes CPU usage. To enable fast decoding performance, also add tiles (i.e. `-tiles 4x1` or `-tiles 2x2` for 4 tiles). Enabling `row-mt` is only faster when the CPU has more threads than the number of encoded tiles. |
| | 88 | `-row-mt 1` enables row-based multi-threading which maximizes CPU usage. To enable fast decoding performance, also add tiles (i.e. `-tiles 4x1` or `-tiles 2x2` for 4 tiles). Enabling `row-mt` is only faster when the CPU has more threads than the number of encoded tiles. |
| | 89 | |
| | 90 | == Keyframe placement == |
| | 91 | |
| | 92 | By default, libaom's maximum keyframe interval is 9999 frames. This can lead to slow seeking, especially with content that has few or infrequent scene changes. |
| | 93 | |
| | 94 | The `-g` option can be used to set the maximum keyframe interval. Anything up to 10 seconds is considered reasonable for most content, so for 30 frames per second content one would use `-g 300`, for 60 fps content `-g 600`, etc. |
| | 95 | |
| | 96 | To set a fixed keyframe interval, set both `-g` and `-keyint_min` to the same value. Note that currently `-keyint_min` is ignored unless it's the same as `-g`, so the minimum keyframe interval can't be set on its own. |
| | 97 | |
| | 98 | For intra-only output, use `-g 0`. |