Official Reply by Paper Authors
We sincerely express our gratitude for the reviewer to allow us compare PaGoDA with SD more deeply. We believe the review is highly helpful, and would like to revise the paper based on our discussion.
**Q1-1. While training a new VAE requires sequential training, PaGoDA also necessitates an additional data generation process.**
**Ans.**
**[Minimal Overhead]** It takes about one day with 8xH100 GPUs to converge in T2I at base resolution if training data pairs are synthesized online. The data collection overhead is minimal compared to the overall DM pretraining cost. For higher-resolution training, the data pairs collected at base resolution are reused, significantly reducing the need for additional DDIM inversion and compute resources.
**Q1-2. For conditional generation, the model p(w∣x,c) must also be trained.**
**Ans.**
**[Use Released Checkpoint]** We recognize that our approach involves higher initial costs due to the need to train the classifier. However, once the classifier is publicly available, the training pipeline will be as equivalent of training a smaller VAE.
**Q1-3. I still doubt whether PaGoDA truly offers a more convenient training pipeline compared to training a smaller VAE.**
**Ans.**
In terms of the number of training stages, PaGoDA is indifferent from SD. However, we would like to further discuss the discrepancy between SD and PaGoDA when we desire to increase the sample resolution, e.g., from 512x512 to 1024x1024.
**[SD Needs Entire Retraining]** In Stable Diffusion, the entire pipeline needs to be retrained from scratch, following these steps:
- Train VAE at 1024x1024 *from scratch*
- Train latent DM *from scratch*
- (Optional) Distill latent DM into one-step generator
- (Optional) (Optional) Distill VAE into smaller VAE
**[PaGoDA Recycles Pretrained Network]** In contrast, PaGoDA could *reuse* 512x512 generator and only necessitates training a upsampling network from 512x512 to 1024x1024, making it significantly more cost-effective than SD, as follows:
- *Reuse* pixel DM at base-resolution
- *Reuse* PaGoDA at base-resolution
- *Reuse* PaGoDA at super-resolution up to 512x512
- Train PaGoDA for upsampling from 512x512 to 1024x1024
**Q2. Doesn't PaGoDA also experience reconstruction error for the input image in Figure C?**
**Ans.**
PaGoDA exhibits less accurate reconstruction than generation quality. This is because PaGoDA's reconstruction quality solely depends on reconstruction loss. Below, we provide details on this respect.
**[Different GANs for Different Purposes]** We kindly remind that the model objectives are different: VAE in SD is for data compression, while PaGoDA is to assist generation. Accordingly, VAE and PaGoDA applied GANs for two different purposes:
- GAN for reconstruction
- Real: a real image
- Fake: its corresponding reconstructed image
- GAN for generation
- Real: a real image
- Fake: a randomly generated image from a random noise
PaGoDA prioritizes generation quality over reconstruction quality, thus using (II) type of GAN. Therefore, PaGoDA's reconstruction relies solely on LPIPS reconstruction loss. In contrast, SD's VAE uses option (I), specifically tailored for better reconstruction quality.
**[Applying Option (I) in PaGoDA for Better Reconstruction]** We observed that the further use of (I) in PaGoDA on top of (II) improves reconstruction quality, and we will include a figure in our final revision to illustrate this improved reconstruction quality. It is important to note that a direct comparison with Figure C is not feasible for PaGoDA, as DDIM inversion relies on the text prompt, which is not provided in Figure C.
**(Side Remarks on Q2)**
We presume that the reviewer may have raised concerns about PaGoDA's upsampling capability due to the loss of high-frequency signal during downsampling of the encoder. This information leakage seems fundamentally blocking higher-dimensional generation at the first glance. Below, we further discuss that it is not necessarily true in PaGoDA.
**[PaGoDA: Lossless Compression]** Although our encoder may seem to perform lossy compression, it can actually achieve lossless compression in principle, i.e., perfect reconstruction. If the downsampled versions of two different images $x$ and $y$ remain distinguishable, DDIM inversion, as an injective function, will map $x$ and $y$ to distinctive vectors in the latent space. Therefore, the generator can map these distinctive latent vectors back to the original signals $x$ and $y$, respectively, given a sufficiently flexible generator and a well-designed loss function. However, this lossless compression is only achievable when two different data remain distinguishable after downsampling. Hence, the downsampling factor should be carefully selected to ensure that the downsampled images are distinguishable. At resolutions like 64x64 (or even 32x32), natural images remain sufficiently distinguishable.