- Rating
- 1
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
The paper introduces Video-EMem for “write-once, query-many” long video understanding: it first encodes a video into a reusable memory under a fixed storage budget, then answers subsequent questions solely from that memory. The memory consists of text records anchored to temporal intervals and sparse images. The Writer merges multi-scale captions, allocates token budgets, compresses the text, and repairs information lost during compression, before selecting images that complement details. The Reader retrieves text relevant to the question, retrieves images as needed, and organizes the evidence into context for answer generation. The paper achieves SOTA performance on various long video benchmarks.
Critical strengths
- The paper focuses on an important problem: constructing reusable memory for long video understanding.
- The proposed method achieves strong overall performance on the long video benchmarks.
- The ablation studies are reasonably comprehensive.
Critical weaknesses
- The presentation introduces too many meaningless symbols that add little explanatory value.
- Essential implementation details are missing, including the actual prompts, the implementation of , and the concrete procedure used to evolve the operators.
- The paper lacks a complete, end-to-end example.
- Excessive defensive writing reduces readability.
- The efficiency discussion emphasizes low per-query cost without adequately accounting for the potentially substantial cost of the Writer. Memory construction costs and per-question answering costs should be reported separately.
Questions for authors
- Please simplify the presentation by removing unnecessary formalism and reducing defensive language.
- Please provide sufficient implementation details for each step of the Writer, Reader, and evolution procedure. Each component should have an informative operational description, for example, the LLM prompt, rather than being represented only by a symbol with specified inputs and outputs.
- Please include an end-to-end example of memory construction and retrieval, with the complete intermediate outputs and execution traces of the Writer and Reader, as well as the changes of Writer and Reader along the evolving progress.
- Please report model-call costs more comprehensively, separating the one-time cost of constructing memory from the cost of answering each subsequent question.