- Rating
- 2
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper addresses the problem that, in low-bit post-training quantization of flow-matching video models, quantization errors change the velocity direction and accumulate along the denoising trajectory, causing generation to collapse. It proposes to temporarily raise the activation bit-width at timesteps with large direction changes (CAQ), and to keep a few key layers in FP16 according to their directional sensitivity (DBP). On Pyramid Flow, it shows better generation quality than MinMax, SmoothQuant, QuaRot, Q-DiT and ViDiT-Q from W6A6 to W3A6. However, it does not verify that the errors at the selected locations actually have the largest impact on the final result, it lacks comparisons with SVDQuant/DeltaQuant and real-deployment efficiency results, and the evaluation is small, with each configuration run only once.
Critical strengths
1、The code is anonymously open-sourced.
2、 The motivation deserves recognition, and it is supported by experiments.
Critical weaknesses
1、The paper is motivated by “errors propagating and accumulating along the denoising trajectory”, but both CAQ and DBP allocate precision only according to local direction changes, without verifying whether the errors at these locations actually have the largest impact on the final video.
2、Several descriptions in the paper need further clarification:
(1) The profiling set used by DBP for layer selection is not specified in terms of size, source and seeds, which makes it hard to rule out systematic bias.
(2) How exactly is the CAQ threshold determined? The paper describes using 10 prompts, but Tables also report results on these same 10 prompts. Is this evaluation reasonable?
(3) The main text states that quantization scales are computed on the fly without offline calibration, whereas Appendix A.1 describes a protocol based on a calibration set. Please clarify the details.
3、The paper claims SOTA under extreme settings such as W4A4, yet excludes SVDQuant and DeltaQuant, which also target 4-bit diffusion/video quantization, on the grounds that they are “a different type of method”. Given that TrajeQ itself also keeps some layers in FP16, this reason for exclusion does not hold. Comparisons should be added under the same bit-width or the same memory/compute budget.
Questions for authors
pls see weeknesses.