Vapoursynth MVToolsFPS: Difference between revisions
New filter page (via create-page on MediaWiki MCP Server) |
Update to current Hybrid behaviour; code as <pre> (via update-page on MediaWiki MCP Server) |
||
| Line 19: | Line 19: | ||
|- | |- | ||
| Precision || pel || pixel, half pixel, quarter pixel || half pixel || Accuracy of the motion vectors (pel 1/2/4). | | Precision || pel || pixel, half pixel, quarter pixel || half pixel || Accuracy of the motion vectors (pel 1/2/4). | ||
|- | |||
| thSCD1 / thSCD2 || thscd1, thscd2 || 0 – 16320 / 0 – 255 || 400 / 130 || Scene change detection of FlowFPS: a block counts as changed above thSCD1 (SAD), a frame counts as a scene change when more than thSCD2 (on a 0 – 255 scale) of its blocks changed; frames at a scene change are not motion-interpolated. | |||
|- | |- | ||
| Tools: MV || – || mvgpu, mvutensils, mv || mvgpu with a discrete GPU, otherwise a CPU implementation || Implementation; mvgpu runs on Vulkan (VapourSynth R82 or newer, Windows/Linux) and ignores the search settings. | | Tools: MV || – || mvgpu, mvutensils, mv || mvgpu with a discrete GPU, otherwise a CPU implementation || Implementation; mvgpu runs on Vulkan (VapourSynth R82 or newer, Windows/Linux) and ignores the search settings. | ||
| Line 25: | Line 27: | ||
== Example == | == Example == | ||
Default settings on a 10-bit YUV 4:2:0 source (640x356, 25 fps), interpolated to 50 fps: | Default settings on a 10-bit YUV 4:2:0 source (640x356, 25 fps), interpolated to 50 fps: | ||
< | <pre> | ||
# Interpolating frames with MVTools | # Interpolating frames with MVTools | ||
sup = core.mvu.Super(clip, pel=2, blksize=[16, 16], overlap=[0, 0]) | sup = core.mvu.Super(clip, pel=2, blksize=[16, 16], overlap=[0, 0]) | ||
bvec = core.mvu.Analyse(sup, blksize=[16, 16], overlap=[0, 0], delta=1, chroma=True, search=1, searchparam=1) | bvec = core.mvu.Analyse(sup, blksize=[16, 16], overlap=[0, 0], delta=1, chroma=True, search=1, searchparam=1) | ||
fvec = core.mvu.Analyse(sup, blksize=[16, 16], overlap=[0, 0], delta=-1, chroma=True, search=1, searchparam=1) | fvec = core.mvu.Analyse(sup, blksize=[16, 16], overlap=[0, 0], delta=-1, chroma=True, search=1, searchparam=1) | ||
clip = core.mvu.FlowFPS(clip, sup, vectors=[bvec, fvec], num=50, den=1, extramask=True) # new fps: 50 | clip = core.mvu.FlowFPS(clip, sup, vectors=[bvec, fvec], num=50, den=1, extramask=True, thscd1=400, thscd2=50.78) # new fps: 50 | ||
</ | </pre> | ||
== How Hybrid calls it == | == How Hybrid calls it == | ||
* The target rate is the ''Target fps'' value. If it is not higher than the current frame rate, the filter is skipped with a note in the script and the frame rate stays. | * The target rate is the ''Target fps'' value. If it is not higher than the current frame rate, the filter is skipped with a note in the script and the frame rate stays. | ||
* Super, Analyse (backward and forward) and FlowFPS are called with fixed extra settings: chroma is used in the search, exhaustive search with radius 1, no overlap; | * Super, Analyse (backward and forward) and FlowFPS are called with fixed extra settings: chroma is used in the search, exhaustive search with radius 1, no overlap; the Super clip keeps the plugin's default padding (16). With mv FlowFPS uses mask 2, with mvutensils/mvgpu an extra occlusion mask is used; for mvutensils thSCD2 is converted to its percentage scale. | ||
* All settings are always written. All YUV formats are accepted, no conversion is needed. | * All settings are always written. All YUV formats are accepted, no conversion is needed. | ||
Latest revision as of 09:50, 16 November 2026
MVToolsFPS is classic motion-compensated frame rate conversion with MVTools: new frames are built by moving pixels along the motion vectors between neighbor frames. No neural network is involved, and it is always available.
Filtering → Vapoursynth → Frame → Interpolation

What it does
MVTools searches backward and forward motion vectors between each pair of frames. FlowFPS then renders the new frames with per-pixel flow and masks occluded areas. Quality depends on how well the motion can be estimated: complex or very fast motion can produce warping artifacts.
Settings
Tick Frame Interpolation and pick MVToolsFPS in the method list. It is the default method when SVPflow (Interframe/SVP) is not available.
| Control | Parameter | Range / values | Hybrid default | Meaning |
|---|---|---|---|---|
| Target fps | num, den | 1 – 999 | 25 | Target frame rate (absolute), written as an exact fraction. |
| Blocksize | blksize | 4, 8, 16, 32 | 16 | Block size of the motion search; smaller blocks follow detail better but are slower and noisier. |
| Precision | pel | pixel, half pixel, quarter pixel | half pixel | Accuracy of the motion vectors (pel 1/2/4). |
| thSCD1 / thSCD2 | thscd1, thscd2 | 0 – 16320 / 0 – 255 | 400 / 130 | Scene change detection of FlowFPS: a block counts as changed above thSCD1 (SAD), a frame counts as a scene change when more than thSCD2 (on a 0 – 255 scale) of its blocks changed; frames at a scene change are not motion-interpolated. |
| Tools: MV | – | mvgpu, mvutensils, mv | mvgpu with a discrete GPU, otherwise a CPU implementation | Implementation; mvgpu runs on Vulkan (VapourSynth R82 or newer, Windows/Linux) and ignores the search settings. |
Example
Default settings on a 10-bit YUV 4:2:0 source (640x356, 25 fps), interpolated to 50 fps:
# Interpolating frames with MVTools sup = core.mvu.Super(clip, pel=2, blksize=[16, 16], overlap=[0, 0]) bvec = core.mvu.Analyse(sup, blksize=[16, 16], overlap=[0, 0], delta=1, chroma=True, search=1, searchparam=1) fvec = core.mvu.Analyse(sup, blksize=[16, 16], overlap=[0, 0], delta=-1, chroma=True, search=1, searchparam=1) clip = core.mvu.FlowFPS(clip, sup, vectors=[bvec, fvec], num=50, den=1, extramask=True, thscd1=400, thscd2=50.78) # new fps: 50
How Hybrid calls it
- The target rate is the Target fps value. If it is not higher than the current frame rate, the filter is skipped with a note in the script and the frame rate stays.
- Super, Analyse (backward and forward) and FlowFPS are called with fixed extra settings: chroma is used in the search, exhaustive search with radius 1, no overlap; the Super clip keeps the plugin's default padding (16). With mv FlowFPS uses mask 2, with mvutensils/mvgpu an extra occlusion mask is used; for mvutensils thSCD2 is converted to its percentage scale.
- All settings are always written. All YUV formats are accepted, no conversion is needed.
Background
MVTools
The VapourSynth plugin is a port of MVTools 2.5.11.20 and works on gray and YUV clips up to 16 bit on the CPU. FlowFPS blends frames at scene changes by default (blend=True with the plugin's own scene thresholds); Hybrid leaves these at the plugin defaults. mvutensils and its Vulkan variant mvutensilsvk provide the same Super/Analyse/FlowFPS chain.
Sources
- vapoursynth-mvtools
- Hybrid's tooltips