- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
RewardSlider works on controlling continuous edit strength on a frozen FLUX.1 Kontext through per-instance test-time optimization. It first builds a candidate trajectory by locally interpolating between source-preservation and instruction following velocities in the early sampling steps. It then calibrates the active strength range and slider control points for each pair using DreamSim, and optimizes early-step velocity residuals with SigLIP, DreamSim and DINOv2 rewards. On a 540-image subset of PIE-Bench++, it achieves the best smoothness metrics but not the best edit alignment or monotonicity, at roughly 10× the runtime of VeloEdit.
Critical strengths
- The model requires no additional heavy model training to make slider positions map to perceptually uniform changes.
- It reports runtime and memory transparently, which makes the cost of its test-time optimization clear.
Critical weaknesses
- There is no real novelty. This paper stitches together VeloEdit's velocity interpolation, generic perceptual re-spacing of slider positions, and standard reward-gradient correction. Its key component, the reward correction, is never ablated.
- The results do not support the claim. RewardSlider wins only on smoothness metrics, which its own test-time calibration directly optimizes. It trails SliderEdit on edit fidelity and Kontinuous Kontext on monotonicity, produces weaker full-strength edits, runs about 10× slower than VeloEdit, and has no user study.
Questions for authors
- If the same DreamSim-based range calibration and control-point re-spacing is applied to VeloEdit, SliderEdit and Kontinuous Kontext, does RewardSlider still outperform them?
- What is the contribution of the multi-reward correction alone (an ablation without it)?