Summary
The paper presents a framework (PCIG) tackling the issue of text-to-image (T2I) generation inconsistencies. It highlights important challenges such as entity mismatches and handling complex scenes, and it proposes a pipeline that integrates large language models (LLMs), knowledge graphs and location prediction to improve overall generation quality.
Strengths
1. The authors have summarized some of the key challenges in text-driven image generation, particularly around maintaining consistency in entities (Figure 1) and managing complex scene generation.
2. The proposed pipeline is relatively complete and utilizes LLM to refine entities and layouts, which helps improve text-consistent image generation.
Weaknesses
I have some concerns about different aspects of the paper that I feel should be addressed:
1. **Framework Innovation**: Actually, what concerns me the most is that the proposed approach feels more like a combination of several established LLM strategies, such as “object extraction,” “relation extraction,” and “object localization,” rather than introducing novel research contributions. This makes it come across more as an industrial solution, which might not fit the innovation threshold for a conference like ICLR.
2. **Quantitative Results**: I find it difficult to be fully convinced by the quantitative results. The use of the existing *AnyText* [1] module to mitigate textual hallucination and factual hallucination (improved *TH Acc* and *FH acc*) seems to remove much of the novelty from your approach, as seen in Tables 1, 3.
3. **Misleading References**:
In my view, the following statement is not rigorous (L50-L51). The mentioned works (*DDPM* [2] and *DDIM* [3]) weren't designed to impose extra conditions like text (an attention-based denoiser is indeed proposed in *DDPM*); rather, *LDM* [4] is what paved the way for capturing these text-driven image generation. This kind of statement may mislead the readers.
> *Attention-based approaches Ho et al. (2020); Song et al. (2020) have been proposed to better capture relationships between words and visual features,*
4. **Presentation Issues**: The citation style isn't consistent—using `\citep` instead of `\cite`. Additionally, there are quite a few grammatical errors and informal math expressions, making parts of the paper hard to follow.
5. **Inconsistent Terminology**: There’s a discrepancy with how LLM is referenced—in the abstract, it’s “*large language **module***,” but later, it’s called a “*large language **model***.” Consistency here would help avoid confusion and “*large language model*” is more formal.
**Reference**
[1] *Tuo, et al. "Anytext: Multilingual visual text generation and editing." arXiv (2023).*
[2] *Ho, et al. "Denoising diffusion probabilistic models." NeurIPS (2020)*.
[3] *Song, et al. "Denoising Diffusion Implicit Models." ICLR (2021)*.
[4] *Rombach, et al. "High-resolution image synthesis with latent diffusion models." CVPR (2022)*
Questions
1. What exactly is "*Stable Diffusion v1.6*"? From what I know, *Stable Diffusion v1.5* [5] is the most widely used in the 1.x series. If v1.6 exists, could you provide its source or any documentation?
2. In Figure 3, the **second row's last column** shows results under the prompt "*A street sign with 'Main Street' written on it*." The output looks suspiciously like an image from the Hugging Face Diffusers documentation [6]. Can you clarify the validity of this comparison?
3. What about the time efficiency of the proposed method? Since this framework involves multiple stages (like calls to OpenAI API and online search engines), I assume the time cost could be higher. Could you provide a quantitative comparison with other methods?
4. In Table 1, you present quantitative results comparing layout-based methods and LLM-based methods, but the qualitative comparison doesn’t include these approaches. Why are these missing from the visual results?
5. Also in Table 1, there’s an odd repetition of numbers. For example, why do the results for *VPGen*, *Ranni*, and *LMD* seem identical? This repetition needs clarification.
**Reference**
[5] *https://huggingface.co/stable-diffusion-v1-5/stable-diffusion-v1-5*.
[6] *https://huggingface.co/docs/diffusers/en/using-diffusers/inpaint*.