Interlace check: Difference between revisions
New page: Hybrid's interlace check (Analyse button), including the repeated-frames hint (via create-page on MediaWiki MCP Server) |
Add screenshot (via update-page on MediaWiki MCP Server) |
||
| Line 3: | Line 3: | ||
''Filtering → (De-)Interlace/Telecine → Analyse'' | ''Filtering → (De-)Interlace/Telecine → Analyse'' | ||
[[File:Interlace_check.png|none|Interlace check controls in Hybrid]] | |||
== What it does == | == What it does == | ||
Latest revision as of 21:36, 17 November 2026
The interlace check looks at the decoded frames of the source and decides its scan type: progressive, top or bottom field first, telecine, mixed or field-shifted. Stream headers are often wrong, so Hybrid uses this result instead of the header value.
Filtering → (De-)Interlace/Telecine → Analyse

What it does
Pressing Analyse checks the given percentage of the source. The result is shown next to Input scan type and replaces the scan type from the stream headers. The reason for the result is written to the Filter log (Reason: … right before interlaced check result); the full numbers go to the analysis log.
With Vapoursynth available (also when no Vapoursynth filter is used), Hybrid loads the source through the same source filter line its scripts use and looks at five sections spread over the whole source, each with at least 300 frames. Three measurements run over the same frames:
- Field matching (VFM) with both field orders: how many frames match a field of a neighbouring frame, how many stay combed after matching, and whether the matches repeat in a fixed cycle (every 5 frames: telecine, every 6 frames: 25 fps brought to 29.97 fps).
- ffmpeg's idet: how many frames look interlaced and how many repeat a field.
- Bob motion with both field orders: the clip is bobbed and the motion between the fields is measured. Motion that stops between the two fields of a frame is progressive, motion that stops between frames means the fields belong to neighbouring frames (field-shifted), and motion that turns back and forth shows the wrong field order.
Without Vapoursynth, or when the Vapoursynth run fails, only idet runs over the first part of the source (the given percentage).
Repeated frames
For a progressive result, Hybrid also counts frames that repeat the previous one. If at least 10% of the frames repeat and the repeats follow a fixed cycle, the reason names that cycle, e.g.
Reason: idet finds 0% of the frames interlaced and field matching leaves 0% combed; 35% of the frames repeat the previous one, regularly every 2 frames (0.71): decimating with cycle 2 would remove them
The scan type stays progressive; the hint only tells you that decimation (e.g. TDecimate with that cycle) would remove the repeats. Repeats without a fixed cycle (occasional duplicates, re-encoded duplicates that are not exact copies) get no hint; for those, look at the duplicate frame filters instead.
Settings
| Control | Range / values | Hybrid default | Meaning |
|---|---|---|---|
| Analyse | button | – | Runs the check. Disabled while Overwrite input scan type to is on. |
| % (next to Analyse) | 0.01 – 100 | 5 | Share of the source that is checked. With Vapoursynth it sets the length of each of the five sections (at least 300 frames each); without Vapoursynth it is the share from the start that idet reads. A higher value can help with sources whose scan type changes. |
| Misc → Automation → Extended Checks → Interlaced check | on/off | off | Runs the check automatically for every new source and adjusts the input scan type. |
Example
The analysis log of a 50 fps source whose every second frame is a copy of the previous one (shortened):
field matching (tff), 385 frames: p 0%, n 0%, combed after matching 0% matches repeat every 5 frames: -, every 6 frames: -, at shorter distances: 0.00 repeated frames after matching: 35%, most regular every 2 frames: 0.71 reason: idet finds 0% of the frames interlaced and field matching leaves 0% combed; 35% of the frames repeat the previous one, regularly every 2 frames (0.71): decimating with cycle 2 would remove them => progressive
How Hybrid uses it
- The result becomes the input scan type and drives the deinterlacer or inverse telecine selection, see Overwrite input scan type for how each scan type is handled.
- The result is kept per source, stream and percentage; loading the same source again reuses it instead of running the check again.
- With Overwrite input scan type to on, the check does not run and the overwritten value is used.
- No detection is always right. If the check gets a source wrong, use Overwrite input scan type and share a short sample with the Hybrid author.
Sources
- Hybrid's tooltips
- Hybrid's analysis and filter log