- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
UniGVC uses one hierarchical latent codec and bitstream to support two generative decoders: a 50-step bidirectional DiT for buffered, quality-oriented reconstruction, and a single-step autoregressive DiT with windowed attention, KV caching, and a conditional tiny decoder for low-delay decoding. Both branches start from Wan2.1-1.3B; codec–LoRA joint training precedes BI-supervised AR distillation and pixel-space refinement. Experiments use the first 96 frames of 1080p HEVC-B, UVG, and MCL-JCV sequences. AR reaches 36.85 decoding FPS on a B300, over 250× faster than the paper’s own BI configuration.
Critical strengths
S1. A useful single-bitstream, multi-mode objective. Separating the transmitted representation from the receiver’s quality–latency choice could support live viewing and higher-quality replay without duplicate bitstreams. The paper develops a coherent implementation of this objective.
S2. Compression-specific conditioning and substantive decoder engineering. Bitstream-derived conditions provide source-aligned temporal context without feeding generated outputs back into subsequent predictions, enabling parallel diffusion training. Table 2 also identifies the original VAE decoder as a bottleneck after one-step distillation and demonstrates useful quality recovery: with adversarial DMD and pixel fine-tuning already enabled, codec conditioning reduces the BD-LPIPS gap from +0.058 to +0.001. These are meaningful results, even though their independent contributions require stronger validation.
Critical weaknesses
W1. The main AR evaluation does not validate causal online streaming.
Appendix D.1 generates captions from complete 96-frame videos, including future motion and events. Causal attention does not remove this non-causal side information. Although Table 9 provides a fixed-prompt ablation on HEVC-B, the main AR comparisons across all three benchmarks are not reproduced using fixed prompts or captions restricted to currently available frames. The reported quality therefore does not establish performance in the intended online setting.
W2. Decoder throughput does not establish end-to-end real-time performance, and deployment costs are incompletely reported.
The 36.85 FPS result measures decoding on a B300, while 1080p encoding requires 86 ms/frame. The reported >250× speedup is relative to the paper’s own 50-step BI configuration. End-to-end latency, including caption generation, text encoding and initial buffering, is not established. FLOPs/MACs, peak memory, KV-cache costs and specialized inference optimizations are insufficiently documented. Performance on other GPUs is also unvalidated, limiting the practical scope of the deployment claim.
W3. Perceptual superiority lacks convincing human and full-video validation against stronger generative baselines.
The user study includes only VTM-LD, DCVC-RT and GLC-Video, despite the paper acknowledging that small perceptual-metric gaps may not reflect human judgments. Fig. 10 also raises concerns about source-appearance and pose fidelity despite improved semantic plausibility. The supplied still images and temporal strips cannot adequately establish identity preservation, motion consistency or source fidelity. Full-video comparisons with and without captions, together with human comparisons against stronger generative baselines, are needed.
W4. The methodological contribution is insufficiently isolated from established designs and simpler alternatives.
GLVC already uses recurrent latent coding, GNVC-VD applies video-DiT refinement, and CausVid performs BI-to-causal distribution matching. Their integration does not by itself establish the benefit of UniGVC’s specific formulation. Missing controls include joint codec–BI/AR training versus a shared codec with independently adapted decoders, and quantitative contextual-autoregression comparisons against TF/SF. Table 2 provides useful decoder ablations, but does not isolate acceleration from UniGVC-specific changes versus inherited DCVC-family optimizations, including DC blocks and the DCVC-UF entropy-decoding strategy.
W5. Baseline coverage and cross-method evaluation consistency are insufficient.
GVC-RT and YODA are omitted. GVC1D and S2VC are included only through author-provided results rather than local reproduction under common settings. The GitHub repository was made open-source before the submission deadline. External results for unavailable methods such as GLVC and GNVC-VD are understandable, but their compatibility in preprocessing, frame selection, metric implementation and operating points is insufficiently documented. Consistent quality and runtime comparisons with reproducible generative baselines are needed to substantiate the claimed quality–latency advantage.
W6. Architectural gains are not disentangled from training scale and additional optimization.
The system uses one million 720p clips and 11K 1080p clips, followed by joint training, high-resolution adaptation, adversarial distillation and pixel-space refinement. Although Table 2 ablates selected training components, matched-data and matched-budget controls are missing for the central architectural comparisons. The results therefore establish the performance of the complete recipe, but not how much improvement comes from the proposed architecture rather than training data and additional optimization stages.
Questions for authors
Q1. Bitrate accounting.
Do the main bpp values and BD-rate calculations include the compressed sequence-caption bytes, or is this overhead reported separately in Appendix D?
Q2. Baseline availability.
What was the cutoff date for determining baseline availability, and were these checks updated before submission? For GVC1D and S2VC, did “unavailable” refer to code, checkpoints or both?
Q3. Supplementary videos.
Why were reconstructed videos not provided, given their importance for assessing perceptual quality, temporal consistency and source fidelity?
4 comments
Response to Reviewer oVJ2 (Part 2/4)
W3. Human preference against additional baselines.
We have conducted additional full-video comparisons, including comparisons with and without sequence-level captions, and extended the human preference study to include the raised and stronger generative baselines: GVC-RT [1], YODA [2], GVC1D [3] and S2VC [4]. The experimental protocol follows the same settings as Figure 8. For each comparison, we collected at least 30 valid human votes. The results on the HEVC-B test set are summarized below:
| UniGVC Preferred (%) ↑ | GVC1D, 0.0058 bpp | GVC-RT, 0.0043 bpp | YODA, 0.0061 bpp | S2VC, 0.0057 bpp |
|---|---|---|---|---|
| UniGVC-BI, 0.0038 bpp | 72.7% | 93.3% | 87.9% | 76.7% |
| UniGVC-AR, 0.0038 bpp | 67.7% | 96.9% | 84.8% | 63.3% |
| UniGVC-AR, 0.0038 bpp (w/o captions) | 64.5% | 93.3% | 83.3% | 60.0% |
The additional human evaluations show that UniGVC maintains a strong perceptual preference over these generative baselines, despite operating at lower bitrates.
W4. Clarification on methodological contribution.
We appreciate the reviewer for pointing out the connections to existing works. However, we would like to clarify that UniGVC is not simply an integration of GLVC, GNVC-VD, and CausVid. The central research question of UniGVC is fundamentally different: we investigate how to develop a single compressed representation that supports two distinct generative decoding modes, namely bidirectional DiT (BI-DiT) for quality-oriented reconstruction and autoregressive DiT (AR-DiT) for low-latency reconstruction.
To the best of our knowledge, this unified single-bitstream, multi-mode decoding objective has not been explored in the aforementioned works. Specifically:
-
Compared with GLVC, which primarily investigates latent-space video compression using the Wan2.1 VAE, UniGVC explores a unified codec jointly supporting BI-DiT and AR-DiT decoding. In addition, we propose HEM to improve coding efficiency under ultra-low-bitrate conditions.
-
Compared with GNVC-VD, which employs ControlNet to guide BI-DiT for generative video compression, UniGVC investigates the joint optimization of the codec with both BI-DiT and AR-DiT. In particular, we develop codec-conditioned autoregressive training and inference strategies, together with distillation-based acceleration for AR decoding.
-
Compared with CausVid, which transforms a bidirectional video generation model into an autoregressive model through DMD, UniGVC addresses the distinct problem of generative video compression. We further develop codec-conditioned adversarial DMD distillation and a Conditional Tiny Decoder to accelerate generative reconstruction under compressed codec conditions.
W4. Additional ablation and discussion.
To further address the concerns regarding the specific design choices, we have conducted additional quantitative ablations.
1. Comparison between independently optimized and unified codecs.
We compare the unified codec against two independently optimized codecs, where the codec is jointly trained with either BI-DiT or AR-DiT alone. The independent codecs achieve better rate–perception performance, quantifying the performance cost of sharing a single representation across two decoding modes.
| Method | LPIPS (%) ↓ | DISTS (%) ↓ |
|---|---|---|
| Independent-BI | -5.42 | -12.23 |
| UniGVC-BI | 0 | 0 |
| Method | LPIPS (%) ↓ | DISTS (%) ↓ |
|---|---|---|
| Independent-AR | -2.81 | -6.15 |
| UniGVC-AR | 0 | 0 |
2. Quantitative comparison of contextual autoregression strategies.
We further provide quantitative BD-rate comparisons between Diffusion Forcing (DF), Teacher Forcing (TF), and Self Forcing (SF), using DF as the anchor:
| Method | LPIPS (%) ↓ | DISTS (%) ↓ |
|---|---|---|
| SF | +44.57 | +61.24 |
| TF | +19.81 | +35.40 |
| DF (Ours) | 0 | 0 |
3. Clarification on UniGVC-AR's decoder acceleration.
Regarding the comparison with DCVC-family optimizations, we would like to clarify that our decoder acceleration primarily targets the computational bottlenecks of the DiT and VAE reconstruction pipeline, rather than the entropy coding process of the codec.
Specifically, DC blocks and the DCVC-UF entropy-decoding strategy optimize different components of the coding pipeline and are therefore not directly comparable to our generative decoder acceleration. Table 2 has explicitly isolated the codec decoding cost and focuses on our acceleration and reconstruction improvement of the DiT and VAE components.
Response to Reviewer oVJ2 (Part 3/4)
W5, Q2. Additional baseline under consistent evaluation.
We thank the reviewer for the suggestion. we have extended the baseline evaluation to include GVC-RT [1] and YODA [2]. Furthermore, we have used the official implementations to reproduce GVC1D [3] and S2VC [4] under our evaluation settings, rather than relying solely on author-provided results.
The updated comparisons are reflected in Figures 6 and 7 of the revised manuscript. The results show that UniGVC maintains the best overall rate–distortion–perception performance among the evaluated methods, while achieving temporal characteristics closer to the ground-truth videos.
Regarding runtime comparisons, we would like to clarify that the primary objective of UniGVC is to provide unified bidirectional and autoregressive decoding from a single bitstream, rather than simply accelerating an individual decoding architecture. Since the aforementioned methods do not provide the same bidirectional decoding capability, a direct comparison of their decoding speeds would not represent equivalent functionality. We therefore focus our runtime evaluation on characterizing the quality–latency operating points supported by UniGVC, rather than claiming universal decoding-speed superiority over all baselines.
W6. Clarification on architectural gains, training scale and additional optimization.
We would like to clarify that the training data and optimization procedures used in UniGVC follow established practices in recent generative video compression and high-resolution video generation works. They are introduced to address specific technical requirements of our framework, rather than to provide an unfair advantage over prior methods.
Specifically:
-
Video codec training data: Following GLVC [5], we use 1 million 720p video clips from Koala36M for training. Importantly, the codec is trained using videos at resolutions up to 480p, following the established training scale for learning latent-space codecs under the Wan2.1 VAE.
-
1080p DiT adaptation: UltraVideo [6] identifies the limitation of directly applying the pretrained Wan2.1 DiT to 1080p video inference. Accordingly, our high-resolution DiT adaptation follows the 1080p training data and adaptation strategy established in UltraVideo.
-
Joint training is essential to establish a shared codec that supports both BI-DiT and AR-DiT decoding.
-
Adversarial distillation and pixel-space refinement: These stages are introduced to address the reconstruction-quality bottlenecks of one-step generative decoding. Their contributions have been separately investigated in Table 2.
Therefore, these training stages are closely tied to the technical requirements of UniGVC, and their respective contributions are examined through component-level ablations.
Furthermore, to more directly validate the architectural contribution of the proposed HEM entropy model in Figure 2, we conduct an additional experiment on HEVC-C. Specifically, we independently train the codec with BI-DiT, replacing only the proposed HEM with a standard Factorized Hyperprior.
| Entropy Model | LPIPS (%) ↓ | DISTS (%) ↓ |
|---|---|---|
| Factorized Hyperprior | +36.35 | +52.68 |
| HEM (Ours) | 0 | 0 |
Q1. Bitrate accounting.
We thank the reviewer for requesting this clarification. We confirm that the bpp values and BD-rate calculations reported in the main paper include the compressed sequence-caption bytes.
Q2. Baseline availability.
In the revised evaluation, we have further checked baseline availability (the cutoff date is 2026/11/10) and used the official implementations to reproduce GVC-RT, GVC1D, YODA, and S2VC under our evaluation settings. Please refer to our response to W5 and the updated results in Figures 6 and 7.
Q3. Supplementary videos.
We apologize that supplementary videos were not included in the original submission. Our code and data release are currently undergoing internal review. Meanwhile, as described in our response to W3, we have extended the full-video human preference study to include additional generative baselines and comparisons, providing further subjective evidence of the proposed method's performance.
We commit to releasing the demonstration videos, source code, and model checkpoints upon paper acceptance, subject to the completion of the internal release process.
Response to Reviewer oVJ2 (Part 4/4)
References
[1] Dang et al., 2026, "GVC-RT: Towards Real-Time Generative Video Compression at Ultra-Low Bitrates".
[2] Li et al., 2026, "YODA: Yet Another One-step Diffusion-based Video Compressor".
[3] Zheng at al., 2026, "Generative Video Compression with One-Dimensional Latent Representation".
[4] Xue et al., 2026, "Single-step Diffusion-based Video Coding with Semantic-Temporal Guidance".
[5] Guo et al., 2025, "Generative Latent Video Compression".
[6] Xue et al., 2025, "UltraVideo: High-Quality UHD Video Dataset with Comprehensive Captions".
Response to Reviewer oVJ2 (Part 1/4)
We sincerely thank Reviewer oVJ2 for the thorough evaluation and suggestion on UniGVC, and for recognizing its core contributions on supporting multi-mode decoding with a single bitstream, compression-specific autoregressive conditioning and substantive decoder optimization. Our point-by-point responses are provided below.
W1, W2. Clarification on live-streaming application and decoder throughput.
We thank the reviewer for raising these concerns. We would like to first emphasize that UniGVC-AR claims real-time decoding capability at the receiver side, rather than end-to-end real-time encoding and decoding on a single device. We believe it is important to distinguish these two concepts when evaluating practical video coding systems.
In fact, practical video coding and live-streaming systems commonly have two characteristics:
Under this common streaming architecture, UniGVC can support practical live-streaming applications:
After the system reaches a steady state, both the encoding and decoding sides can operate in real time, given sufficient parallel computational resources at the encoder and a reserved fixed latency.
We acknowledge that our current encoder implementation requires approximately 86 ms per frame at 1080p (11.6 FPS) on a single GPU. However, this does not contradict our receiver-side real-time decoding claim, as the intended deployment architecture allows parallel computational resources at the encoder and a fixed delivery latency between the two sides.
W2. Deployment cost.
We provide additional measurements of the computational and memory requirements of UniGVC at 1080p resolution, including peak GPU memory, MACs per pixel, and the memory required for the autoregressive KV cache.
We clarify that we do not employ additional specialized inference optimizations beyond the proposed model design and decoding procedure. Furthermore, our current experimental environment does not provide other GPU models for cross-device evaluation. We will explicitly state this hardware limitation and report the above computational costs to better characterize the deployment requirements.
For sequence-level text conditioning, the additional text-related operations can be completed within the reserved fixed latency between encoding and decoding. Using HEVC-B with a GOP size of 96 as an example, we provide a detailed breakdown of the additional latency introduced by textual side information:
The additional latency introduced by textual processing is approximately 9.8 seconds, primarily due to video caption generation (6.5 seconds). This overhead can be accommodated within the minute-level fixed delivery latency commonly available in live-streaming applications.
We will add a dedicated discussion in the revised final manuscript. In particular, we will explicitly distinguish receiver-side real-time decoding from end-to-end real-time processing and clarify that extremely low-latency applications, such as video conferencing, are beyond the current scope of this work.