Papers › EDVR: Video Restoration with Enhanced Deformable Convolutional Networks
EDVR: Video Restoration with Enhanced Deformable Convolutional Networks
Xintao Wang, Kelvin C. K. Chan, Ke Yu, Chao Dong, Chen Change Loy
Video restoration tasks, including super-resolution, deblurring, etc, are drawing increasing attention in the computer vision community. A challenging benchmark named REDS is released in the NTIRE19 Challenge. This new benchmark challenges existing methods from two aspects: (1) how to align multiple frames given large motions, and (2) how to effectively fuse different frames with diverse motion and blur. In this work, we propose a novel Video Restoration framework with Enhanced Deformable networks, termed EDVR, to address these challenges. First, to handle large motions, we devise a Pyramid, Cascading and Deformable (PCD) alignment module, in which frame alignment is done at the feature level using deformable convolutions in a coarse-to-fine manner. Second, we propose a Temporal and Spatial Attention (TSA) fusion module, in which attention is applied both temporally and spatially, so as to emphasize important features for subsequent restoration. Thanks to these modules, our EDVR wins the champions and outperforms the second place by a large margin in all four tracks in the NTIRE19 video restoration and enhancement challenges. EDVR also demonstrates superior performance to state-of-the-art published methods on video super-resolution and deblurring. The code is available at https://github.com/xinntao/EDVR.
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):
get_harvested_code_for_paper(arxiv_id="1905.02716")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="1905.02716", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="1905.02716")
Code
The archive's official repository (xinntao/EDVR) was not harvested; the 19 samples below come from 2 community repositories.
Syntology 19 code samples harvested from 2 repositories linked to this paper: 15 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 1 honoured, 0 violated, 11 with no contract checked; 3 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: community (archive-listed): 19 samples from 2 repositories, 15 ran (12 with no instrument failure; 3 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.
No sample is linked to this paper from 2 of its repositories that Syntology harvested for other papers:
- Pea-Shooter/ADNet, community (archive-listed): harvested for another paper, listed under the repository
- YapengTian/TDAN-VSR-CVPR-2020, community (archive-listed): harvested for another paper, listed under the repository
Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
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.
A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.
Code Syntology ran Syntology
19 samples harvested: 15 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 1 honoured, 0 violated, 11 with no contract checked; 3 where Syntology's instrument failed) · 4 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.
Licence: 5 of the 19 samples are pointer only, meaning Syntology does not serve that copy's text. For 5 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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”. For 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “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.
a3c1e35e4ff68673 · report
fixture: signature Rx:Tensor/4/float, scale:int/0/int · returned Tensor · level recorded 2026-09-24 9394ff2c25b8a988 · report
fixture: signature img1:ndarray/3/int, img2:ndarray/3/int · returned float · level recorded 2026-09-24 40c52ad98161c17b · report
fixture: signature opt:dict/0/?, indent_l:int/0/int · returned str · level recorded 2026-09-22 ada7273eee7081c7 · report
fixture: signature opt:dict/0/? · returned NoneDict · level recorded 2026-09-22 7018e324f2150c43 · report
fixture: signature x:Tensor/4/float, flow:Tensor/4/float, interp_mode:str/0/str, padding_mode:str/0/str · returned Tensor · level recorded 2026-09-24 c04a23de0531da4a · report
fixture: signature block:callable/0/?, n_layers:int/0/int · returned Sequential · level recorded 2026-09-22 e47a76b039b007e1 · report
fixture: signature path:str/0/str, key:str/0/str · returned tuple · level recorded 2026-09-24 1b40b4f3f0ea0b6e · report
fixture: returned ndarray · level recorded 2026-09-24 ce4ad67a16f94299 · report
54b6d9dc8ce868bb · report
fixture: signature keys:list/1/str · returned dict · level recorded 2026-09-25 2c460a151351c467 · report
fixture: signature data_cfg:dict/0/? · returned dict · level recorded 2026-09-25 0ce4b91d8aca61e4 · report
fixture: signature metric_mapping:dict/0/?, summary_data:dict/0/? · returned dict · level recorded 2026-09-25 8e5814637d5291d6 · report
fixture: signature lines:list/1/str, i:int/0/int · returned bool · level recorded 2026-09-25 4214819cf4b6bd8d · report
fixture: signature root:str/0/str, proc:MockProc/0/? · returned list · level recorded 2026-09-25 4bbabfed79ffbff3 · report
fixture: signature config:dict/0/?, args:Args/0/? · returned dict · level recorded 2026-09-25 185156d990381282 · report
fixture: signature md_file:str/0/str · returned bool · level recorded 2026-09-25 eda5ede48a264b22 · report
cee4c863ad3de58e · report
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Deblurring | REDS | EDVR_Deblur | Average PSNR | 34.80 | #2 of 3 | Archive leaderboard | report |
| Video Enhancement | MFQE v2 | EDVR | Incremental PSNR | 0.75 | #4 of 6 | Archive leaderboard | report |
| Video Super-Resolution | Vid4 - 4x upscaling | EDVR | PSNR | 27.35 | #13 of 27 | Archive leaderboard | report |
| Video Super-Resolution | Vid4 - 4x upscaling | EDVR | SSIM | 0.8264 | #13 of 27 | Archive leaderboard | report |
| Video Super-Resolution | Vid4 - 4x upscaling - BD degradation | EDVR | PSNR | 27.85 | #10 of 18 | Archive leaderboard | report |
| Video Super-Resolution | Vid4 - 4x upscaling - BD degradation | EDVR | SSIM | 0.8503 | #10 of 18 | 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.
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