- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
This paper presents ccSplat, a compaction and compression framework for feedforward 3DGS. It selects Gaussian primitives under a fixed budget using learned importance prediction, coverage-aware selection, and scale refinement. The retained primitives preserve their original pixel correspondence, which is then used to predict and encode Gaussian attributes from the input image and neighboring grid locations. The method is evaluated on SHARP and AnySplat for both compaction and compression.
Critical strengths
1.The method makes good use of the pixel-aligned structure of feedforward 3DGS. The retained pixel addresses are shared across attribute organization, context prediction, and position recovery. Figure 8 verifies the coding benefit of preserving the native pixel layout under identical reconstruction.
2.The experiments cover both single-view and multi-view backbones, including codec comparisons on the same compact input, RD curves, and component ablations. On SHARP, ccSplat reduces the Gaussian count by approximately 4x and the storage by 27x, with only a 0.37 dB drop in source-view PSNR.
Critical weaknesses
1.The rate-distortion benefit of the proposed selection strategy within the full compaction-compression pipeline has not been sufficiently validated. The compaction stage selects primitives based on rendering error and a Gaussian-count budget, without considering the coding cost of the retained primitives. Table 1 compares different selectors only by image quality at a budget of approximately 300K Gaussians, whereas Table 2 and Figure 4 compare codecs using only the output selected by ccSplat. Figure 8 demonstrates the coding benefit of the native pixel layout for a given Gaussian set, but does not compare different selected sets encoded with the same codec. The current results therefore support the value of preserving pixel correspondence for coding, but do not establish whether the proposed selection strategy gives a better end-to-end rate-distortion trade-off than other selectors. This makes it difficult to identify the source of the final performance gains.
2.The current experiments do not sufficiently isolate the contribution of the proposed compaction strategy. In the SHARP experiment, RAP is applied using its released importance-prediction weights with a DC-only attribute adapter, whereas ccSplat trains its importance head for the SHARP backbone. Although a selector-specific scale-refinement head is trained for RAP, its importance predictor is not retrained under the same setting. In the AnySplat experiment, ccSplat’s per-view selection before fusion is compared with the original voxel-fusion output, so both the processing pipeline and the Gaussian count differ. These results demonstrate the performance of the complete systems, but a selector comparison with matched training, input, and budget settings is still missing.
Questions for authors
1.Could the authors apply the same codec to the outputs of different compaction methods under the same backbone and Gaussian budget? For example, the ccSplat codec could be used to encode the outputs of ccSplat and RAP with refinement, with full rd curves reported for both.
2.Could the authors report per-scene storage and image-quality results? This would be particularly helpful for AnySplat, where ccSplat and LGSCV differ by only 0.06 MB and 0.08 dB in PSNR at the representative operating point.
3.Could the authors provide a compaction comparison with matched training adaptation? For example, the RAP importance predictor could be retrained or fine-tuned using the same training data and SHARP outputs as ccSplat. Each selector could then use its own scale-refinement head and be evaluated under the same budget.
2 comments
Response (2/2): Results by Scene
Q2: Size and image quality for each scene
Response: Thank you for suggesting results for each scene. We have added the complete bitstream size and image quality results for each scene to the appendix, as the full tables are lengthy. We would be grateful if you could refer to the tables cited below for the detailed results. Table 13 compares ccSplat and LGSCV on the same AnySplat test views at their respective representative operating points (Appendix E.5, p. 24, lines 1284 to 1285).
Across the five AnySplat scenes in Table 13, ccSplat has slightly higher PSNR than LGSCV in every scene, while the tradeoff in size varies by scene. For example, the sizes for bonsai are 4.849 and 5.025 MB, respectively. For garden, they are 5.907 and 5.494 MB, with PSNR values of 19.490 and 19.459 dB.
Tables 16 and 17 in Appendix E.7 report representative operating points for all codecs on each AnySplat and SHARP scene, including size, PSNR, SSIM, and LPIPS (p. 26, line 1355, and p. 27, line 1404, respectively).
Response (1/2): Selector RD and RAP Adaptation
W1/Q1: Different selectors encoded with the same codec
Response: Thank you for suggesting a comparison of different selectors using the same codec. In this comparison with a common codec, ccSplat provides higher rendering quality at similar bitstream sizes. For example, at one tested operating point, ccSplat has a size of 2.096 MB and a source view PSNR of 27.129 dB against ground truth. Fine tuned RAP with its corresponding scale refinement uses 2.196 MB at 26.695 dB. Their novel view PSNR values relative to dense SHARP are 37.014 and 32.049 dB, respectively.
We have added RD curves for six selectors: Opacity, opacity-scale proxy, Vox, fine tuned RAP, fine tuned RAP with its corresponding scale refinement, and ccSplat. They use SHARP predictions with a budget of approximately 300K Gaussians and are encoded with the same codec. We report both source view quality against real ground truth and novel view fidelity relative to dense SHARP.
Even when selectors retain similar numbers of Gaussians, their compact point clouds differ in rendering quality. These differences remain after coding with the same codec, leading to similar bitstream sizes but substantially different quality. The RD comparison with a common codec measures the actual size and quality after coding these retained sets, providing empirical evidence for the tradeoff of the full pipeline.
The main curves are in Fig. 5(b) (p. 7, line 377), with the discussion in Section 4.2 (lines 358 to 365). Fig. 16 in the appendix provides the complete quality metrics (p. 23, lines 1212 to 1213). Fig. 17 reports the original five common coding configurations for all selectors (lines 1239 to 1240).
W2/Q3: RAP adaptation and corresponding scale refinement
Response: Thank you for suggesting a comparison after adapting RAP. We have fine tuned RAP's importance predictor and trained a corresponding scale refinement head for each of the public and fine tuned RAP versions. With common test inputs, cameras, and a budget of approximately 300K Gaussians, public RAP has a source view PSNR of 24.376 dB, which increases to 25.261 dB after fine tuning. Their respective scale refinement heads increase these values to 25.944 and 26.716 dB, while ccSplat has a PSNR of 27.332 dB. Table Q1 reports all four quality metrics.
Fine tuning uses outputs from frozen SHARP and data from DL3DV, Getty, OpenScene, and Tanks and Temples. The training data are exactly the same as those used to adapt ccSplat. Mip-NeRF 360 is used only for testing. The importance predictor is updated for 15,000 steps, and each scale refinement head is updated for 10,000 steps, so that both the public and fine tuned importance predictors have scale refinement heads trained for their respective selections.
Keeping both public and fine tuned results makes the gains from adaptation and their corresponding scale refinement directly comparable.
The AnySplat comparison also reports both the original voxel fusion output and the representation obtained by compacting the grids from individual views. The former contains an average of 1,109,451 Gaussians, while the latter retains at most 300K. This comparison includes changes in both the pipeline and the Gaussian count and evaluates the complete systems. Table 3 additionally reports EcoSplat, Off The Grid, and AdaptiveSplat at similar Gaussian budgets, providing a further system comparison at approximately 300K Gaussians (p. 8, line 426).
The RAP adaptation procedure is in Appendix E.1 (p. 20, lines 1063 to 1069). Quality results are also reported in Table 1 (p. 6, lines 296 to 297) and Table 10 in the appendix (p. 21, line 1080). The complete source view and novel view crop comparisons are in Fig. 14 (p. 21, lines 1114 to 1116) and Fig. 15 (p. 22, lines 1156 to 1158), respectively.
Table Q1. Source view comparison of selectors based on SHARP. Quality is measured against the input image; actual Gaussian counts are listed.