encoding.info
You are hereSourcePredictionTransformEntropy codingFiltersFramesDecisionsRate controlPerceptionQualityBitstreamSettingsEncoder map
Page 6 of 6 in Settings decoded

Recipes: on-demand ladder, low-latency live, high-quality, grain

Settings decoded · concept · added 2026-11-15

In Brief:
Four x264 command lines, each tying settings to a job with a reason for every option and a list of what to test. They are starting points, not a complete streaming or storage workflow: the high-quality copy is lossy, and the live example leaves delivery and delay to be measured.

A recipe is a short list of settings chosen for one job, with a reason for each. This page gives four: a rung of an on-demand ladder, a low-latency live stream, a high-quality lossy copy for storage, and a grainy source. Each is written for x264, because that is the encoder this course has read most closely. The values marked as examples are places to start looking, not answers.

Build a command line

Choose a scenario. Where the input's frame rate, a maximum rate and a duration matter, set them and the command line follows: the keyframe interval is the frame rate times the seconds, and the buffer is sized from the rate. The frame rate is an assumption about the input, which has to be constant-rate at that figure: the command neither checks nor changes it. The maximum rate is --vbv-maxrate, the fill rate of x264's buffer model, not a cap on every short stretch of the stream. For the ladder rung the seconds are the segment length; for live they are the longest spacing between keyframes. Controls a scenario does not use are switched off.

5 Mbit/s
← 1 Mbit/s20 Mbit/s →

Command line

  
OptionWhy it is there
Options set
Keyframe interval
Buffer size
What to check before trusting it
    Simplified demo: a calculator for two numbers and a list of reasons. Nothing is encoded, and no recipe here was tested on video. What each option does is from x264's source, on the page each row links to. Which options to combine, and every value marked as an example, is this page's judgment. The command writes one elementary stream: packaging, pacing and playback are not part of it. The file names are placeholders.

    Why these and not others

    Trade-offs

    Sources

    Read 2026-11-15, at the commit linked. The lines on minimum-rate behavior, filler and the default chroma format were read 2026-11-16.