- Rating
- 1
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes VeloForesight, a training-free sampling acceleration method for flow-based image and video generation models. The method reduces the number of network evaluations by extrapolating velocity estimates from previously computed outputs. It leverages first- and second-order temporal differences between recent exact velocity evaluations to estimate the velocity at skipped sampling steps. To prevent potentially unstable extrapolation, the method introduces a reliability control mechanism.
The proposed framework further incorporates residual calibration and clean-state feedback to correct the extrapolated velocities, as well as a noise-progress-based strategy for allocating exact model evaluations. The authors evaluate the method on image and video generation models, comparing it against existing acceleration methods, including TaylorSeer, Spectrum, and an adapted version of VDE. The experimental results demonstrate improved inference efficiency and generally competitive or better fidelity compared with the evaluated baselines. Ablation studies further investigate the effectiveness of the proposed reliability control and auxiliary feedback mechanisms.
Critical strengths
- The proposed approach is simple and easy to follow. Extrapolating velocities using first- and second-order temporal differences, followed by reliability control and calibration, appears to be a reasonable approach to reducing expensive network evaluations. The method also requires no additional training and preserves the original denoiser and sampling scheduler.
- The experiments cover multiple image and video generation backbones and demonstrate improvements over the considered baselines.
Critical weaknesses
- The idea of leveraging historical model outputs to extrapolate future values and avoid expensive network forward passes has already been explored in prior work, such as TaylorSeer and Spectrum. In particular, TaylorSeer employs Taylor-series-based extrapolation using finite differences of previously computed features, which is conceptually very similar to the proposed velocity predictor. The main distinction appears to be the prediction target: VeloForesight extrapolates the final velocity outputs rather than intermediate network features. Moreover, FastFlow has already explored direct velocity extrapolation using finite differences. Although the proposed structured reliability control introduces additional mechanisms for regulating the extrapolated updates, the paper does not sufficiently establish how these mechanisms constitute a substantial technical advancement over existing reliability estimation and correction mechanisms.
- The correction mechanisms in Sec. 3.3 appear to be heuristic and sensitive to the choice of hyperparameters.
- Despite comparing against VDE (CVPR 2026), the main experiments do not include comparisons with FastFlow (ICLR 2026), which appears particularly relevant given its use of finite-difference-based velocity extrapolation. While Appendix G provides a same-state diagnostic comparison using an equation-level adaptation of FastFlow, this is not equivalent to a comparison with the complete FastFlow. Given the substantial methodological overlap, a comparison against it would help establish the effectiveness of the proposed method.
- One of the main contributions of this work is the introduction of reliability control and auxiliary feedback mechanisms for correcting extrapolated velocities. However, the experiments do not include comparisons with the existing methods discussed in the "Prediction reliability and correction" paragraph of the Related Work section.
- Several expressions could be clarified to improve readability. For example:
- L91: "We introduce a multi-anchor velocity predictor whose complete scheduler-facing change proposal is controlled before the sampler update..." The term "scheduler-facing change proposal" is somewhat artificial and could be replaced with a more direct description of the bounded velocity update supplied to the scheduler.
- L102: The term "local comparisons" is ambiguous. It would be helpful to clarify whether this refers to locally reproduced baseline implementations, matched evaluation environments, or both.
- L235: "At an exact step a, we reconstruct ... from the old anchor history, before inserting the new velocity." The phrase "inserting the new velocity" could be made more explicit. Presumably, this refers to appending the newly evaluated velocity to the exact-anchor history, rather than modifying the sampling state.
Questions for authors
- Could the authors clarify the fundamental technical differences between the proposed velocity extrapolation method and prior approaches such as TaylorSeer, Spectrum, and FastFlow? What is the main methodological novelty of the proposed predictor beyond applying separate gains, horizon-dependent attenuation, and norm bounds?
- Could the authors explain why comparisons with FastFlow are not included in the main experiments? Given the similarity between the two approaches, a comparison under matched evaluation budgets and computational settings would be particularly informative.
- Could the authors provide additional empirical comparisons with the prediction reliability and correction methods discussed in the Related Work section, such as Confidence-Gated Taylor, GP-Refiner, and RACER? If direct comparisons are impractical due to differences in prediction targets or computational overhead, could the authors explain these limitations and clarify the advantages of the proposed mechanisms over these approaches?
- In Table 3, adding state feedback increases the relative velocity prediction error from 0.1181 to 0.1262 and slightly decreases PSNR from 24.41 to 24.39, while improving LPIPS from 0.1788 to 0.1603. Could the authors elaborate on why state feedback improves perceptual fidelity despite worsening the measured velocity prediction accuracy? Additionally, could the authors provide separate ablations for clean-state feedback and corrected gain adaptation to clarify their respective contributions?