- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
This paper proposes an extension of step-distillation techniques based on the TwinFlow framework. TwinFlow constructs a fake-score estimator by extending the timestep domain to negative values, using the sign of the timestep to distinguish the real and fake trajectory estimation tasks. In contrast, APEX retains the original timestep domain and uses a shifted text embedding as the conditioning signal to distinguish the fake-trajectory task.
Critical strengths
-
Clear presentation and implementation. The method builds upon prior works, particularly TwinFlow and RCGM, making the overall methodology and implementation relatively easy to follow.
-
Promising empirical results. APEX achieves competitive or improved FID, CLIP, and GenEval scores over prior methods in Tables 1 and 2, demonstrating its potential for efficient text-to-image generation.
Critical weaknesses
-
Unclear motivation and insufficient justification for the proposed conditioning mechanism. The main contribution appears to be replacing TwinFlow's timestep-based separation with condition-space separation. However, the paper does not sufficiently explain the limitations of TwinFlow that motivate this change or establish why the proposed alternative is preferable. More importantly, the rationale for the proposed conditioning mechanism is unclear. In TwinFlow, extending the timestep domain to negative values explicitly introduces a new input region to distinguish fake-trajectory estimation from real-trajectory estimation. In contrast, shifting the text embedding does not inherently guarantee that the model will learn a distinct fake-score estimator. Since the text embedding space is implicitly learned, the shifted embeddings may remain within the same semantic representation space as the original embeddings, and the paper does not explain how the shift reliably distinguishes the two estimation tasks. Consequently, the motivation and methodological justification for condition shifting remain insufficiently established.
-
The evaluation lacks fair and comprehensive comparisons.
- Latency and throughput comparisons are unclear. For methods using the same backbone, such as Qwen-Image, I would expect inference latency and throughput to be comparable under consistent evaluation settings. However, the reported numbers for APEX differ from those of Qwen-Image-Lightning, RCGM, and TwinFlow. Similar concerns apply to methods based on SANA. The paper should clarify whether these differences arise from different hardware, inference configurations, resolutions, or implementation optimizations, and provide a more controlled comparison.
- The evaluation protocol and presentation of results could be improved. DPG-Bench is also an important benchmark for text-to-image generation and should be reported alongside other evaluation metrics rather than treated as a complementary evaluation (e.g. SANA paper and Qwen-Image report). Table 3 could be integrated with Table 1 to facilitate direct comparison. The main comparisons should focus on few-step generation methods, while comparisons with full-model systems such as GPT Image 1 [High] could be included as a reference for the performance gap to more capable systems.
- The most informative comparison is insufficiently presented. Table 4 could provide particularly valuable evidence by comparing different step-distillation methods trained on the same dataset under controlled conditions. However, the paper reports only the NFE = 2 setting, despite being titled One-Step Generation. Including NFE = 1 results and providing a more comprehensive comparison with prior methods would make the table substantially more informative and better support the paper's central claim.
- The ablation study on alternative condition constructions lacks sufficient context. The ablation study in Table 5 investigates alternative condition constructions, but the rationale behind the conditioning framework itself is not adequately established earlier in the paper. Without a clear explanation of why condition shifting should distinguish real and fake trajectory estimation, it is difficult to interpret these ablations or understand the principles underlying the design choices.
Questions for authors
-
What specific limitations of TwinFlow motivate replacing timestep-based separation with condition-space separation?
-
How does shifting the text embedding enable the model to distinguish real-trajectory estimation from fake-trajectory estimation?
Dear Reviewer,
Thank you for your time and effort in reviewing the submissions. We kindly ask you to check the authors' responses and engage in further discussion if necessary. Please let us know promptly whether your concerns have been addressed or if any issues remain unresolved.
Your timely feedback would be greatly appreciated. Thank you for your cooperation!