- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper presents CrossPair, a generalist image editing framework designed to transfer visual transformations from a single before–after exemplar pair to a content-distinct query image. The central objective is to infer the transformation demonstrated by the reference pair and apply it to a new image while preserving unrelated query content. Built upon Qwen-Image-Edit, CrossPair introduces role-ordered exemplar conditioning through the pretrained editor's native VLM and VAE pathways. The VLM pathway provides semantic interpretation of the demonstrated operation, while the VAE pathway preserves fine-grained visual appearance and structural information. The authors further introduce a training-only DINOv3 relation alignment objective. This objective aggregates patchwise feature displacements using change-aware spatial weights and aligns transformation directions between the reference and query scenes without requiring direct spatial correspondence across different scenes. Additionally, the paper constructs Transform-360K, consisting of 91,010 four-image training records spanning more than 8,000 fine-grained transformation relations across restoration, stylization, conditional representations, virtual try-on, and spatial editing. Experiments on seen and held-out transformations derived from Relation252K show improvements in target agreement, CLIP directional similarity, and GPT-5.5-based transformation faithfulness compared with the evaluated released systems.
Critical strengths
-
CrossPair makes effective use of the pretrained image editor’s existing VLM and VAE conditioning pathways. By feeding the reference-before, reference-after, and query images into both pathways in a fixed order, the method combines semantic understanding of the demonstrated transformation with the preservation of fine-grained visual details. Moreover, DINOv3-based relation alignment is used only during training, eliminating the need for an additional relation encoder or computational overhead at inference time.
-
The construction of Transform-360K is a meaningful contribution. It contains 91,010 training records covering more than 8,000 fine-grained transformation relations, with operation-specific pairing and quality filtering across diverse editing tasks.
Critical weaknesses
-
While CrossPair substantially improves transformation faithfulness, its query-content preservation remains considerably weaker than several baselines. For example, its in-domain content-preservation Rank-1 rate is only 15.3%, compared with 47.8% for LoRWeB (Table 2). This raises concerns about whether the model effectively transfers demonstrated transformations while preserving query-specific content.
-
Although the change-aware DINOv3 relation objective is presented as a central technical contribution, Table 3 shows only marginal improvements in CLIP-I (GT) (0.776 to 0.778) and LPIPS (0.402 to 0.400), while the more noticeable gain is in CLIP-Dir (0.350 to 0.369). Moreover, the method introduces a DINOv3 ViT-7B/16 encoder during training, requiring additional feature extraction and gradient computation. Without an analysis of the additional training cost, it is difficult to assess whether these improvements justify the computational overhead.
-
As described in the supplementary material, some prompts contain explicit editing descriptions in addition to image-role instructions. These descriptions may already specify the intended transformations, making it difficult to determine whether CrossPair learns transformations from visual exemplars or primarily follows textual instructions using a strong pretrained image editor. Since visual transformation learning is central to the paper, the contribution of visual exemplars should be evaluated more explicitly.
Questions for authors
-
Could the authors report the additional training time, GPU memory usage, and computational overhead introduced by the DINO relation loss? Given its marginal improvements in CLIP-I (GT) and LPIPS, a cost–performance analysis would help establish its practical value.
-
Could the authors evaluate CrossPair using role-only prompts without explicit editing descriptions? Additionally, how would the output change if the reference pair were replaced with one demonstrating a different transformation while keeping the query image and text instruction unchanged?
-
Could the authors clarify why the full-model OOD results differ between Tables 2 and 3, particularly the CLIP-Dir scores (0.312 vs. 0.369)? Do these experiments use the same evaluation samples, model checkpoints, prompts, and inference configurations?
3 comments
Response to Reviewer YgHh (2/2): Visual Exemplars and Evaluation Protocol
This comment addresses Weakness 3 and Questions 2-3. Comment 1/2 discusses content preservation and DINO's benefits and computational cost.
3. Text conditioning and the contribution of visual exemplars (Weakness 3 and Question 2)
(1) Does visual input still help when the text already describes the edit?
Yes. Section 3.2 and Appendix C.4 explicitly describe our text-assisted exemplar-editing setting. In Table 3, VLM-only and VLM+VAE use the same concrete edit text; the latter additionally supplies exemplars through the VAE. CLIP-I_GT improves from 0.768 to 0.776, CLIP-Dir from 0.343 to 0.350, and LPIPS_GT from 0.406 to 0.402.
These results show that VAE exemplar input provides an additional benefit when text and VLM exemplar information are already available. The improvement does not come from a more detailed textual instruction.
(2) How do we view evaluation with role-only prompts?
Role-only prompts can further assess the model's ability to infer the transformation from the visual exemplars alone. Our focus is on using visual exemplars more effectively in a text-assisted setting, so removing the concrete edit description entirely is not a prerequisite for establishing the pathway benefit above. We plan to include role-only evaluation in subsequent experiments and report the results in the appendix.
(3) What about changing the exemplar while keeping the query and text fixed?
The Relation252K test set includes multiple cases for the same transformation, with five queries per group in the seen-task evaluation. Table 2 shows how these transformations transfer across different query content. This provides evidence of cross-content transfer; changing only the exemplar while holding the query and text fixed is a further test of exemplar-specific control.
4. Differences between Tables 2 and 3 (Question 3)
(1) Why are the full model's OOD CLIP-Dir scores 0.312 and 0.369?
The tables use different evaluation sets. The component ablation in Table 3 uses the original 300 released Relation252K unseen cases, allowing all variants to be compared on the same fixed benchmark. We subsequently added 150 cases to broaden the coverage of transformation types in the main evaluation, giving the 450-case test set in Table 2. The original 300 cases are the established benchmark, not a subset selected from the 450 cases based on model performance.
Thus, 0.369 and 0.312 are averages over different evaluation sets. Section 4.1 and Appendix B.6 (Table 7) already describe the original 300 cases and the additional 150. We will state the sample count and its relationship to Table 2 directly in the Table 3 caption.
(2) Are the checkpoint, prompts, and inference settings the same?
Yes. The comparison is between CrossPair (R252K) in Table 2 and the full model in Table 3. They use the same checkpoint, prompts, and inference settings. The difference is the test set, rather than the model or inference configuration. All variants within Table 3 are evaluated on the same test set.
Thank you
Dear Reviewer YgHh:
As the discussion period closes on November 18 (AoE), we would like to kindly check whether our response has addressed your concerns. If so, we would be grateful if you would consider updating your score. We are happy to clarify anything further.
Response to Reviewer YgHh (1/2): Content Preservation and DINO Supervision
Thank you for recognizing our dual-pathway design for combining semantic understanding with visual detail, as well as the contribution of Transform-360K. This comment addresses Weaknesses 1-2 and Question 1. Comment 2/2 addresses Weakness 3 and Questions 2-3.
1. Content preservation and overall editing quality (Weakness 1)
(1) Does a lower content-preservation score mean worse editing?
Content preservation needs to be considered in the context of the requested transformation. Our benchmark includes style transfer, segmentation, and conditional representation tasks, where the correct output can differ substantially from the source. Style transfer changes texture and appearance, while segmentation or edge-map generation removes much of the photographic appearance. Higher source similarity can therefore also indicate that the requested transformation has not been fully applied.
On the seen tasks in Table 2, CrossPair has lower CLIP-I_src than LoRWeB (0.572 versus 0.690), but higher CLIP-Dir (0.438 versus 0.309), higher CLIP-I_GT (0.871 versus 0.772), and lower LPIPS_GT (0.361 versus 0.479). The outputs change the source appearance while becoming closer to the target and better following the demonstrated transformation.
Figure 5 provides concrete examples. For poster-style transfer, LoRWeB and RelationAdapter retain more of the train photograph's appearance. For watercolor transfer, LoRWeB also remains closer to a photographic appearance. CrossPair more fully reproduces the styles demonstrated by the exemplars.
(2) Does the overall evaluation support CrossPair's editing quality?
Yes. In Table 2, CrossPair achieves GPT Rank-1 rates of 53.7% for overall quality and 59.6% for transformation faithfulness, leading all compared methods on the seen tasks. LoRWeB's corresponding rates are 17.3% and 15.1%. Content preservation should therefore be evaluated alongside transformation fidelity. The target metrics, directional metric, and overall GPT evaluation all support more faithful transformation transfer and better overall editing results.
2. DINO benefits and computational cost (Weakness 2 and Question 1)
(1) What does DINO contribute when the gains in target similarity and LPIPS are small?
DINO relation supervision focuses on whether the query undergoes the same change as the exemplar. In Table 3, with the dual-pathway configuration unchanged, CLIP-Dir improves from 0.350 to 0.369, with improvements in target similarity and LPIPS as well. The main benefit is in directional consistency, which matches the objective's purpose. The dual-pathway model already has editing capability; relation supervision further improves transformation transfer.
(2) Where does the additional computation occur? Is DINO needed at inference?
During training, DINO's parameters are frozen and its inputs are resized to 224 x 224. Among the DINO branches, only the predicted-image branch retains input gradients through the encoder (Appendix C.5). Only the generator's LoRA parameters are updated. The additional training computation comes from decoding the predicted image, extracting DINO features, and backpropagating through the prediction branch.
DINO is not needed at inference. Appendix D explicitly states that DINO and the auxiliary loss computation are removed after training. Processing new exemplars and queries requires neither loading DINO nor running its feature extraction or relation computation. The benefit of this supervision therefore comes without additional inference-time DINO computation.