- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
The paper proposes VCRM, a training free framework for long-context question-answering. VCRM retrieves relevant information from the context, and renders the retrieved context into an image, and the model answers the question from this rendered image. VCRM has three main modules: Hierarchical Evidence Prospecting (HEP), Semantic Fact Extraction (SFE), and Density-Differentiated rendering (DDR).
The paper experiments on LoCoMo, LongMemEval-S and HotpotQA using two small Qwen2.5-VL and Qwen3-VL models, and it reports improved accuracy with much fewer memory tokens than the baselines. The authors did ablation experiments to examine the individual components of VCRM. The experiments also demonstrate strong performance of VCRM even at only 64 visual tokens.
Critical strengths
- The observation that converting textual input into visual input can sometimes be more effective and efficient in textual QA tasks is a very interesting, surprising, and counter-intuitive result, which could have high significance if thoroughly studied and investigated.
- The experiments reports strong performance under very tight memory budgets, as few as 64 tokens on Qwen3-VL-4B, suggesting potential of VCRM in low-budget settings.
Critical weaknesses
- The paper did not provide sufficient evidence to show the benefit of visual representation over raw text. This is a very surprising observation so it also required substantial evidence to fully investigate when we shall expect such benefit. Table 4 provides a useful text-versus-image comparison, but does not report the corresponding token costs or repeat this comparison across memory budgets. Most of the experiments also bundles image conversion with visual emphasis, without comparing uniform images or text given equivalent emphasis. It therefore remains unclear when images help, particularly when the extracted facts are already short enough to fit as text (such as the example in Figure 8).
- The hyperparameter selection protocol is unclear. HEP introduces fusion weights, confidence thresholds, retrieval quotas, and pruning parameters; rendering adds further configuration choices. Their values and selection procedures are incompletely documented.
Questions for authors
- How are the hyperparameters selected? VCRM involves many hyperparameters and it is not clear whether any of the hyperparameters are tuned on the test set. Many hyperparameter selection details are missing. The authors should carefully list all the hyperparameters required for their method and explain how these hyperparameters are set. Is it set by standard/default evaluation practice, a separate validation dataset, or what else?
- How much of the reported token reduction comes from retrieval and extraction (HEP, SFE) versus rendering (DDR)? What are the token consumption and end-to-end latency of the HEP+SFE-only variant?
Dear Reviewer Qcvn,
Thank you again for your careful review and constructive feedback. We have made additional clarifications and provided supplementary analyses in response to the concerns raised in your review.
With the discussion period nearing its end, we would greatly appreciate your taking the time to review our responses and share any remaining questions or concerns. If you find that our responses have adequately addressed your concerns, we would sincerely appreciate your consideration of an updated rating.
Thank you again for your time and consideration.
Best regards,
The Authors