- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes ReCaVSR, a one-step streaming video super-resolution framework based on Wan2.2. The main idea is to reuse the SR latents from the previous block to provide local temporal information, and to learn a separate KV-cache policy for each transformer layer. The learned policies are fixed during inference to reduce computation and memory costs. The paper also introduces a Multi-Scope Query discriminator for global, spatial, and temporal supervision, and adds LR conditioning to FlashDecoder for efficient decoding. Training includes VSR adaptation, cache-route learning, and sequential self-rollout adversarial training. Experiments cover synthetic and real-world benchmarks, long videos, ablation studies, and a user study. The reported results show a favorable balance between perceptual quality and inference efficiency.
Critical strengths
The method uses recycled SR latents to provide local temporal information, and keeps additional historical KV states only in selected layers. Table 4 shows that, compared with Uniform (3R), the proposed configuration reduces KV memory from 6.44 GB to 2.17 GB and historical-attention FLOPs to 0.28×, while DOVER only decreases from 0.5601 to 0.5587. These results show that the method can substantially reduce cache costs while largely maintaining perceptual quality.
In Table 5, the total number of queries, discriminator backbone, and training settings are kept the same. Using all three query scopes gives better NIQE, MUSIQ, and DOVER than using only global queries or two query scopes. This supports the usefulness of combining global supervision with local spatial and temporal supervision.
Critical weaknesses
ReCaVSR and FlashVSR share a similar overall pipeline: sparse attention, a lightweight decoder, and streaming inference. However, ReCaVSR uses Wan2.2-TI2V-5B, whereas the original FlashVSR Tiny is based on Wan2.1-1.3B. Besides the differences in model version and size, Wan2.2-TI2V-5B uses a VAE with higher spatial compression: its temporal–spatial downsampling factors are 4×16×16, compared with 4×8×8 for Wan2.1. With the same patch size, this results in roughly one quarter as many spatial DiT tokens at the same output resolution. Therefore, the backbone change also affects the computational workload. Although the paper provides component ablations, it remains unclear how much of the reported quality improvement and overall speedup comes from the proposed method, and how much comes from the backbone and its more compressed latent representation. Moreover, the cache ablation changes both layer-wise allocation and anchor access relative to the uniform-window baselines, leaving the specific contribution of learned allocation insufficiently isolated.
I watched the demo videos on the project page, but did not see an obvious visual-quality advantage over FlashVSR Tiny. The paper reports improvements in several metrics, but it remains unclear whether these improvements correspond to a noticeable difference in the videos. In the user study, the reported gains over FlashVSR Tiny are 0.06, 0.09, and 0.18 points for overall quality, detail quality, and temporal stability, respectively, without uncertainty estimates. In addition, the MSQ ablation does not directly evaluate texture flicker or discontinuities between generated blocks, and the temporal metrics on LongVSR60 do not consistently favor ReCaVSR. Overall, the magnitude and reliability of the claimed perceptual and fine-detail temporal improvements over FlashVSR Tiny remain insufficiently established. Nevertheless, maintaining comparable quality at substantially lower runtime and memory would itself be a meaningful benefit.
I acknowledge the value of the reported quality–efficiency tradeoff. My main reservation is that the current controls do not sufficiently establish the benefit of learning the layer-wise cache assignment beyond simpler matched-budget alternatives, while the magnitude of the claimed temporal-quality improvement remains uncertain. These unresolved questions about the central contribution are the main reason for my weak-reject recommendation.
Questions for authors
Can the authors compare against a FlashVSR-style baseline using the same Wan2.2 backbone, latent compression ratio, training data, and training budget, or conduct ablations by replacing the corresponding components in ReCaVSR with those from FlashVSR under these matched conditions? A runtime breakdown for the DiT, including historical attention, and the decoder would also help clarify how much of the efficiency gain comes from the proposed designs rather than the backbone’s higher latent compression.
Since the visual difference from FlashVSR Tiny is not obvious in the demo videos, can the authors provide confidence intervals for the differences in user ratings, together with an evaluation that directly measures texture flicker or block-boundary discontinuities? This would help determine whether the reported quality improvements are reliable and perceptible.