Updated November 2026: corrected encoder defaults (quantisation matrices are off by default in x264, x265, libaom and SVT-AV1), SVT-AV1 4.0 and 4.2 perceptual tuning modes, Netflix’s AV1 film grain synthesis results, plus a short answer and an FAQ.

Psychovisual redundancy: the short answer

Psychovisual redundancy (also written psycho-visual redundancy, or called perceptual redundancy) is the part of an image or video signal that the human visual system does not use, so an encoder can discard it without a visible loss. Spatial and temporal redundancy are repeated data inside a frame or between frames. Psychovisual redundancy is different: the data is real, but the viewer does not perceive it. Removing it is lossy, because the discarded detail cannot be restored, yet at a normal viewing distance nobody notices it is gone. See also the psychovisual glossary entry for a one-line definition.

Video encoders remove it with four levers. Chroma subsampling keeps less colour detail than brightness detail. Quantisation matrices quantise fine detail more coarsely than coarse detail. Adaptive quantisation spends fewer bits where texture, darkness or motion hides the error. Psy-rd makes the encoder keep texture instead of chasing exact pixel values. Only the first lever is on by default in every delivery format, so check the other three in your own encoder settings.

LeverLimit of the eye it usesTypical encoder settingOn by default?
Chroma subsampling (4:2:0)colour acuity is about half of brightness acuityyuv420p pixel formatyes, in consumer delivery formats
Quantisation matricescontrast sensitivity falls at high spatial frequenciesx264 --cqm, x265 --scaling-list, aomenc and SVT-AV1 --enable-qmin JPEG, yes; in x264, x265, libaom and SVT-AV1, no
Adaptive quantisation (AQ)masking in texture, shadow and motionx264 --aq-mode 1, x265 --aq-mode 2, SVT-AV1 --aq-mode 2yes in x264, x265 and SVT-AV1; off in aomenc (--aq-mode 0)
Psy-rdviewers prefer kept texture over exact pixelsx264 --psy-rd 1.0:0.0, x265 --psy-rd 2.0yes in x264 and x265

Why this matters

If you build, buy, or operate any product that delivers video, psycho-visual redundancy is the lever that decides how much your CDN bills, your encode farm, and your viewer churn really cost. A team that understands which encoder flags drive perceptual quality will ship 1080p streams at a bitrate the next team needs for 720p, and they will do it without their viewers being able to tell. The same understanding tells you when 4:4:4 chroma is a real requirement (post-production, screen sharing, telemedicine) and when it is an expensive vanity feature (mainstream streaming). Skip it, and you over-spend on bits the eye will never see — or you under-spend on the few places it does see, and viewers complain about a "soft" or "blocky" picture they cannot describe. This article walks a non-technical reader from "the eye is not a camera" all the way to a working mental model of psy-rd, AQ modes, and per-title encoding.

What "psycho-visual redundancy" actually means

The phrase has three parts, and the order matters. "Psycho-" refers to perception — what the brain actually does with a signal once the eye has captured it. "Visual" is just a reminder that we are talking about images and not, say, audio masking inside MP3. "Redundancy" is the engineering word for information you can drop without consequence.

Put them together: psycho-visual redundancy is the part of a video signal that the encoder can throw away because the viewer's perceptual system would have thrown it away anyway. It is not the same as the redundancy a codec removes between neighbouring pixels (that's spatial redundancy) or between neighbouring frames (that's temporal redundancy). Those two are statistical — the data is repetitive. Psycho-visual redundancy is perceptual — the data is real, but the viewer would never have noticed it.

A useful analogy. Think of a postal worker delivering a 100-page contract. Spatial and temporal redundancy are the parts of the contract that are duplicates of pages already delivered — the worker can compress those and the recipient still gets the full document. Psycho-visual redundancy is the legalese on page 73 that nobody is going to read; the worker can replace it with a one-line summary and the recipient's behaviour does not change. The eye, like the contract reader, has a budget of attention. A codec that knows where that budget is being spent can stop wasting bits on the bits the eye skips.

This is the third pillar of every modern codec, alongside spatial and temporal compression. It was Claude Shannon's information-theory framing — "irrelevant" information versus "redundant" information — that made the distinction explicit, and JPEG was the first widely deployed standard to take psycho-visual modelling seriously, in 1992.1 Every codec since has built on the same idea, and every codec generation has refined the model: MPEG-2’s reference encoder (Test Model 5) varied the quantiser per macroblock by local activity, H.264 High profile added frequency-weighted scaling matrices, HEVC extended them to every transform size, and AV1 lets the encoder give each of up to eight segments of a frame its own quantiser offset.

Three cards stacked top to bottom, one per form of redundancy a codec exploits. Spatial redundancy, within a single frame, statistical: a four-by-four patch of identical samples; neighbouring pixels usually look almost the same, removed by intra-prediction and the frequency transform. Temporal redundancy, between consecutive frames, statistical: two identical small frames side by side; a scene rarely changes much from one frame to the next, removed by motion estimation and inter-frame prediction. Psycho-visual redundancy, inside the viewer's perception, perceptual, highlighted as the subject of this article: a four-by-four patch whose left half is kept and right half is drawn as dropped, dashed cells; data the viewer's perception would have ignored anyway, removed by subsampling, quantisation matrices and psy-rd. A closing line reads: spatial and temporal redundancy are about the signal, psycho-visual redundancy is about the viewer Figure 1. The three forms of redundancy a codec exploits. The first two are statistical patterns in the signal; the third is a property of the viewer.

How the eye actually sees

Before walking through the tricks, you need a rough mental model of what the eye does well and what it does poorly. The human retina has two main photoreceptor populations. Rod cells dominate peripheral and low-light vision and are colour-blind; they outnumber cone cells about 20-to-1 (roughly 92 million rods against 4.6 million cones).2 Cone cells handle daylight vision and come in three subtypes that respond to long, medium, and short wavelengths — what we summarise as red, green, and blue. Crucially, the three subtypes are not present in equal numbers, and they are concentrated in a small central patch of retina called the fovea. Outside the fovea, your colour resolution collapses fast.

The visual system recombines the cone signals into a brightness channel and colour-difference channels, and video engineering copies that split. One channel — luma — carries brightness, built in daylight mainly from the long- and medium-wavelength cones, with high spatial resolution and high contrast sensitivity. The other channel — chroma — carries colour, with about half the spatial resolution of luma and a noticeably lower sensitivity to fine detail.3 The split is not a codec invention; it is a property of the visual pathway, measurable with psychophysical experiments going back to the 1950s.

Three concrete consequences fall out of that split. First, you can throw away most of the chroma resolution and the viewer will not see the change. This is the foundation of chroma subsampling and the reason 4:2:0 ships in essentially every consumer video format. Second, the eye is much more sensitive to luma at low and middle spatial frequencies than to luma at high spatial frequencies. The number that captures this — sensitivity as a function of cycles-per-degree — is called the contrast sensitivity function, or CSF, and it peaks around 4–6 cycles per degree, then falls off sharply.4 Third, the eye's sensitivity to error in any one region drops sharply when that region is busy, dark, or moving fast, because higher-priority signal in the same neighbourhood crowds out the perception of the noise — a phenomenon called masking.

A practical thought experiment. Hold a sheet of paper at arm's length and read these letters — easy. Stand up, walk past the paper at full speed, and try to read the same letters — impossible, even though the eye received exactly the same photons. The brain stopped resolving fine detail in a moving stimulus, freeing perceptual capacity for the bigger picture. A codec that knows this can spend fewer bits on a fast-pan frame and the viewer will not notice.

A log-log plot of human contrast sensitivity against spatial frequency. The horizontal axis runs from 0.1 to 100 cycles per degree of visual angle with ticks at 0.1, 1, 5, 10, 30, 60 and 100; the vertical axis is contrast sensitivity, one over threshold, with ticks at 1, 10, 100 and 500. The curve rises from about 30 at 0.1 cycles per degree, peaks at 500 between four and six cycles per degree, and falls away to 1 at sixty, where the eye stops resolving finer detail. Two dashed vertical lines at 2 and 20 cycles per degree mark where HD streaming content lives. A note inside the plot says everything under the curve is contrast the eye resolves. Three captions below: low frequencies, flat-field limit, the eye discounts them; peak four to six cycles per degree, highest sensitivity, protect these bits; above sixty cycles per degree, acuity limit, finer texture is not resolved. A closing line says every codec quantises harder at both ends of this curve and gentler at the peak, and that JPEG, MPEG-2, H.264, HEVC, VVC and AV1 all ship a matrix shaped this way Figure 2. The eye's contrast sensitivity is not flat. It peaks in the middle of the frequency range and falls off at both ends — the foundation of frequency-weighted quantisation.

Trick 1 — Chroma subsampling: half the colour data, no visible loss

The first and biggest psycho-visual trick a codec plays is to throw away three-quarters of the chroma data before any actual compression has happened. The mechanism is straightforward. The signal arrives in some RGB form from the sensor; the encoder converts it to a luma-plus-two-chroma representation (Y′CbCr, with the conversion coefficients set by BT.601, BT.709 or BT.2020); then the chroma planes are downsampled. The dominant pattern is 4:2:0 — full-resolution luma, chroma at half resolution horizontally and vertically. A 1920×1080 luma plane keeps every pixel; the two chroma planes carry only 960×540 samples each.

Run the maths once. A raw 4:4:4 1080p frame at 8 bits per sample costs 1920 × 1080 × 3 × 8 = 49.8 Mbit per frame. The same frame at 4:2:0 is (1920 × 1080 + 2 × 960 × 540) × 8 = 24.9 Mbit — exactly half.5 The codec has not done a single lossy compression step yet and has already shrunk the picture by 50%, and yet on a normal display at a normal viewing distance a non-expert viewer cannot reliably tell 4:4:4 from 4:2:0. That is psycho-visual redundancy in its purest form: the saved data was real, but the viewer's perceptual system was never going to use it.

A short reality check. Chroma subsampling is not free everywhere. On a screen-share with sharp red text on a blue background, the chroma-edge resolution matters and 4:2:0 produces visible coloured fringing along the letter edges. The same effect appears in fine, saturated patterns — woven cloth, computer-generated graphics, animation linework, telemedicine images of skin lesions where the diagnostic value is in the colour boundary. Those workflows ship 4:2:2 (half chroma horizontally, full vertically) or 4:4:4 (no chroma reduction at all). The trade-off looks like this:

Sampling Luma Chroma per plane Bits-per-pixel cost Visible cost on natural images Where it ships
4:4:4 full full 100% none medical imaging, post-production, screen capture
4:2:2 full 1/2 horizontal 67% imperceptible on most content broadcast contribution, professional cameras
4:2:0 full 1/4 (both axes) 50% hard to see on natural video at normal viewing distance every streaming codec; YouTube, Netflix, broadcast delivery
4:1:1 full 1/4 horizontal 50% visible on red diagonal edges legacy DV / NTSC tape

The lesson for product teams: 4:2:0 is the right default for any delivery pipeline, and chasing 4:4:4 in a consumer streaming context is almost always a bit-cost mistake. The exception is verticals where the value of the image lives in the chroma channel, and then 4:2:2 is usually enough.

Three cards comparing chroma sampling of the same two-by-two quad, with filled cells meaning a sample is kept and dashed cells meaning it is dropped. 4:4:4, full chroma: four luma samples and four chroma samples, 12 bytes per quad, 100% of raw cost, shipped in post-production, medical imaging and screen capture. 4:2:2, half horizontal: four luma samples and two chroma samples in the left column, 8 bytes per quad, 67% of raw cost, shipped in broadcast feeds and professional cameras. 4:2:0, a quarter on both axes, highlighted: four luma samples and a single chroma sample, 6 bytes per quad, 50% of raw cost, shipped in every streaming codec on the web. A panel titled why the eye does not notice explains that human chroma acuity is about half of human luma acuity, so at about 1.5 picture heights a viewer cannot reliably tell 4:4:4 from 4:2:0 on natural images Figure 3. The three chroma layouts that matter in practice. The lost chroma resolution sits below the eye's threshold on natural content; the saved bytes are real money.

Trick 2 — Quantisation matrices: spending bits where the eye is sensitive

After the chroma plane has been thinned, the codec splits each frame into small blocks and runs a frequency transform on each one. The transform — a Discrete Cosine Transform in classic codecs, integer approximations in modern ones — converts the block of pixels into a block of coefficients, one per spatial-frequency component. The top-left coefficient is the "DC" term, the block's average brightness; the bottom-right coefficient is the highest-frequency detail, the finest texture in the block.

The encoder then quantises every coefficient — divides it by a step size and rounds. Quantisation is where lossy compression actually happens, and it is the lever the psycho-visual model pulls hardest. The trick: instead of using the same step size for every coefficient, the codec uses a different step size per frequency — a small step (preserve precision) for the frequencies the eye is sensitive to, and a large step (throw away precision) for the frequencies it is not. The table of step sizes is the quantisation matrix.

The original JPEG quantisation matrix from 1992 was the first widely deployed psycho-visual table.6 It was built from psychophysical experiments — show viewers two patterns, ask at what amplitude they can tell them apart, and use that threshold as the step size. The matrix looks like this when normalised:

16  11  10  16  24  40  51  61
12  12  14  19  26  58  60  55
14  13  16  24  40  57  69  56
14  17  22  29  51  87  80  62
18  22  37  56  68 109 103  77
24  35  55  64  81 104 113  92
49  64  78  87 103 121 120 101
72  92  95  98 112 100 103  99

Read it as a heat map. Low frequencies (top-left) get small step sizes — 11 to 16 — so they survive almost intact. High frequencies (bottom-right) get step sizes of 99 to 121 — six to eight times harsher — and most of those coefficients quantise straight to zero. The matrix is not symmetric: horizontal frequencies get slightly different weights from vertical frequencies, and diagonal frequencies harshest of all, because the eye's contrast sensitivity is itself anisotropic. The result: in a typical block of a natural image most of the energy sits in the top-left corner, and that is where most of the surviving bits go.

Modern codecs ship their own scaling lists rather than the JPEG matrix, but the idea is identical. H.264 High profile defines default 4×4 and 8×8 scaling lists that get coarser toward high frequencies. HEVC keeps separate lists for luma and each chroma component, for intra and inter prediction, and for each transform size.7 AV1 ships predefined matrices at 16 flatness levels (0 to 15, where 15 is flat), and the encoder picks the range with --qm-min and --qm-max.12 The matrices have become more granular, but the philosophy has not changed in 34 years: quantise the eye's blind spots first.

A common mistake is to call quantisation matrices a "compression algorithm". They are not. They are a bit-budgeting policy layered on top of quantisation; the math of dividing-and-rounding is identical. What the matrix changes is which coefficients survive at any given target bitrate. Disable the psycho-visual matrix (encode with a flat scaling list) and you spend an even number of bits on every frequency, including the ones the eye cannot see — same bitrate, lower perceived quality. JPEG encoders use the matrix by default. Most video encoders do not: x264 defaults to a flat matrix (--cqm flat), x265 uses no scaling lists unless asked, and both libaom and SVT-AV1 ship with --enable-qm 0.13 In video, the bigger psycho-visual gains usually come from adaptive quantisation and psy-rd, which x264 and x265 turn on by default. If you try matrices, compare runs at equal VMAF on your own content before you make them the default.

Trick 3 — Adaptive quantisation: bigger errors where the eye won't see them

Quantisation matrices change the bit budget within a block, by frequency. Adaptive quantisation (AQ) changes the bit budget across a frame, by location. The principle: spend more bits on the regions the eye watches, and fewer on the regions it does not.

Three properties make a region eye-friendly to under-encode: high spatial variance (texture), low luma (dark areas), and high local motion. The first one — variance — is the most powerful, because it triggers contrast masking. The eye's ability to detect a defect inside a busy texture is much lower than its ability to detect the same defect on a flat surface. Show somebody a flat blue sky with a faint compression block: they spot it instantly. Show them the same block inside a frame of woven fabric or moving leaves: they cannot find it.

Open-source encoders expose this lever directly. SVT-AV1's variance-based AQ uses 8×8, 16×16, 32×32, and 64×64 block variances as a proxy for contrast and shifts the QP up or down per block accordingly.8 x264 calls the same idea "AQ mode 1" (variance AQ) and "AQ mode 2" (auto-variance AQ), with strength controlled by the --aq-strength parameter; x264 defaults to mode 1 at strength 1.0, and its mode 3 adds a bias toward dark scenes.9 x265 defaults to mode 2 and adds mode 4, which feeds edge information into the variance estimate.13 How much AQ saves depends on the content, so measure it on your own clips at equal VMAF. For one masking effect on its own, temporal masking, Adzic and colleagues measured up to 6% extra bitrate savings on top of a state-of-the-art HEVC encoder.10

The second axis — luma — exploits the eye's lower sensitivity to noise in dark regions. The mechanism is the same: in a shadow, the local brightness is low and the noise floor of the cone cells is high, so a quantisation error of, say, 4 levels is invisible. Push the QP up in shadows and you save bits without visible cost. The rule has a limit in 8-bit video, where smooth shadows band easily. That is why x264 and x265 both offer an --aq-mode 3 that biases bits toward dark scenes, and x265’s documentation recommends it for 8-bit encodes. SVT-AV1 exposes the same axis as --luminance-qp-bias, which adjusts each frame’s QP from its average luma and is off by default.14

The third axis — motion — is the most counter-intuitive. A fast-moving region has high temporal energy, and the eye's tracking system trades spatial acuity for stable fixation. The result is temporal masking: a few frames of quantisation error during a hard cut or a fast pan are invisible. Research encoders use this by raising the quantiser for the frames right after a cut, while the viewer is still taking in the new scene; that is the effect behind the 6% figure above. Production encoders mostly treat a cut the other way, by placing a keyframe on it.

One video frame drawn as four coloured regions, each carrying its quantiser offset: a pale blue band across the top, flat sky, QP minus 2, boost; a pale green block at lower left, busy texture, QP plus 4, save; a black block at lower right, dark shadow, QP plus 3, save; and a pale purple band across the bottom, fast motion, QP plus 5, save. Below, a table gives the perceptual reason for each offset: flat sky, minus 2, highlighted, smooth areas expose every artefact so spend bits; busy texture, plus 4, high variance masks the error the encoder leaves; dark shadow, plus 3, the eye is less sensitive to noise in darkness; fast motion, plus 5, the eye tracks the subject and stops resolving it. A closing line says QP minus 2 means finer quantisation with better quality and more bits, QP plus 4 means coarser with worse quality and fewer bits, and that the offset is chosen per block on every frame Figure 4. An adaptive-quantisation map for one frame. The encoder is making four bets at once: more bits to the sky, fewer to the texture, fewer to the dark, fewer to the motion.

The fourth lever — psy-rd and "the eye prefers detail over fidelity"

There is one more psycho-visual tool worth knowing, because it changes how the encoder makes its core decision: which way to compress this block? That decision is called rate-distortion optimisation (RDO) — pick the coding mode that gives the best balance between bits spent and distortion produced. The default "distortion" measure is plain sum-of-squared-error against the source: a literal pixel-by-pixel comparison.

The problem with plain SSE is that it rewards blurry reconstructions. A flat, smoothed block has low SSE against the original even if it has lost all the texture; a sharp, slightly-wrong block has high SSE even if it looks more like the source to a viewer. Left to its own devices, an SSE-optimising encoder will blur the picture every chance it gets, because blur scores well by the math. Viewers hate it. They prefer a slightly-wrong-but-detailed reconstruction over a faithful-but-mushy one, every time.11

The fix is to add a second term to the cost function: a penalty for blocks whose visual "energy" (high-frequency content) differs from the source's. The x264 implementation called this psy-rd and ships with a default of 1.0:0.0 (rate-distortion strength 1.0, trellis term off). x265 reworked it for HEVC with a default of 2.0 and added --psy-rdoq, which applies the same bias during quantisation. AV1 encoders get there through tuning modes: SVT-AV1 has --sharpness and, since version 4.0, --tune vq; libaom offers --tune values such as ssim, vmaf and butteraugli.12 The effect is exactly the one the math implies: the encoder spends slightly more bits to keep texture and slightly less on hitting the exact pixel values. Objective metrics (PSNR, the simplest pixel-wise measure) drop a fraction; perceptual metrics (SSIM, VMAF) and human raters rise. It is one of the few cases in video where lower PSNR really does mean better quality.11

The lesson is bigger than one parameter. PSNR is a literalist; the human eye is not. A psycho-visual encoder is built around the second fact, and a toolchain whose only quality target is PSNR is optimising a number viewers never see. This is exactly the gap that VMAF and other perceptual metrics were invented to close.

A common mistake: turning psycho-visual features off "to look at the data"

Engineers under quality pressure sometimes disable adaptive quantisation, psy-rd, and quantisation matrices "to get a clean baseline" — and then publish bitrate numbers from that baseline as the project default. The numbers are not wrong, but they are not the numbers a real user would ever see, because production encoders run with adaptive quantisation and psy-rd on by default. A baseline that turns them off has invented a pessimistic codec that is worse than the one your viewers actually receive, and any feature you compare against it will look better than it really is.

If you must benchmark against a "clean" reference, fine — but document which psycho-visual features were on or off, and never compare a "clean" run against a "tuned" run without saying which is which. The internal language for this is "feature parity": every run in the comparison should have the same psycho-visual toggle set, or the numbers cannot be compared.

What changed in 2025 and 2026

Film grain is the clearest case of psychovisual redundancy in streaming. Viewers notice whether grain is there and how coarse it looks, but not where each grain lands. AV1 film grain synthesis is built on that: the encoder removes the grain, sends a small parametric description of it, and the decoder adds statistically similar grain back. Netflix rolled AV1 film grain synthesis out for film content in July 2025. In its A/B test the starting bitrate fell by 24% and the average bitrate by 31.6%, with about 10% fewer rebuffers.15

The perceptual tuning that used to live in community forks moved into the main AV1 encoder. SVT-AV1 4.0, released in January 2026, finished porting the SVT-AV1-PSY features into --tune vq for video and --tune iq for still images. SVT-AV1 4.2, released in July 2026, added a VMAF tuning mode that targets about 15% VMAF BD-rate improvement at minimal PSNR loss.14 A mode that tunes for a metric can move the score further than it moves what viewers see, so confirm a VMAF gain with a short viewing session before you change a production ladder.

AOMedia released the AV2 specification in June 2026.16 Adaptive quantisation and perceptual rate-distortion tuning are encoder decisions rather than bitstream features, so the levers in this article apply to AV2 encoders the same way they apply to AV1.

Frequently asked questions

What is psychovisual redundancy?

Psychovisual redundancy is the information in an image or video that the human visual system does not perceive, such as fine colour detail or errors hidden in busy texture. Encoders discard it to save bits without a visible drop in quality. Perceptual redundancy is another name for the same thing.

How is psychovisual redundancy different from spatial and temporal redundancy?

Spatial and temporal redundancy are statistical: neighbouring pixels and neighbouring frames repeat each other, and a codec can predict them. Psychovisual redundancy is perceptual: the data does not repeat, but the viewer would not notice if it were gone.

Is removing psychovisual redundancy lossy?

Yes. The discarded data cannot be recovered by the decoder, so the result is lossy compression. The goal is that the loss stays below what a viewer can see at a normal viewing distance.

What does the “0” in 4:2:0 chroma subsampling mean?

In the J:a:b notation, the last number counts the chroma samples in the second row of the reference block. A 0 means the second row has no chroma samples of its own and reuses the first row’s, so chroma is halved vertically as well as horizontally. Luma is still stored for every pixel.

What is psy-rd in x264 and x265?

Psy-rd is a psycho-visual rate-distortion option that makes the encoder keep texture and sharpness close to the source instead of minimising pixel error alone. It usually lowers PSNR slightly while improving perceived quality. The default is 1.0:0.0 in x264 and 2.0 in x265.

Are quantisation matrices enabled by default in video encoders?

Usually not. x264 defaults to a flat matrix, x265 uses no scaling lists unless asked, and libaom and SVT-AV1 default to --enable-qm 0. JPEG image encoders do use their standard matrices by default.

Which encoder settings exploit psychovisual redundancy?

The main ones are the chroma format (for example 4:2:0), adaptive quantisation (--aq-mode and --aq-strength), psy-rd and psy-rdoq, quantisation matrices, and in AV1 encoders the perceptual tuning modes such as SVT-AV1’s --tune vq and film grain synthesis.

↓ Free download: Psycho-Visual Encoder Cheat SheetOne-page reference: which psycho-visual feature exists in x264, x265, SVT-AV1, and libvpx, the default flags, and the safe ranges per content type (live, VOD, surveillance, medical).

Where Fora Soft fits in

We build video streaming software, video-conferencing, telemedicine, and OTT and IPTV platforms where psycho-visual encoding decisions are not academic — they are the difference between a profitable bitrate ladder and one that hurts the business case. In our streaming deployments we routinely tune chroma format, AQ strength, and psy-rd values per content category, because a music-video service and a security-surveillance archive want completely different defaults; the surveillance archive cares about high-frequency detail (a license plate), the music video cares about smooth colour (a stage light). In telemedicine and AR/VR projects the trade-offs shift again — diagnostic chroma matters in a dermatology stream, peripheral acuity does not. The pattern under all of it is the same: know what the eye will actually look at, then quantise around that knowledge.

Video Encoding: A Complete Guide to Video Compression - book cover

The book

Video Encoding: A Complete Guide to Video Compression

This article names four levers; the book works through the tables behind them. It carries the JPEG and HEVC scaling lists coefficient by coefficient with the contrast-sensitivity measurements the weights were derived from, x264's AQ modes and --aq-strength ranges beside SVT-AV1's variance segments, and the psy-rd experiments that explain why a lower PSNR can mean a better picture. Chroma gets its own chapters — 4:2:0 siting, the cost of 4:2:2, and the content types where the colour boundary is the product. Written by Nikolay Sapunov, CEO at Fora Soft.

Read it on Amazon →Kindle & paperback · Fora Soft Video Engineering Handbook

Are you paying for bits your viewers cannot see?

Send us a sample of your ladder and the encoder settings behind it, and we will tell you what the psycho-visual features are actually doing: whether adaptive quantisation and the quantisation matrices are on at all, what your chroma format is costing you at your volumes, and what an --aq-strength and psy-rd sweep is worth on your own content — measured in VMAF and in viewer ratings, not in PSNR. 250+ video products shipped since 2005.

Book a 30-min call →WhatsApp →Email us →

See our case studies


  1. Wallace, G. K. (1992). "The JPEG Still Picture Compression Standard." IEEE Transactions on Consumer Electronics, vol. 38, no. 1. https://ieeexplore.ieee.org/document/125072. Accessed 2026-05-16. ↩

  2. Curcio, C. A. et al. (1990). "Human photoreceptor topography." Journal of Comparative Neurology. Photoreceptor counts and distribution. https://onlinelibrary.wiley.com/doi/10.1002/cne.902920402. Accessed 2026-05-16. ↩

  3. Poynton, C. (2012). Digital Video and HD: Algorithms and Interfaces (2nd ed.). Morgan Kaufmann. Luma/chroma separation in the visual system. Accessed 2026-05-16. ↩

  4. Mannos, J. L., Sakrison, D. J. (1974). "The Effects of a Visual Fidelity Criterion on the Encoding of Images." IEEE Transactions on Information Theory. Original CSF measurements used in image-coding research. Accessed 2026-05-16. ↩

  5. ITU-R BT.601 / BT.709 specifications on chroma sampling structures. https://www.itu.int/rec/R-REC-BT.709/. Accessed 2026-05-16. ↩

  6. CCIR / CCITT JPEG specification (1992), Annex K, Tables K.1 / K.2 — default luminance and chrominance quantisation matrices. https://www.w3.org/Graphics/JPEG/itu-t81.pdf. Accessed 2026-05-16. ↩

  7. Sullivan, G. J., Ohm, J.-R., Han, W.-J., Wiegand, T. (2012). "Overview of the High Efficiency Video Coding (HEVC) Standard." IEEE Transactions on Circuits and Systems for Video Technology, vol. 22, no. 12. Scaling list and quantisation matrix overview. https://ieeexplore.ieee.org/document/6316136. Accessed 2026-05-16. ↩

  8. SVT-AV1 documentation — Appendix: Variance-Based Adaptive Quantization. https://gitlab.com/AOMediaCodec/SVT-AV1/-/blob/master/Docs/Appendix-Variance-Based-Adaptive-Quantization.md. Accessed 2026-05-16. ↩

  9. x264 manual (Debian, current build) — --aq-mode, --aq-strength parameters. https://manpages.debian.org/experimental/x264/x264.1.en.html. Accessed 2026-05-16. ↩

  10. Adzic, V., Kalva, H., Furht, B. (2013). "Exploring visual temporal masking for video compression." Up to 6% additional bitrate savings on top of state-of-the-art HEVC. https://www.cse.fau.edu/~hari/files/2028/Adzic%20et%20al_2013_Exploring%20visual%20temporal%20masking%20for%20video%20compression.pdf. Accessed 2026-05-16. ↩

  11. Wang, S., Zeng, K., Rehman, A., Wang, Z. (2017). "Perceptual Evaluation of Psychovisual Rate-Distortion Enhancement in Video Coding." University of Waterloo. Confirms psy-rd lowers PSNR but improves perceptual quality. https://ece.uwaterloo.ca/~z70wang/publications/HVEI17_PsyRD.pdf. Accessed 2026-05-16. ↩↩

  12. aomenc manual (Debian testing): --enable-qm (default 0), --qm-min 8 and --qm-max 15, --aq-mode (default 0), --deltaq-mode, --tune options. https://manpages.debian.org/testing/aom-tools/aomenc.1.en.html. Accessed 2026-11-04. ↩↩

  13. x265 documentation, Command Line Options: --aq-mode (default 2; modes 3 and 4), --psy-rd (default 2.0), --psy-rdoq, --scaling-list (“x265 does not use scaling lists by default”). https://x265.readthedocs.io/en/master/cli.html. Accessed 2026-11-04. ↩↩

  14. SVT-AV1 release notes: v4.0.0 (2026-01-23, SVT-AV1-PSY features ported to --tune vq and --tune iq) and v4.2.0 (2026-07-14, VMAF tuning mode, ~15% VMAF BD-rate). https://newreleases.io/project/gitlab/AOMediaCodec/SVT-AV1/release/v4.0.0 and https://newreleases.io/project/gitlab/AOMediaCodec/SVT-AV1/release/v4.2.0; option defaults (--luminance-qp-bias, --enable-qm, --aq-mode) from the SvtAv1EncApp manual, https://www.mankier.com/1/SvtAv1EncApp. Accessed 2026-11-04. ↩↩

  15. Netflix TechBlog (3 July 2025), “AV1 @ Scale: Film Grain Synthesis, The Awakening”, https://netflixtechblog.com/av1-scale-film-grain-synthesis-the-awakening-ee09cfdff40b; A/B figures as reported by Broadband TV News, https://www.broadbandtvnews.com/2025/07/04/netflix-film-grain-synthesis-saves-on-the-bitrate/, and TV Technology, https://www.tvtechnology.com/news/netflix-rolls-out-av1-film-grain-synthesis-streams-for-film-content. Accessed 2026-11-04. ↩

  16. Alliance for Open Media (June 2026). “Alliance for Open Media Releases AV2 Codec.” https://aomedia.org/press%20releases/Alliance-for-Open-Media-Releases-AV2-Codec/. Accessed 2026-11-04. ↩