- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
This paper presents ReleaseEdit, a training-free framework for multi-turn image editing. Its main idea is to distinguish regions that may change from content that should be preserved, and to separate proposal generation from final acceptance. Different strategies are used for subject editing, object addition, and background replacement. The paper reports results on multi-turn editing sequences, but many qualitative examples are too blurry to support detailed visual inspection.
Critical strengths
- Multi-turn image editing is an important problem.
- The proposal–acceptance distinction is intuitive and potentially useful.
Critical weaknesses
- The technical novelty appears limited. The central idea is to modify target regions while preserving non-target regions. However, this method does not fully address the fundamental difficulty of multi-turn editing. If the same region is edited repeatedly, errors within that region can still accumulate and eventually collapse.
- The final image is obtained through mask-based compositing. This may introduce seams or inconsistent illumination near mask boundaries.
Minor:
- Figure 1 shows only five editing turns. Longer sequences would better demonstrate the performance.
Questions for authors
- How does ReleaseEdit compare with strong commercial multi-turn editors such as Nano Banana under the same instruction sequences?
- The method contains several task-dependent components and hyperparameters, but the paper does not provide sufficiently systematic robustness analysis. How sensitive is the method to the choices of hyperparameters?
2 comments
Thank you for your response to my comments.
For technical novelty, the rebuttal largely restates the method as presented in the paper, so my concern is not addressed. I remain unconvinced that the proposed design is a sufficiently substantial technical contribution.
For comparison with Nano Banana, the examples in the rebuttal show cases where Nano Banana fails to follow the editing instruction and the proposed method produces a more accurate edit. However, the proposed method builds on the open-source FLUX and Qwen backbones. I therefore believe its overall editing accuracy is likely below that of Nano Banana, and a few selected failure cases do not change this. For a paper focused on multi-turn image editing, the more relevant question is whether the method better preserves image quality across successive edits. A convincing demonstration would be examples like Figure 6, where FLUX Kontext shows quality collapse after multiple editing turns. The authors would need to show that Nano Banana degrades in the similar way while the proposed method does not.
Given these remaining concerns, I will keep my original score.
Response to Reviewer 8EDA: Additional Evaluations and Method Clarifications
Thank you for your valuable suggestions and questions. We have carefully considered your feedback and provide our responses to each point below.
Q1. Comparison with Nano Banana
We have added a ten-turn comparison with Nano Banana, FLUX.2-klein-4B, and FLUX.1 Kontext [dev] in Figure 6, together with enlarged regional comparisons in Figure 7. All methods start from the same image, follow the same editing instruction sequence, and recursively edit their own outputs.
In this sequence, ReleaseEdit maintains stronger visual consistency than the two FLUX baselines, with less texture degradation and subject drift. At the fourth-turn background replacement, ReleaseEdit produces the requested pale-grey background while retaining the previously added yellow ball. Nano Banana leaves the background largely white and changes the ball into a tennis ball. The enlarged views in Figure 7 make these differences directly inspectable. We discuss the comparison in Section 4.4.
Q2. Hyperparameter sensitivity
We have added the default configurations for all three editing types in Table 3 (Appendix B, p. 14), qualitative sensitivity comparisons in Figure 5 (p. 9), and numerical diagnostics in Table 4 (Appendix E, p. 17).
The six-turn and ten-turn evaluations in Table 1 use fixed task-specific defaults shared across examples, without individual tuning. Common settings are FLUX.1-dev, 512×512 resolution, seed 42, and one candidate per instruction.
Figure 5 includes nearby settings for subject guidance g∈{3.0,3.5,4.0}, addition gain αadd∈{0.65,0.75,0.85,0.95}, and background width ω∈{0.015,0.020,0.025}. Each sweep fixes the input, prompts, observations, seed, sampling schedule, and acceptance rule.
The results expose the completion–preservation trade-off: increasing addition gain from 0.75 to 0.85 barely changes Edit scores while reducing local integrity, whereas nearby background widths produce similar preservation scores. Section 4.3 discusses these results. Diagnostic definitions and within-branch normalization are provided in Appendix E.
M1. Longer sequences and clearer qualitative examples
We have added quantitative evaluation on 400 ten-turn editing sequences in Table 1, a complete ten-turn comparison in Figure 6, and enlarged qualitative details in Figure 7.
Table 1. Final-turn results on 400 ten-turn editing sequences (p. 8). Each method recursively edits its own preceding output. All four metrics are higher-is-better.
ReleaseEdit leads all five baselines across the four Turn-10 metrics. The additional figures expose the complete editing trajectory and local preservation details, addressing the concern about qualitative clarity.
W1. Technical novelty and error accumulation
ReleaseEdit separates the support used for proposal generation from the permission for acceptance. Subject proposals use broader semantic context with localized acceptance, while addition and background replacement use task-specific proposal controls and direct acceptance (Sections 3.4–3.6; Table 2).
For repeated editing, earlier requirements remain active unless superseded by the current instruction. This design reduces unintended changes while allowing new edits. The 400 ten-turn sequences in Table 1, together with Figures 6–7, provide evidence of sustained editability and reduced drift over the evaluated sequences.
W2. Mask compositing, seams, and illumination consistency
Acceptance is task-dependent. Addition and background replacement directly accept the generated proposal without a final pixel-space mask composite (Sections 3.5–3.6). Background masks control source-feature transport inside the transformer, allowing boundaries and surrounding appearance to form during generation.
Subject editing instead applies a continuous, scale-normalized release projection after context-aware proposal generation (Sections 3.3–3.4). Figure 7 provides unretouched enlarged views across all three edit types for inspecting boundaries, contact regions, and surrounding appearance.