Updated October 2026: short answer and comparison table up top, 1080i vs 1080p resolution and frame-rate math, which codecs still code interlaced video (H.264 yes, HEVC metadata only, AV1 no), GPU deinterlacers through FFmpeg 9.0, and an FAQ.
Progressive vs interlaced: the short answer
Progressive scan draws every line of a video frame in one pass; interlaced scan splits each frame into two half-pictures, called fields, that are captured and shown one after the other. One field carries the odd lines, the other the even lines, and the two are taken 1/50 or 1/60 of a second apart. 1 Interlacing halves the bandwidth a broadcast needs at the same refresh rate, but anything that moves between the two fields tears into horizontal "comb teeth" on a modern screen.
For anything you build in 2026, progressive is the answer. Web streaming, video calls, phones, laptops, modern TVs and every Ultra HD format are progressive; interlaced survives only as an input you may receive from broadcast feeds, older cameras and archives. When it arrives, you convert it to progressive once, at ingest, before encoding.
| Progressive (for example 1080p) | Interlaced (for example 1080i) | |
|---|---|---|
| How a frame is drawn | All lines, top to bottom, in one pass | One field (odd or even lines), then the other field |
| Lines captured at one moment | 1,080 of 1,080 | 540 of 1,080 (one field) |
| Motion samples per second | Equal to the frame rate (25, 30, 50 or 60) | Twice the frame rate: 50 or 60 fields |
| Typical artefacts | None from the scan itself | Combing on moving edges, flicker on fine horizontal detail |
| Bandwidth | Full frame every refresh | About half, at the cost of vertical detail in motion |
| Where you meet it in 2026 | Web, mobile, streaming TV apps, video calls, all Ultra HD (4K/8K) | Feeds between broadcast studios, US digital TV (ATSC 1.0), DVDs, legacy cameras and archives |
| Codec support | Every codec | MPEG-2 and H.264 have special field-coding modes; HEVC only labels fields; AV1 has none |
Why this matters
If you build a product that ingests video from outside sources — telemedicine systems pulling from older medical equipment, surveillance platforms accepting old IP cameras, online learning tools repurposing archive content, broadcasting platforms taking satellite contribution feeds — you will receive interlaced material whether you ask for it or not. If your team processes that material as if it were modern progressive video, every moving object in the resulting stream will grow visible "teeth" — a defect called combing — and your codec will waste bits encoding that defect instead of real picture content. Combing makes professional-looking content look broken, and once it's baked into the encoded file, removing it later always costs picture quality.
The fix is well-known and cheap, but it has to happen at the right step in your pipeline and you have to know what to look for. By the end of this article you'll understand exactly when to apply it and which of the available tools is the right choice for your situation.
The 1930s problem that gave us interlaced scan
To understand why interlacing exists, you have to remember what television looked like in the 1930s. Engineers in the UK, USA, and Germany were racing to send moving pictures over the air for the first time, and they hit a hard trade-off. They needed pictures that were detailed enough to be useful (enough horizontal lines per picture), they needed those pictures to refresh fast enough that motion looked smooth (a high refresh rate), and they had only a narrow slice of radio bandwidth to send everything through. The technology of the time couldn't deliver all three at once.
Here's the trade-off in concrete numbers. A high refresh rate — about 50 or 60 pictures per second — was necessary because anything slower visibly flickered on the cathode-ray tubes of the era; the screen would noticeably dim between frames and the viewer would see it. But the radio bandwidth available could carry only about half that much detail. Engineers had to pick: either flicker-free at low detail, or detailed but flickering. Neither was acceptable.
Interlacing had been patented a few years earlier, and the BBC's 405-line service, launched in 1936, was the first regular broadcast to use it. 2 Instead of sending each complete picture in one go, they split every picture into two halves. The first half contained only the odd-numbered horizontal lines (1, 3, 5, 7…). The second half contained only the even-numbered lines (2, 4, 6, 8…). Each half — called a field — could be transmitted in half the bandwidth a whole picture would need, so the engineers sent two fields in the time one whole frame would have taken. The viewer's TV stitched them together visually so fast that the brain saw one detailed picture refreshing 50 times per second, even though complete frames arrived only 25 times per second.
The trick worked because of two quirks of human vision. The phosphor coating on a CRT screen kept glowing for a tiny moment after the electron beam hit it, which softened the transition between fields. And your eye is slow enough that two interlocking half-pictures, drawn 1/50 of a second apart, look like one whole picture. Interlaced scan was, in effect, the first video compression trick — a 2× bandwidth saving in exchange for the visual sleight of hand. 3
Every major analog broadcast standard that followed inherited the same idea: NTSC in America used 525 lines interlaced at 60 fields per second (59.94 after colour was added in 1953), PAL in Europe used 625 lines interlaced at 50 Hz, and SECAM in France used similar numbers. 4 For the next 60 years, that's how almost all the television in the world was transmitted.
Figure 1. Progressive draws every line of a frame in one pass at one moment in time. Interlaced draws odd lines first, then even lines 1/50 (or 1/60) second later — so the two halves of a "frame" can already show different things if anything in the scene moved between them.
Progressive scan, and why it took over
Progressive scan is the modern alternative. It draws every line of every frame in order, top to bottom, in a single pass at a single moment in time. Each frame is one complete, coherent snapshot. The name comes from the fact that the lines progress straight down the picture instead of jumping between odd and even.
You don't have to design around bandwidth tricks anymore for three reasons that all became true in the 1990s and 2000s.
First, screens changed. The flat-panel LCD and OLED displays in your phone, laptop, and TV don't have an electron beam scanning across phosphor anymore — they have a fixed grid of pixels that holds each frame on screen until the next one replaces it. Showing odd lines and even lines as separate moments doesn't map onto how a modern screen works. Modern screens expect whole frames.
Second, compression got smart enough. Video codecs — the software algorithms that compress video so it can fit in a streaming bitrate — are designed around the assumption that each frame is one coherent snapshot. They look for patterns across a frame and between frames, and the math they use breaks down on interlaced data where the two halves of a frame show slightly different things. HEVC and AV1 have no interlace tools at all, and even H.264, which has them, runs in progressive mode in almost every streaming encoder and player, so interlaced material fed in as-is wastes bits and produces worse output. 5
Third, the internet doesn't care about analog bandwidth. The protocols that deliver video on the web — HLS, MPEG-DASH, WebRTC, CMAF — were all designed for progressive frames from day one. There's simply no clean path for an interlaced signal to reach a viewer through a modern streaming pipeline without being converted first.
The result: 720p, 1080p, 4K UHD, 8K — all of them are progressive by specification. The "p" in "1080p" actually stands for progressive. (The "i" in "1080i," which still shows up in some broadcast contribution feeds, stands for interlaced.) For any product you build in 2026, treat interlaced as a legacy input format you might receive from outside, never as something you produce yourself.
Is 1080i the same resolution as 1080p? Resolution and frame rate compared
1080i and 1080p have the same frame size, 1,920 × 1,080 pixels, but 1080i only ever captures 540 of those lines at any one moment. 6 On a still picture the two fields line up and you see the full 1,080 lines. As soon as something moves, the two fields disagree, and the effective vertical detail of the moving part drops toward 540 lines.
Frame rate is where the naming gets confusing. An interlaced signal sends two fields for every frame, so a European 1080i signal carries 25 frames but 50 fields per second. Written out:
fields per second = frames per second × 2
25 frames × 2 = 50 fields per second
The same signal is therefore labelled 1080i25 by people who count frames and 1080i50 by people who count fields; the European Broadcasting Union writes it 1080i/25. 6 North American 1080i is 29.97 frames, or 59.94 fields, per second. Before you set up a deinterlace step, find out which convention the person handing you the feed is using.
That doubled field rate is the one real advantage interlacing still has: motion is sampled 50 or 60 times per second, so sport looks smooth even though each sample has half the lines. It is also why a good deinterlacer can turn 1080i25 into 1080p50 rather than 1080p25 — the extra motion information is already in the source.
The same frame-versus-field logic applies to standard definition. DVDs are an interlaced 480i (NTSC) or 576i (PAL) format; video-shot discs store real fields, while film-sourced NTSC discs usually store 23.976 progressive frames with flags that tell the player to repeat fields (3:2 pulldown). A "progressive scan" DVD player deinterlaces the first kind, rebuilds the film frames of the second, and sends 480p or 576p to the TV, which avoids a second, often worse, conversion inside the television.
The combing artefact — and why it's so destructive
Here's where the abstract idea of "two fields per frame" becomes a concrete visual problem.
Imagine you're filming a soccer ball flying across the screen. With interlaced scan, the camera captures the odd lines of the picture at one moment, and the even lines 1/50 of a second later. During that 1/50 of a second, the ball has moved a few centimetres. So the odd lines see the ball in one position, and the even lines see it slightly to the right. If the TV correctly stitches them together visually, you don't notice — the eye and the CRT blend them into smooth motion.
But what happens if you take that interlaced data and try to display it as if it were progressive — for example, by writing both fields into a single image and showing that single image on a modern flat panel? The two halves don't blend anymore. The odd lines show the ball in its first position; the even lines show it in its second. Anywhere the ball's edge is, you see a horizontal sawtooth pattern — the famous combing artefact. 5
The sawtooth looks exactly like the teeth of a comb, hence the name. Static parts of the frame (the grass, the goalposts) don't show combing because nothing moved between the two fields; the odd and even lines line up perfectly. Combing appears only at moving edges.
Figure 2. Combing appears anywhere something moved between the two field captures. Static areas of the frame look fine; moving edges develop the characteristic "teeth" because the odd and even fields recorded slightly different positions.
Here is why this matters for encoding. Combing is not a display problem that goes away when the viewer's screen does its thing. The artefact is baked into the data the moment you treat two fields as if they were one frame. If you feed that combed frame to a modern codec, the codec sees those horizontal jaggies as real picture detail and compresses them. Bits get wasted encoding noise. Motion estimation — the part of the codec that figures out how each frame relates to the next — gets confused by all the high-frequency horizontal noise. The output stream ends up bigger and worse-looking than the source deserved.
This is why a well-built pipeline converts interlaced sources to progressive before encoding, not after. Once you've encoded a combed frame, you can still deinterlace the file later, but the bits spent on the teeth are gone and any scaling or chroma subsampling done on the woven frame has already blended the two fields.
Where interlaced video still exists in 2026
Interlacing has disappeared from screens, web video and Ultra HD, but it has not disappeared from the signals you receive. Two sources keep it alive.
Broadcast television. In the United States, 1080i is still the preferred format for most broadcasters; Fox- and Disney-owned networks use 720p instead. 6 Even the next-generation standard, ATSC 3.0, keeps interlaced HD as a legacy format: 1080-line interlaced video is limited to 30 frames per second and cannot use HDR, high frame rate or wide colour gamut, while the progressive formats go up to 4K at 120 fps. 7
Archives and older equipment. Tape archives, NTSC and PAL surveillance footage, DVDs and older medical and industrial cameras all record fields.
Ultra HD and modern codecs leave it behind. Ultra HD itself is progressive-only: ITU-R BT.2020 allows only progressive frame rates, from 23.976p to 120p. 8 The codecs follow the same trend, and it matters when you choose what to encode into:
| Codec | Interlaced support | What it means for your pipeline |
|---|---|---|
| MPEG-2 | Native field and frame coding | Still common in broadcast; the usual source of 1080i you will receive. |
| H.264 / AVC | Picture-adaptive (PAFF) and macroblock-adaptive (MBAFF) frame-field coding 9 | Can carry interlaced video efficiently. The Baseline profile has no field coding, so many web players never expect it. |
| H.265 / HEVC | No interlace coding tools; fields can be coded as separate pictures, with metadata saying so 10 | Players that ignore the metadata show half-height fields. Deinterlace first. |
| AV1 | None: the bitstream specification has no field or interlace mode 11 | Progressive input only. Deinterlace before an AV1 encode, every time. |
The practical rule: if your output is HEVC or AV1, which covers most modern streaming ladders, interlaced material must be converted before the encoder ever sees it.
Deinterlacing — do it once, do it right
The conversion process is called deinterlacing. It takes a two-field interlaced source and produces a series of full progressive frames the modern world can use. There are four families of deinterlacing algorithms, in order of how cheap and bad they are versus how expensive and good they are.
| Method | What it does | When to use it | Quality |
|---|---|---|---|
| Weave | Stick the odd and even fields together into one frame, exactly as captured. | Only safe if the scene is completely static — no motion at all. | Combs on every motion. |
| Bob (line doubling) | Turn each field into its own frame by doubling (or interpolating) its lines. | Cheap real-time conversion when you have no compute budget. | Half vertical detail per frame, edges flicker. |
| Motion-adaptive (YADIF, BWDIF) | Check every pixel to see if it moved between fields; weave the still areas, interpolate the moving ones. | The default for almost every production pipeline. | Production grade. |
| Motion-compensated (QTGMC, neural) | Build per-pixel motion vectors between fields; reconstruct missing samples along the actual paths of moving objects. | High-end restoration of old footage, archive work. | Best available; CPU/GPU heavy. |
For the overwhelming majority of jobs, the right answer is the motion-adaptive category — specifically a filter called BWDIF.
BWDIF (Bob Weaver Deinterlacing Filter) is a refinement of an older filter called YADIF (Yet Another DeInterlacing Filter, originally written for the MPlayer open-source video player by an engineer named Michael Niedermayer). 12 Both filters work by inspecting each pixel: if the pixel sits in a part of the frame that didn't move between the odd and even fields, they "weave" — they trust both fields and combine them directly. If the pixel sits in a region with motion, they "bob" — they discard the conflicting field and synthesise a replacement line from its neighbours. Both look at the previous, current and next frame to make that call. The difference is how the replacement line is built: BWDIF keeps YADIF's motion check but fills the gaps with the BBC R&D "w3fdif" filter coefficients and cubic interpolation, which holds fine detail and fast motion better. 13 Both ship inside the popular open-source video tool FFmpeg out of the box.
One default catches people out: BWDIF's default mode is send_field, which doubles the frame rate, while YADIF defaults to send_frame. 13 Always set the mode explicitly, as in the command below, so a filter swap never silently changes your output frame rate.
Here is the actual command — the one we run in production at Fora Soft for a 1080i source coming in over a broadcast SRT link:
# Deinterlace a 1080i source to 1080p25 using BWDIF, then re-encode to H.264.
# parity=tff only after idet has confirmed top field first; otherwise leave parity=auto.
ffmpeg -i in.ts -vf "bwdif=mode=send_frame:parity=tff" \
-c:v libx264 -preset slow -crf 18 -c:a copy out.mp4
The cryptic-looking part is the bwdif=mode=send_frame:parity=tff filter chain. mode=send_frame tells the filter to produce one progressive frame for every two interlaced fields — which keeps the frame rate the same as the source (1080i25 → 1080p25). The alternative is mode=send_field, which produces a progressive frame from every single field — doubling the frame rate (1080i25 → 1080p50) and preserving the smoothest possible motion. For camera-shot interlaced video, send_field keeps all the motion the camera recorded and is the safer default; use send_frame when your delivery ladder must stay at 25 or 30 fps. Film transferred to interlaced video is a different case: it needs inverse telecine (FFmpeg's fieldmatch and decimate filters) to rebuild the original film frames, not deinterlacing.
parity=tff tells the filter which of the two fields was captured first in time. The top field is the one that starts on the first line of the picture; "TFF" stands for "top field first," "BFF" for "bottom field first." Interlaced sources in the wild are not all the same; some send TFF, some send BFF, and getting the parity wrong produces a jittery output that looks like time is broken. It's a frustratingly hard problem to debug if you don't know it's the cause.
Always check parity before processing in bulk. The tool to use is ffprobe, which inspects a video file and reports its metadata, or the idet filter inside FFmpeg, which examines actual pixel data to detect parity rather than trusting the file's metadata flag. Run a 5-second sample of the source through idet and look at the result before you start a 4-hour batch job.
How to tell whether a video is progressive or interlaced
Two commands answer the "scan type: progressive or interlaced?" question in under a minute. The first reads what the file claims; the second measures what the pixels actually do:
# What the container and codec claim: progressive, tt (top field first), bb, tb or bt
ffprobe -v error -select_streams v:0 -show_entries stream=field_order -of default=nw=1 in.ts
# What the pixels say: classify the first 500 frames
ffmpeg -i in.ts -vf idet -frames:v 500 -an -f null -
The idet filter prints counts of frames it judged top-field-first, bottom-field-first, progressive or undetermined, and it also flags repeated fields — the fingerprint of telecined film. 14 If the flag and the measurement disagree, trust the measurement. MediaInfo shows the same flag as "Scan type". For mixed sources, where some frames are flagged interlaced and some are not, BWDIF's deint=interlaced option deinterlaces only the flagged frames and passes the rest through untouched. 13
Deinterlacing on the GPU
If your pipeline decodes and encodes on a GPU, copying frames back to the CPU just to deinterlace them wastes most of the speed-up. FFmpeg ships GPU versions of the same algorithms: yadif_cuda since FFmpeg 4.1, bwdif_cuda and bwdif_vulkan since FFmpeg 6.1, and deinterlace_d3d12 for Windows since FFmpeg 8.1 (March 2026). 15 As of October 2026 the newest stable release is FFmpeg 9.0.2 (September 2026). 16 A common pattern is to prototype with bwdif on the CPU and switch to bwdif_cuda or bwdif_vulkan once the rest of the pipeline runs on the GPU.
Common mistake: deinterlacing twice, or not at all
Two failure modes show up over and over in production audits. Both are easy to make and hard to detect after the fact.
Mistake 1: deinterlacing twice. A capture device deinterlaces on input (because the manufacturer's firmware does it automatically). Later in the pipeline, a transcoding step deinterlaces again (because the operator wasn't told the previous step had already done it). The double-conversion produces soft, smeared, slightly-jittery output that looks "wrong" but is hard to localise to one stage. Pick one place in your pipeline to deinterlace, do it carefully, and clearly label the result as progressive in your metadata so nobody downstream tries to deinterlace it a second time.
Mistake 2: deinterlacing never happens. Someone uploads "1080i25" footage to a pipeline that assumes everything is progressive. The encoder happily processes the data as if it were progressive — and bakes combing into every motion-heavy frame in the output. The viewer sees teeth on everything that moves, and the damage is hard to undo: deinterlacing the encoded file afterwards recovers only part of the picture, and a clean re-encode from the original source is the only full fix.
The fix for both: have one clearly-labelled deinterlace step in your ingest pipeline, immediately after the source enters your system. Mark the output as "progressive — already deinterlaced." Every subsequent stage trusts that label and does not re-process.
Frequently asked questions
Which is better, progressive or interlaced?
Progressive. It shows a complete frame on every refresh, has no combing, and is the only format modern screens, streaming protocols and codecs such as HEVC and AV1 are designed for. Interlaced only made sense when analog bandwidth was scarce.
Is 1080p better than 1080i?
Yes. Both are 1,920 × 1,080 pixels, but 1080p captures all 1,080 lines at once, while 1080i captures 540 lines per field, so moving objects lose vertical detail and can show combing. 1080i's one advantage, 50 or 60 motion samples per second, is matched by 1080p50 or 1080p60.
Which statement correctly describes progressive scan video?
Progressive scan video shows the full frame in each refresh cycle, drawing every line from top to bottom in one pass. Displaying odd and even lines in alternating fields describes interlaced video, not progressive.
What does "interlaced vs non-interlaced" mean?
"Non-interlaced" is another name for progressive scan. An interlaced video splits each frame into two fields of alternating lines; a non-interlaced video stores and shows every frame whole.
Does interlaced video have a higher frame rate?
It has a higher field rate, not a higher frame rate. 1080i25 carries 25 full frames but 50 fields per second, which is why it is also labelled 1080i50 and why it can be deinterlaced to 1080p50.
Is 4K ever interlaced?
No. Ultra HD (ITU-R BT.2020) allows only progressive frame rates, and ATSC 3.0 restricts interlaced video to 1080-line HD. 4K and 8K are always progressive.
What is progressive scan on a DVD player?
DVDs are an interlaced 480i or 576i format. A progressive scan DVD player converts the disc to 480p or 576p itself, deinterlacing video-shot material and rebuilding the original frames of film-sourced discs, so the TV does not have to.
How do I check whether a file is interlaced?
Run ffprobe and read the field_order value, then confirm with FFmpeg's idet filter, which measures the actual pixels. MediaInfo shows the same information as "Scan type".
Where Fora Soft fits in
We deal with interlaced sources regularly. Telemedicine systems often receive 1080i contribution feeds over SRT from older hospital equipment. Surveillance archives reach back into NTSC and PAL eras when the cameras were inherently interlaced. Broadcast partners sometimes hand off feeds in 1080i25 that need to land on the public web as 1080p25 or 1080p50 — work that lives inside our video and audio streaming practice, and in the OTT and IPTV platforms we build, where live 1080i channels have to reach phones and smart TVs as clean progressive HLS. The fix is always a small, careful piece of pipeline glue — a parity-detection step that runs idet on a sample, a deinterlace filter chosen to match the content type, and clean progressive output that every downstream codec and player will accept. The principles in this article are the ones we apply every time.
The book
Video Encoding: A Complete Guide to Video Compression
Deinterlacing is one filter in a much longer chain. The book walks the rest of it in the same plain language across 1,500+ pages — how a codec predicts, transforms and quantises a frame, why motion estimation suffers on the high-frequency noise combing leaves behind, and how rate control and quality metrics decide what your output finally looks like. Written by Nikolay Sapunov, CEO at Fora Soft.
Receiving 1080i feeds you have to put on the web?
Tell us where the interlaced material comes from and we will tell you where the deinterlace step belongs, which filter fits the content, and what it costs to run. 250+ video products shipped since 2005.
See our case studies
Case study
Mindbox
AI video management in 50+ deployments across transport, pharma and gated communities: RTSP ingest from cameras of every vintage, normalised by FFmpeg before HLS delivery.
Case study
Worldcast Live
Live concert feeds landing on the public web as 1.5 Gb/s HD at 0.4–0.5 s latency for 10,000 simultaneous viewers, with quality that adapts when a connection drops.
Case study
Speed.Space
Remote production used on Netflix, EA and HBO shoots, where the crew sets resolution, frame rate, codec and bitrate per shoot — 1080p at 8 Mbps recorded locally.
What to read next
Foundations
What is Digital Video: From Analog Signal to Bits
Where scan lines, frames and bits come from — one step before this article starts.
Motion
Frame Rate: 24, 60, 120 fps, Judder and Motion Blur
Why send_field doubles the frame rate to 1080p50, and when that is worth the extra bits.
Pipeline
Transcoding Pipeline: Decode, Filter, Encode, Mux
Which stage the deinterlace filter belongs to, and what runs before and after it.
Tooling
FFmpeg: A Must-Know Cheat Sheet for Developers
The commands around bwdif: idet parity detection, scaling, and the encode that follows.
Additional supporting references: FFmpeg official documentation on the bwdif, yadif, idet and GPU deinterlacing filters (checked October 2026) at https://ffmpeg.org/ffmpeg-filters.html · Progressive scan, Wikipedia, https://en.wikipedia.org/wiki/Progressive_scan · Interlace: Part 1 — It Began In The 1930s, The Broadcast Bridge, https://www.thebroadcastbridge.com/content/entry/19116/interlace-part-1-it-began-in-the-1930s
-
Mechanics of interlaced capture and display; field rate, frame rate. Wikipedia: Interlaced video, accessed October 2026. https://en.wikipedia.org/wiki/Interlaced_video ↩
-
1936 UK 405-line interlaced television; thermionic-valve scan-rate constraints. Interlacing — the hidden story of 1920s video compression technology, BECG, accessed May 2026. https://becg.org.uk/2018/12/16/interlacing-the-hidden-story-of-1920s-video-compression-technology/ ↩
-
Interlacing as a 2× bandwidth-conservation compromise. Understanding interlace, TV Tech, accessed May 2026. https://www.tvtechnology.com/news/understanding-interlace-268148 ↩
-
NTSC adopted monochrome 1941, colour update 1953; PAL patented 1962 by Telefunken. Wikipedia: NTSC, accessed May 2026. https://en.wikipedia.org/wiki/NTSC ↩
-
Combing, and why modern codecs prefer progressive: motion estimation and intra prediction assume coherent frames. Wikipedia: Deinterlacing, accessed October 2026. https://en.wikipedia.org/wiki/Deinterlacing ↩
-
1080i frame size, US broadcaster formats (1080i for most networks, 720p for Fox and Disney), 1080i25 / 1080i30 naming and EBU 1080i/25 notation. Wikipedia: 1080i, accessed October 2026. https://en.wikipedia.org/wiki/1080i ↩
-
ATSC 3.0 video formats: legacy SD, interlaced HD (1080 lines, up to 30 fps, no HDR/HFR/WCG) and progressive up to 2160p120. Wikipedia: ATSC 3.0, accessed October 2026. https://en.wikipedia.org/wiki/ATSC_3.0 ↩
-
ITU-R BT.2020: "Only progressive scan frame rates are allowed", 23.976p to 120p. Wikipedia: Rec. 2020, accessed October 2026. https://en.wikipedia.org/wiki/Rec._2020 ↩
-
H.264 picture-adaptive (PAFF) and macroblock-adaptive (MBAFF) frame-field coding; Baseline-type profiles without field coding. Wikipedia: Advanced Video Coding, accessed October 2026. https://en.wikipedia.org/wiki/Advanced_Video_Coding ↩
-
HEVC: "no coding tools were added specifically for interlaced video"; fields sent as separate pictures with metadata (SAFF). Wikipedia: High Efficiency Video Coding, accessed October 2026. https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding ↩
-
AV1 Bitstream & Decoding Process Specification: defines no field or interlaced coding mode. Alliance for Open Media, accessed October 2026. https://aomediacodec.github.io/av1-spec/ ↩
-
YADIF deinterlacing filter; spatial and temporal checks across previous, current, next frames. Wikipedia: Deinterlacing, accessed May 2026. https://en.wikipedia.org/wiki/Deinterlacing ↩
-
bwdif: "motion adaptive deinterlacing based on yadif with the use of w3fdif and cubic interpolation"; defaults mode=send_field, parity=auto, deint=all. FFmpeg Filters Documentation, accessed October 2026. https://ffmpeg.org/ffmpeg-filters.html#bwdif ↩
-
idet: detects interlaced, progressive, top- or bottom-field-first frames and repeated fields (telecine). FFmpeg Filters Documentation, accessed October 2026. https://ffmpeg.org/ffmpeg-filters.html#idet ↩
-
yadif_cuda (4.1), bwdif_cuda and bwdif_vulkan (6.1), deinterlace_d3d12 (8.1). FFmpeg Changelog and FFmpeg 8.1 "Hoare" release notes, 16 March 2026, accessed October 2026. https://ffmpeg.org/ ↩
-
FFmpeg 9.0.2 "Lei", released 2026-09-18. FFmpeg Download, accessed October 2026. https://ffmpeg.org/download.html ↩
