Papers › Zooming Slow-Mo: Fast and Accurate One-Stage Space-Time Video Super-Resolution

Zooming Slow-Mo: Fast and Accurate One-Stage Space-Time Video Super-Resolution

26 Feb 2020CVPR 2020 6arXiv:2002.11616archive 2025-07-28

Xiaoyu Xiang, Yapeng Tian, Yulun Zhang, Yun Fu, Jan P. Allebach, Chenliang Xu

In this paper, we explore the space-time video super-resolution task, which aims to generate a high-resolution (HR) slow-motion video from a low frame rate (LFR), low-resolution (LR) video. A simple solution is to split it into two sub-tasks: video frame interpolation (VFI) and video super-resolution (VSR). However, temporal interpolation and spatial super-resolution are intra-related in this task. Two-stage methods cannot fully take advantage of the natural property. In addition, state-of-the-art VFI or VSR networks require a large frame-synthesis or reconstruction module for predicting high-quality video frames, which makes the two-stage methods have large model sizes and thus be time-consuming. To overcome the problems, we propose a one-stage space-time video super-resolution framework, which directly synthesizes an HR slow-motion video from an LFR, LR video. Rather than synthesizing missing LR video frames as VFI networks do, we firstly temporally interpolate LR frame features in missing LR video frames capturing local temporal contexts by the proposed feature temporal interpolation network. Then, we propose a deformable ConvLSTM to align and aggregate temporal information simultaneously for better leveraging global temporal contexts. Finally, a deep reconstruction network is adopted to predict HR slow-motion video frames. Extensive experiments on benchmark datasets demonstrate that the proposed method not only achieves better quantitative and qualitative performance but also is more than three times faster than recent two-stage state-of-the-art methods, e.g., DAIN+EDVR and DAIN+RBPN.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

The archive's official repository (Mukosame/Zooming-Slow-Mo-CVPR-2020) was not harvested; the 8 samples below come from 1 community repository.

Syntology 8 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 2 honoured, 0 violated, 4 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 8 samples from 1 repository, 7 ran (6 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 7 samples that ran has no recorded date.

Mukosame/Zooming-Slow-Mo-CVPR-2020 officialmentioned in papermentioned on GitHubpytorchGPL-3.0Syntology: not harvested report
YapengTian/TDAN-VSR-CVPR-2020 mentioned on GitHubpytorchMITSyntology: 8 samples, 7 ran (1 instrument-failed) · 1 unverified report
YapengTian/TDAN_VSR mentioned on GitHubpytorchMITSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

8 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 2 honoured, 0 violated, 4 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · honoured contract
1ran · our draft was wrong
4ran
1unverified

Licence: 0 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from YapengTian/TDAN-VSR-CVPR-2020. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

YapengTian/TDAN-VSR-CVPR-2020 community (archive-listed) 8 samples, 7 ran (1 instrument-failed) · 1 unverified
create_window in 82 papers pytorch_ssim.py ran · honoured contract fingerprinted MIT (permissive) · 6154e3744ece5728 · report fixture: signature window_size:int/0/int, channel:int/0/int · returned Tensor · level recorded 2026-09-22
default_conv in 70 papers model.py ran MIT (permissive) · 632c987c9fa2059e · report fixture: signature in_channelss:int/0/int, out_channels:int/0/int, kernel_size:int/0/int, bias:bool/0/bool · returned Conv2d · level recorded 2026-09-24
gaussian in 218 papers
census: 8 implementations from 9 papers, 8 distinct outputs across 4 buckets, one shared input per bucket
pytorch_ssim.py ran · honoured contract fingerprinted MIT (permissive) · c56b7ef16f309a45 · report fixture: signature window_size:int/0/int, sigma:float/0/float · returned Tensor · level recorded, date not recorded
get_loss_fn in 12 papers loss.py ran MIT (permissive) · d4e819ca1651f5bd · report fixture: signature model_name:str/0/str · returned MSELoss · level recorded 2026-09-24
quantize in 70 papers
census: 8 implementations from 11 papers, 6 distinct outputs across 3 buckets, one shared input per bucket
solver.py ran fingerprinted MIT (permissive) · 91df9c98a6149376 · report fixture: signature img:Tensor/4/float, rgb_range:float/0/float · returned Tensor · level recorded 2026-09-24
rgb2ycbcrT solver.py ran MIT (permissive) · 2c13e8beeb2c3688 · report fixture: signature rgb:Tensor/3/float · returned Tensor · level recorded 2026-09-24
ssim in 112 papers pytorch_ssim.py ran · our draft was wrong fingerprinted MIT (permissive) · 9151c793f90473f0 · report fixture: signature img1:Tensor/4/float, img2:Tensor/4/float, window_size:int/0/int, size_average:bool/0/bool · returned Tensor · level recorded 2026-09-26
chop_forward solver.py unverified MIT (permissive) · 6e8be0c98c405673 · report

Tasks

Space-time Video Super-resolutionSuper-ResolutionVideo Frame InterpolationVideo Super-Resolution

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Video Frame Interpolation Vid4 - 4x upscaling Zooming Slow-Mo PSNR 26.31 #4 of 5 Archive leaderboard report
Video Frame Interpolation Vid4 - 4x upscaling Zooming Slow-Mo Parameters 11100000 #4 of 5 Archive leaderboard report
Video Frame Interpolation Vid4 - 4x upscaling Zooming Slow-Mo SSIM 0.7976 #4 of 5 Archive leaderboard report
Video Frame Interpolation Vid4 - 4x upscaling Zooming Slow-Mo runtime (s) 0.0606 #4 of 5 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

ConvLSTMConvolutionSigmoid ActivationTanh Activation

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections