- Rating
- 1
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper studies compression of streaming 4D Gaussian (4DGS) representations for free-viewpoint video under sparse-view capture. Building on the 4DGC codec, the authors first measure that motion grids constitute ~99% of P-frame payloads in their three-view reproduction, with consecutive decoded grids correlating at 0.92–0.95 and ~95–96% of integer residuals being zero (§3.2). They then propose GR4DGS, a lossless post-training recoding that transmits integer differences against the previously decoded grid (Δ_t = S_t − S_{t−1}, Eq. 2), achieving bit-exact recovery with 65–72% P-frame payload reduction, plus an optional causal context entropy coder (§4.2). A second variant, GR4DGS-E2E (§4.4), trains in the residual domain with a residual-rate objective (Eq. 5) and occupancy-aware initialization (Eq. 6), reaching 88–93% P-frame reduction with per-scene mean PSNR differences within 0.03 dB. Including the shared uncompressed keyframe, sequence payloads fall by 81–86%. Validation covers six Neural 3D Video scenes (300 frames each) at three/six/nine training views, with ablations on initialization strategies, occupancy pruning, and rate weights (Tables 1–3, 5, 9).
Critical strengths
-
Well-motivated, reproducible diagnostics. The empirical decomposition (motion grids ≈ 99% of P-frame payload; consecutive-grid correlation 0.92–0.95; 41.5% cell occupancy, Table 8) precisely identifies the dominant compression bottleneck, and the lossless variant is verified bit-exact on every decoded stream with transparent byte accounting (frequency tables, fp32 MLP, keyframe listed separately).
-
Clean and honest experimental practice. The ablation panel (Table 5: rate-only / plain temporal / occupancy-aware / GOP-10 initialization) cleanly isolates the contribution of residual-domain training, the drift failure modes are disclosed, and limitations (seeking, packet loss, single E2E runs) are stated rather than hidden.
Critical weaknesses
-
Missing rate–distortion evaluation; the central claim is not established on equal terms. All headline savings are reported against a single default operating point (λ_grid = 10⁻⁵). Table 9 shows that merely tuning the baseline rate weight makes 4DGC competitive or better: on cook spinach, 4DGC at λ_grid = 10⁻⁴ achieves 0.020 MiB/frame at 21.325 dB, versus GR4DGS-E2E's 0.084 MiB/frame at 21.387 dB — 4× fewer bits at essentially equal quality. The authors acknowledge the same phenomenon at six views but provide no R–D curves or BD-rate. It is therefore impossible to separate "our method compresses better" from "the baseline was simply not tuned."
-
Weak baseline and no comparison or citation of 2025 state-of-the-art methods. The comparison is confined to the 4DGC family and 2024-or-earlier methods (QUEEN, TeTriRF, 3DGStream, GC-4DGS). Directly competing 2025 works are neither compared nor cited. Examples include [1] "Compressing streamable free-viewpoint videos to 0.1 MB per frame" (AAAI 2025), [2] GIFStream (CVPR 2025), [3] Motion matters (NeurIPS 2025), [4] 4D Gaussian videos with motion layering (TOG 2025), and [5] EvolvingGS (SIGGRAPH Asia 2025). The paper never establishes its position relative to the current state of the art, and its absolute bitrate is not shown to be competitive under a unified accounting convention.
Questions for authors
-
It is recommended that the authors provide sequence-level R–D curves and BD-rate for 4DGC, GR4DGS, and GR4DGS-E2E across 3–4 rate weights, and reconcile Table 9, where tuned 4DGC (0.020 MiB/frame at 21.325 dB on cook spinach) uses 4× fewer bits than GR4DGS-E2E (0.084 MiB/frame at 21.387 dB) at nearly the same PSNR.
-
It is recommended that the authors compare against the recent works mentioned above under a unified accounting convention (MLP, keyframe, container overhead). If reproducing them is infeasible, it is recommended that they state the specific technical difference that keeps their method competitive.
-
It is recommended that the authors clarify how sparse-view capture specifically affects the temporal redundancy of motion grids, and why three-view training is the appropriate evaluation protocol rather than a general streaming setting.
-
It is recommended that the authors discuss keyframe compression, since the uncompressed keyframe is >40% of the E2E sequence payload (Table 2), and state how the claimed sequence-level savings would change.
Thank you for these questions.
Q1. How much of the gain survives tuning 4DGC?
A1. Tuning 4DGC closes most of the original gap. E2E still saves about one fifth at the middle weight. 4DGC penalizes the current grid. E2E penalizes its change from the decoder’s previous grid.
Table 10 and Fig. 8 (p. 25) report the three paired cook weights, all using one regenerated warm-up. At 3×10⁻⁵, losslessly recoding tuned 4DGC increased the cook sequence from 35.404 to 37.495 MiB. Training E2E gave 28.557 MiB, saving 19.34% at −0.00134 dB. On sear it saved 23.89% (31.204 to 23.748 MiB, +0.0315 dB). Totals count one keyframe and 299 updates.
The original 0.020 vs. 0.084 MiB/update used 10⁻⁴ for 4DGC and 10⁻⁵ for E2E (Tables 9 and 1, pp. 24 and 7). At a shared 10⁻⁴ we measured 0.0193 vs. 0.0195. E2E was 0.25% larger overall. Table 9 also reports 4DGC at 3×10⁻⁴. Cook PSNR BD-rates vs. 4DGC were −14.84% for E2E and −3.23% for lossless recoding (PCHIP), or −17.70% and −6.52% (linear). The PSNR overlap for E2E is 0.02216 dB. Each setting ran once. Lossless recoding saved 61.46% at the default cook weight but cost bytes at both higher weights.
Q2. Where does GR4DGS stand relative to the five recent codecs?
A2. On three-view cook, E2E used fewer bytes at higher PSNR than iFVC. GIFStream had the smallest stream and highest PSNR in Table 12 (p. 26). Lossless GR4DGS also recodes an existing 4DGC sequence with exact grid recovery.
All methods share the images, cameras and point cloud. Sizes cover all 300 frames and quality covers frames 1–299. We independently decoded one point per external codec, each trained on its own schedule. E2E used saved-model renders and separate grid checks. Native bytes exclude transport framing. We counted E2E’s keyframe, grids, tables, residual attributes and motion MLP, and all five GIFStream groups with metadata.
The remaining comparisons use published work (p. 26). 4DGV codes deformation offsets and reports 34.008 dB at 24.87 MB on cook with 17 training cameras. It cannot be ranked directly against our three-view runs. ComGS propagates motion from sparse keypoints. EvolvingGS deforms Gaussians and adds or removes points. 4DGV, ACM TOG 2025 · ComGS, NeurIPS 2025 · EvolvingGS
Q3. Why study compression with only three input cameras?
A3. A small rig lowers the cost of filming a moving scene from several directions. Its fitted motion field can still be expensive to stream. 4C4D recorded Dyn4Cam with four cameras at a total rig cost below USD 1,500. RF-DeRF discusses motion ambiguity with few views. We use three spaced cameras for depth estimation (one reference, two source views) and a held-out camera for evaluation. On cook we vary the training views on the same recording (§1, p. 1 and Appendix D, p. 19). 4C4D, CVPR 2026 · RF-DeRF, SIGGRAPH 2024
Reducing six views to three lowered default 4DGC’s held-out PSNR from 29.585 to 21.365 dB, yet mean update size stayed near 0.7 MiB (0.723 vs. 0.708, Table 9, p. 24). Motion grids account for about 99% of default three-view update bytes (§3.2, p. 3). Across 298 cook transitions, 94.75%, 95.52% and 95.80% of finest-grid differences were zero at 3, 6 and 9 views. Coding those differences saved 65.0%, 67.1% and 68.6% of update bytes with exact recovery (Table 4, p. 15 and Appendix G, p. 25). Redundancy persisted at all three view counts on cook. The other five scenes were tested only at three views. Over 130 six-view cook updates, default E2E used 0.0653 MiB/update at 29.627 dB vs. tuned 4DGC’s 0.0174 at 29.512 dB (p. 16).
Q4. Does the saving survive keyframe compression?
A4. Yes. Compressing the common keyframe subtracts the same bytes from both totals. Lossless xz (preset 6) reduced it from 17,099,168 to 13,911,640 bytes on cook. At the middle weight, 4DGC and E2E then used 32.364 and 25.518 MiB, increasing the saving from 19.34% to 21.16%. At 10⁻⁴ the totals were (19.037 vs. 19.093 MiB). At the default weight the saving rose from 82.46% to 83.58% (p. 25). Table 2’s 81.9% is from the original batch (p. 8).