ECCV 2026 · Long-video understanding · Vision and multimodality

Tempo: turning the compressor itself into a small model that reads the question

Daily ML/AI In-Depth Paper Tracking · 2026-08-11 (Tuesday) · Field rotation: vision and multimodality

ECCV 2026 Meta AI · KAUST arXiv 2604.08120 6B · 0.5–16 tok/frame 24-paper candidate pool · 0 redraws

Positioning in one sentence: Compression is no longer a stateless module attached to a visual encoder. It is a small VLM that reads the user's question and decides how much attention each segment deserves. Its accompanying relevance scores directly allocate the global token budget.

0. Issue metadata and methodology

ItemContent
Date2026-08-11 (Tuesday, date +%u = 2)
Rotating research areaVision and multimodality (detection/segmentation, VLMs, video understanding, representation learning)
Candidate-pool size24 papers (after retrieving 63 CVPR 2026 Highlights, removing generative-model papers reserved for Wednesday and nonvision papers, and adding 3 recent high-profile preprints)
Selection methodshuf -i 1-24 -n 3 → output 19, 20, 13; first draw #19 had sufficient materials, 0 redraws
Core paperTempo (ECCV 2026, Meta AI + KAUST)
Deduplication index⚠️ Could not access. This was a scheduled cloud task with no desktop bridge; ml-report-index.md was unreachable, preventing the 14-day deduplication check. See the endnote.
Transparency statement upfront: Every number in this report comes from the actually retrieved arXiv HTML full text (arxiv.org/html/2604.08120v1), project website, or GitHub README, with table references. Anything not found—such as measured latency/FLOPs, standard deviations, or a v2 date—is explicitly marked “not provided by the paper” or “not found.” No number is inferred from memory.

1. Link verification table

1.1 Focal paper

All links were checked through retrieval. ✅ Confirmed accessible; ⚠️ exists but retrieval is restricted or information conflicts; ❌ not found.

ResourcesLinkState
arXiv abstract pagearxiv.org/abs/2604.08120✅
arXiv full-text HTML (v1)arxiv.org/html/2604.08120v1✅ Main data source for this report
arXiv PDFarxiv.org/pdf/2604.08120✅
Project pagefeielysia.github.io/tempo-page✅
Code repositorygithub.com/FeiElysia/Tempo✅ Apache-2.0
Model weights (final)huggingface.co/Vision-CAIR/Tempo-6B✅ Academic noncommercial use
Model weights (by stage)Vision-CAIR/Tempo-6B-Stage0 / Stage1 / Stage2✅ All three intermediate checkpoints public
HF paper pagehuggingface.co/papers/2604.08120✅ 21 upvotes
Online demohuggingface.co/spaces/Vision-CAIR-Admin/Tempo⚠️ The project page lists Vision-CAIR/Tempo, while the HF paper page actually lists Vision-CAIR-Admin/Tempo with SwingRain/Tempo, ; the two conflict
Official ECCV 2026 proceedings—❌ Not found(Not yet on ECVA; venue information is self-reported in the GitHub README and project page)
KAUST institutional-repository copyrepository.kaust.edu.sa/…✅
Version-date note: arXiv ID 2604.08120 Under arXiv identifier conventions, this corresponds to April 2026. The HF paper page's “April 10, 2024” conflicts with that convention and is treated as an HF parsing error. This report uses April 2026, v1. Whether v2 exists and its date: not found (export.arxiv.org API was blocked by this session's egress policy with HTTP 403).

1.2 Related work

The paperConference website / ProceedingsarXivCodeWeightsProject page
LLaMA-VID ECVA ECCV 2024 ✅ · Springer ✅ pp.323–340 2311.17043 ✅
v1: 2023-11-28
JIA-Lab-research ✅ HF ✅ llama-vid.github.io ✅
LongVA ❌ Not found(No venue claim; OpenReview blocked by a bot wall; treated as a preprint) 2406.16852 ✅
v1: 2024-06-24
v2: 2024-07-01
EvolvingLMMs-Lab ✅ HF ✅ lmms-lab.com ✅
LongVU ICML 2025 Poster 44939 ✅ Main conference 2410.17434 ✅
v1: 2024-10-22 (v1 only)
Vision-CAIR ✅ HF ✅ vision-cair.github.io ✅
BIMBA CVPR 2025 Poster 32662 ✅ Main conference · CVF supplementary material ✅ (Main PDF returned 403 ⚠️) 2503.09590 ✅
v1: 2025-03-12
v2: 2025-03-13
md-mohaiminul ✅ HF ✅ ⚠️ sites.google.com/view/bimba-mllm Retrieval blocked
VideoChat-Flash OpenReview ICLR 2026 Poster ✅ Main conference 2501.00574 ✅
v1: 2024-12-31
v4: 2025-07-13
OpenGVLab ✅ HF ✅ InternVideo blog ✅
STORM
(Efficiency comparison)
CVF ICCVW 2025 CLVL ⚠️ Workshop, not the main conference 2503.04130 ✅
v1: 2025-03-06
v2 date not found
❌ Official repository not found ❌ Not found research.nvidia.com ✅
Important correction: LLaMA-VID's original repository github.com/dvlab-research/LLaMA-VID has moved to JIA-Lab-research/LLaMA-VID. Although the old URL redirects, citations should use the new path.

2. In-depth analysis of the core paper

Small Vision-Language Models are Smart Compressors for Long Video Understanding

Junjie Fei, Jun Chen, Zechun Liu, Yunyang Xiong, Chong Zhou, Wei Wen, Junlin Han, Mingchen Zhuge, Saksham Suri, Qi Qian, Shuming Liu, Lemeng Wu, Raghuraman Krishnamoorthi, Vikas Chandra, Mohamed Elhoseiny, Chenchen Zhu
Meta AI · KAUST — ECCV 2026 — arXiv 2604.08120 (April 2026)

2.1 Positioning in One Sentence

The compressor is promoted from a feed-forward module into a small VLM that reads the question. One forward pass produces both compressed memory tokens and a score for how relevant the segment is to the question; the latter directly controls global budget allocation.

The key is not using a small model for compression—BIMBA and LongVU already compress—but one forward pass with two outputs: relevance is not computed by a separate retriever, but taken from the compressor's own hidden states. Compression and scoring therefore share exactly the same multimodal context, with O(1) routing overhead.

2.2 Motivation and Problem Evidence

The paper frames the problem as a structural mismatch: video streams are dense and variable in duration, while LLM context is fixed and scarce. Its introduction says dense visual streams quickly exhaust token budgets and worsen the lost-in-the-middle problem (citing Liu et al., 2024c).

Existing approachThe paper's criticism (original wording)Underlying reason for failure
Sparse sampling"risks skipping the transient yet decisive moments required to answer a specific query"Uniform sampling ignores when the answer occurs; it is a query-independent prior
Uniform pooling"blur fine-grained evidence in query-critical segments while wasting representational bandwidth on irrelevant backgrounds"Distributes bandwidth Average across segments with highly uneven information density

What is novel about this problem framing? Not that long videos are difficult—an old problem—but that the paper reframes it as a bandwidth-allocation problem rather than compression-ratio problem. Most predecessors optimize a single scalar: tokens per frame (2 for LLaMA-VID, 16 for VideoChat-Flash, 16× compression for BIMBA). Tempo argues that tokens per frame should not itself be a constant.

Why is it worth solving? One quantitative argument comes from the paper's Table 1: Qwen2.5-VL-7B uses 1924 tokens/frame to score 65.1 on Video-MME, while Tempo uses a measured average of approximately 2.8–3.6 tokens/frame to score 67.8. This is about a 687-fold token gap, with a gain of +2.7pp in the opposite direction. It suggests that much of today's visual bandwidth is wasted and that the waste can be systematically recovered.

⚠️ Transparency caveat: The Introduction provides no failure-rate statistics or quantitative diagnostic experiments for previous methods, such as the percentage of LVBench examples where uniform sampling misses the ground-truth segment. The 687× argument above is my derivation from Table 1, not motivation evidence supplied by the authors. This is the first gap in the paper's reasoning.

2.3 The Paper's Argument

The argument proceeds through four observation-to-inference steps:

  1. Observation: A video's information density depends strongly on the query. Asking when someone tightens a screw requires a very different temporal distribution from asking for a video summary.
    Inference: Compression must be query-aware. (→ LongVU / BIMBA already reached this point)
  2. Observation: Query-aware compression requires a module that understands both vision and text. A small VLM is exactly such a module, already available and pretrained.
    Inference: Instead of designing a new compression operator, repurpose an SVLM as the compressor. (→ First turning point)
  3. Observation: While compressing, the SVLM already knows whether the segment relates to the question; it simply has not been asked to say so.
    Inference: Its hidden states can provide at no extra decoding cost a relevance score. (→ Second turning point; the foundation of ATA)
  4. Observation: Segment-level scores remove the need to divide the global token budget evenly.
    Inference: Design ATA to distribute the budget by score continuously rather than through binary top-K selection.

Implicit Design Trade-Off(Implicit in the design, though not explicitly stated):

2.4 Methodology and Mechanisms

2.4.1 Architecture overview

┌──────────────── Parallel segments ────────────────┐ Video V │ │ ├─ S₁ ──┐ │ ┌───────────────────────────────────────────┐ │ ├─ S₂ ──┼──────▶│ │ Local compressor C_φ = SVLM │ │ ├─ ... │ │ │ (Qwen3-VL-2B-Instruct) │ │ └─ S_N ─┘ │ │ │ │ │ │ Causal sequence (order is essential): │ │ User query Q ────┼─▶│ [system prompt] │ │ │ │ ↓ │ │ │ │ X_i ← visual tokens (segment S_i) │ │ │ │ ↓ │ │ │ │ Q ← user query │ │ │ │ ↓ │ │ │ │ M ← learnable memory tokens │ │ │ │ (last, so causal attention lets │ │ │ │ every M see X_i + Q) │ │ │ └───────┬────────────────┬──────────────────┘ │ │ │ │ │ │ H_i (k_max=128) h_i^rel │ │ Memory tokens Relevance hidden state │ └──────────┼────────────────┼──────────────────────┘ │ │ │ ▼ │ s_i = σ((w_yes − w_no)ᵀ h_i^rel) │ │ ← O(1), no autoregressive decoding │ ▼ │ ┌──────────────────────┐ └─────▶│ ATA adaptive allocation│ │ Budget B_max (4K/8K) │ └─────────┬────────────┘ │ H_i[1:k_i] ← prefix truncation, O(1) slicing ▼ Linear projection → H̃_i + timestamps <t=2.0s> ▼ ┌─────────────────────────────────┐ │ Global decoder D_θ = Qwen3-LM-4B│ └────────────────┬────────────────┘ ▼ Answer Total parameters: 6B = 2B (SVLM) + 4B (LLM)

2.4.2 Formal definitions

End-to-end objective—note that there is no auxiliary compression loss, routing network, or distillation loss, only a standard autoregressive loss:

L_AR(θ, φ) = − Σ_{t=1}^{T} log p_θ( a_t | a_<t, Q, {H̃_i}_{i=1}^{N} )

Fixed capacity k_max itself acts as a structural bottleneck that induces compression. This is the method's most economical design choice: compression emerges from the training objective rather than explicit supervision.

Zero-shot relevance prior—let h_i^rel denote the SVLM's final hidden state before answering the binary question of whether the segment is relevant to the query, and w_yes / w_no and for frozen language-head weights:

s_i = σ( (w_yes − w_no)ᵀ · h_i^rel ) ∈ (0, 1)

The paper's most elegant engineering step reduces an otherwise autoregressively decoded judgment to one vector inner product. It also emphasizes extracting s_i and H_i in the same forward pass(the forward pass continues after reading the hidden state), ensuring that both outputs condition on exactly the same multimodal context.

ATA's two-stage allocation:

Stage 1 (contrastive linear allocation) ŝ_i = (s_i − min(s)) / (max(s) − min(s) + ε) # Min-max normalization k_i^ideal = k_min + ⌊ (k_max − k_min) · ŝ_i ⌋ # Linear capacity mapping Stage 2 (capacity protection) If Σ_i k_i^ideal ≤ B_max : k_i = k_i^ideal Otherwise : B_res = B_max − N · k_min k_i = k_min + [ B_res · ŝ_i / (Σ_j ŝ_j + ε) ] Within-segment reduction H_i^ATA = H_i[1 : k_i] # Prefix truncation, O(1) tensor slicing

Prefix truncation is justified by the paper's semantic front-loading hypothesis: causal attention packs the most salient evidence into the earliest memory tokens. Ablations strongly support this hypothesis (see §2.5.3-C).

2.4.3 Key mechanisms

Mechanism / dimensionDesign choiceMotivationKey hyperparameters
Local compressorQwen3-VL-2B-Instruct (trainable)Ready-made cross-modal understanding; no new operatorSVLM lr = 2×10⁻⁶
Global decoderQwen3-LM-4BOnly reasons over the sparse sequencelr = 1×10⁻⁵
Memory slotsLearnable memory tokens placed at the end of the causal sequenceEnsures every M sees the entire visual + query contextk_max = 128
Relevance scoringFrozen language-head yes/no logit difference + sigmoidO(1), avoiding autoregressive overheadNone (zero-shot, no training)
Budget allocationTwo-stage linear allocation + proportional fallbackContinuous allocation outperforms binary top-KB_max ∈ {4K, 8K}; k_min = 4
Within-segment reductionDynamic prefix truncation H_i[1:k_i]Semantic front-loading hypothesis; O(1) slicingk_i ∈ [4, 128]
Temporal anchorsMinimum guaranteed allocation k_min = 4 tokenPreserves temporal continuity and avoids missing segmentsk_min = 4
Temporal localizationExplicit timestamp prefixes <t=2.0s>Preserves segment temporal identity and causal order2 FPS sampling

2.4.4 Engineering details

Four-stage progressive curriculum(Appendix Table A; module freezing is crucial):

ConfigurationStage 0: alignmentStage 1: pretrainingStage 2: broad SFTStage 3: long-context SFT
Local compressor SVLMFrozenUnfrozenUnfrozenFrozen
Memory tokenUnfrozenUnfrozenUnfrozenFrozen
Linear projection layerUnfrozenUnfrozenUnfrozenFrozen
Global decoder LLMFrozenUnfrozenUnfrozenUnfrozen
Learning rate (LLM/projection/memory)1×10⁻³1×10⁻⁵1×10⁻⁵1×10⁻⁵
LR (SVLM)—2×10⁻⁶2×10⁻⁶—
Global batch size12825612864
Maximum sampled frames f_max1 (images only)8128384
Segment capacity k_max128128128128
Maximum LLM context81928192819216384
Warmup / Epoch3% / 13% / 13% / 13% / 1

Data mixture(Appendix Table B):

ModalityStage 0Stage 1Stage 2Stage 3Total
Image~558K~2.00M~0.93M—~3.49M
Video—~1.38M~2.25M~384K~4.01M
Text—~143K~71K—~214K
Subtotal~558K~3.52M~3.25M~384K~7.71M
Stage 3's design deserves emphasis: Freeze the entire compression side and train only the LLM to reason over sparse long sequences. This cleanly separates learning to compress from learning long-context reasoning.

2.5 Experimental Design and Quantitative Results

2.5.1 Benchmarks and datasets

BenchmarkMean durationCapability focus
LongVideoBench473 sReferential reasoning requiring specific-frame localization
MLVU651 sComprehensive multitask long-video understanding
Video-MME (w/o sub.)1010 sComprehensive evaluation with short/medium/long categories
Video-MME Long2386 sLong-video subset
LVBench4101 sExtremely long videos (>1 hour), the paper's primary focus

This benchmark progression is well designed: duration increases monotonically from 473s to 4101s, directly exposing degradation with video length.

2.5.2 Main-results matrix (Table 1)

pp = percentage point. Bold marks the column best.

MethodSizetok/frameLongVB
473s
MLVU
651s
VMME
1010s
VMME-L
2386s
LVBench
4101s
Five-task mean
— Closed-source models —
GPT-4o——66.764.671.965.330.859.86
Gemini 1.5 Pro——64.0—75.067.433.1—
— General open-source MLLMs —
VideoChat2-HD7B72—47.945.339.8——
LLaVA-OneVision7B19656.464.758.2———
LLaVA-Video7B67658.270.863.3———
VideoLLaMA37B≤9159.873.066.254.945.359.84
InternVL3.58B25662.170.266.0———
Molmo28B8367.5—69.9—52.8—
Qwen2.5-VL7B192456.070.265.1—45.3—
Qwen3-VL ← Tempo's compressor backbone2B≤640—68.361.9—47.4—
Qwen3-VL ← See critique ③8B≤640—78.171.4—58.0—
— Specialized long-video MLLMs —
LLaMA-VID7B2—33.225.9—23.9 (13B)—
LongVA7B144—56.352.646.2——
Kangaroo8B25654.861.056.046.739.451.58
LongLLaVA13B14453.5—53.846.4——
LongVILA7B19657.1—60.147.0——
LongVU ← See critique ④7B64—65.460.659.5——
Storm7B6460.572.963.453.4——
BIMBA7B3659.571.464.7———
VideoChat-Flash7B1664.774.765.355.448.261.66
Tempo (4K budget)6B0.5–16
Measured 2.8–3.6
64.575.667.857.852.763.68
Tempo (8K budget)6B0.5–16
Measured 3.1–4.3
65.175.267.757.052.363.46

Figure 1 · Tempo's advantage over the strongest open-source competitor grows monotonically with video duration

Source: Table 1. Benchmarks are ordered by mean duration (473s → 4101s). Labels above bars show Δ (Tempo 4K − VideoChat-Flash). Hover for exact values.

VideoChat-Flash 7B (16 tok/frame, ICLR 2026) Tempo 6B (4K budget, measured 2.8–3.6 tokens/frame)
40 50 60 70 80 Benchmark score 64.7 64.5 −0.2 LongVideoBench 473 s 74.7 75.6 +0.9 MLVU 651 s 65.3 67.8 +2.5 Video-MME 1010 s 55.4 57.8 +2.4 Video-MME Long 2386 s 48.2 52.7 +4.5 LVBench 4101 s ← Increasing mean video duration →

Relative-gain calculation(Tempo 4K vs. VideoChat-Flash, the strongest specialized open-source long-video baseline):

BenchmarkVideoChat-FlashTempo 4KΔRelative gain
LongVideoBench (473s)64.764.5−0.2 pp−0.31%
MLVU (651s)74.775.6+0.9 pp+1.20%
Video-MME (1010s)65.367.8+2.5 pp+3.83%
Video-MME Long (2386s)55.457.8+2.4 pp+4.33%
LVBench (4101s)48.252.7+4.5 pp+9.34%
Five-task mean61.6663.68+2.02 pp+3.28%
📈 Key trend (one of the paper's most persuasive quantitative findings): Tempo's gain over VideoChat-Flash has a strictly monotonic positive relationship with video duration: −0.2pp at 473s, +0.9pp at 651s, +2.5pp at 1010s, +2.4pp at 2386s, and at 4101s, +4.5pp. This is not random fluctuation; it is the pattern adaptive bandwidth allocation should produce: longer videos have sparser information, greater waste from uniform allocation, and greater adaptive gains. Conversely, Tempo has a net disadvantage at 473s. The paper does not discuss this crossover, although it defines the method's applicability boundary.

Comparison with LLaMA-VID (the most important numbers for the technical lineage)

At almost identical token budgets(LLaMA-VID's fixed 2 tokens/frame versus Tempo's measured mean of 2.8 tokens/frame):

BenchmarkLLaMA-VID (2 tok/f)Tempo 4K (~2.8 tok/f)Δ
MLVU33.275.6+42.4 pp
Video-MME25.967.8+41.9 pp
LVBench23.9 (13B)52.7 (6B)+28.8 pp
These numbers suggest that the problem with 2 tokens/frame was never simply token count, but how those two tokens were selected. Two and a half years of progress more than doubled performance under a similar budget.

Figure 2 · The token-budget/performance Pareto frontier: an evolution that turns back toward the upper left

The horizontal axis is visual tokens/frame (log scale), and the vertical axis is MLVU score. Source: Table 1. Dashed lines connect the technical lineage chronologically: initially up and right (more tokens for higher performance), then back toward the upper left(far fewer tokens with continued performance gains). One vertical axis; no dual y-axes.

Predecessors in the lineage Tempo (focal paper) Other comparison models
30 40 50 60 70 80 MLVU score 1 10 100 1000 Visual tokens per frame (log scale) Qwen2.5-VL BIMBA Storm LLaMA-VID (2023.11) LongVA (2024.06) LongVU (2024.10) VideoChat-Flash (2024.12) ★ Tempo (2026.04) ← Fewer tokens (cheaper) More tokens (costlier) →
How to read Figure 2: The path moves from lower right (LLaMA-VID: very few tokens but very poor performance) toward upper right (LongVA: 144 tokens/frame for better performance), then continues back toward the upper left——LongVU 64, VideoChat-Flash 16, Tempo 2.8. The horizontal axis goes out and back; the vertical axis rises monotonically by 42.4pp. This summarizes the subfield's last 30 months: token selection, rather than token budget itself, is the performance bottleneck.

2.5.3 Ablations (Table 2, five levels)

A. Progressive training curriculum

ConfigurationBudgetLongVBMLVUVMMEVMME-LLVBenchMean
Without Stage 3 (long-context SFT)16K61.467.266.156.347.359.66
w/o ATA16K62.873.567.056.251.162.12
Default Tempo8K65.175.267.757.052.363.46
🔥 Evidence of a regime change: w/o ATA Use A 16K budget scores only 62.12, whereas full Tempo with an 8K budget(half as large) scores 63.46. Half the budget, yet performance rises 1.34pp. This is the strongest defense of ATA: allocation strategy matters more than allocation quantity. Stage 3 also contributes substantially: MLVU rises from 67.2 to 75.2, +8.0pp the largest single-metric gap in the table.
⚠️ However, these two comparison rows use A 16K budget, while the default uses 8K. This is an uncontrolled comparison: budget and the ablated component change together. The paper does not report 8K-budget w/o ATA results. See critique ② in §2.7.

B. Segment-level budget allocation (ATA's central defense)

PolicyLongVBMLVUVMMEVMME-LLVBenchMeanvs. ATA
Adversarial routing (retains Minimum scoring segments)50.759.352.447.836.949.42−14.04 pp
Random dropping59.370.963.655.249.859.76−3.70 pp
Uniform subsampling61.974.066.355.249.961.46−2.00 pp
Hard top-K routing (retains Maximum scoring segments)63.573.966.756.252.762.60−0.86 pp
ATA (continuous allocation)65.175.267.757.052.363.46—

Figure 3 · Adversarial-routing collapse: relevance scores contain real information

Five-benchmark means for five segment-level allocation strategies (Table 2-B; means calculated in this report). The key finding is that adversarial routing falls 10.34pp below random dropping. If scores were noise, reversing them should be equivalent to random selection. Hover for values.

Comparison strategies ATA (proposed method) Adversarial routing (reverses the scores)
45 50 55 60 65 Five-benchmark mean score Adversarial routing 49.42 Random dropping 59.76 Uniform subsampling 61.46 Hard top-K routing 62.60 ★ ATA 63.46 −10.34pp vs. random
🔥 The strongest quantitative evidence in the paper: Adversarial routing, which deliberately retains the least relevant segments, falls below Random dropping by 10.34pp(49.42 vs. 59.76). This is a particularly clean causal argument: if s_i were noise, reversing it should perform equally to random selection. Instead, reversing it is substantially worse than random, indicating that s_i encodes real query–segment relevance. This supports the zero-shot relevance prior more directly than any positive SOTA score.
⚠️ Yet the same table contains a problem: on LVBench (4101s, the paper's main focus), hard top-K routing scores 52.7, above ATA's 52.3. On the extremely long videos that most need adaptive allocation, ATA loses to simple binary top-K. See critique ① in §2.7.

C. Within-segment token reduction (testing semantic front-loading)

ApproachLongVBMLVUVMMEVMME-LLVBenchMean
Uniform Tails truncation (fixed 64)59.571.664.154.841.858.36
Dynamic Tails truncation (retain the final k_i)61.973.464.854.250.560.96
Uniform Prefix truncation (fixed 64)63.273.466.956.251.562.24
Token Merging (merge to k_i tokens)63.674.966.355.453.062.64
Dynamic prefix truncation (default)65.175.267.757.052.363.46
Strong evidence supports semantic front-loading: under exactly the same fixed budget of 64 , prefix truncation exceeds suffix truncation by 3.88pp(62.24 vs. 58.36); on LVBench, the gap expands to +9.7pp(51.5 vs. 41.8). Causal attention does pack key evidence into earlier memory tokens. This finding is independently reusable: any causal-LM token compressor can retain the beginning rather than the end.

⚠️ However, Token Merging scores on LVBench 53.0 > the default's 52.3, again outperforming the default on extremely long videos.

D. Relevance-score sources and zero-shot priors

Scoring sourceLongVBMLVUVMMEVMME-LLVBenchMean
Base-model prior (explicit routing prompt)65.776.367.657.352.763.92
Tempo SVLM prior (standard prompt)64.175.467.257.053.463.42
Base-model prior (standard prompt)64.675.167.256.152.663.12
External dense retriever (Qwen3-VL Reranker)64.375.467.257.051.863.14
Tempo SVLM prior (explicit routing prompt) ← Paper default65.175.267.757.052.363.46
🚨 This is the paper's most awkward table and, in my view, a key issue: The default configuration (63.46) is not the best in this group. The base-model prior with an explicit routing prompt scores 63.92, higher by +0.46pp, winning on 4 of the 5 benchmarks (65.7>65.1, 76.3>75.2, 57.3>57.0, 52.7>52.3; only overall Video-MME is marginally lower, 67.6<67.7).

This means that as a router, the fine-tuned SVLM performs worse than the original base model without Tempo training. The paper neither explains this counterintuitive result nor changes its default. A plausible hypothesis is that Stage 1/2 compression training biases the SVLM toward compression-friendly representations, harming discriminative calibration. This is my hypothesis, not a tested explanation.
A clean positive argument: The external dense retriever (63.14) offers almost no advantage and even trails the free base-model prior (63.92), strongly supporting the claim that a separate retriever is unnecessary.

E. Temporal continuity (minimum token allocation)

ApproachLongVBMLVUVMMEVMME-LLVBenchMean
Hard pruning (0 tokens for irrelevant segments)63.974.867.456.352.362.94
Minimum temporal anchor k_min = 465.175.267.757.052.363.46

k_min = 4 contributes only +0.52pp, the smallest effect among the five ablation groups. It is necessary by design to avoid breaking the timeline, but its quantitative benefit is far below ATA (+2.00pp vs. uniform) and prefix truncation (+2.50pp vs. suffix).

2.5.4 Budget sensitivity: a regime change understated by the paper

BenchmarkTempo 4KTempo 8KΔ(8K − 4K)
LongVideoBench (473s)64.565.1+0.6
MLVU (651s)75.675.2−0.4
Video-MME (1010s)67.867.7−0.1
Video-MME Long (2386s)57.857.0−0.8
LVBench (4101s)52.752.3−0.4
Mean63.6863.46−0.22
⚡ Highlighted regime change: Doubling the budget lowers mean performance by 0.22pp, with 4 of 5 benchmarks declining. Only the shortest benchmark, LongVideoBench, benefits. The paper explains in Figure 3's caption that a strict 4K budget optimally filters standard long-video tasks, while larger budgets add marginal noise. It also claims that larger capacities such as 12K monotonically unlock new peaks on LVBench at higher frame densities.

However, Table 1's 8K row does not support the latter claim: LVBench scores 52.3 at 8K, below 52.7 at 4K. Figure 3's claim and Table 1 are in tension. An unstated confound is that Figure 3 sweeps both budget and maximum frame count and Budget, while Table 1 fixes frame count. The paper provides no budget-monotonicity curve at fixed frame count, so the claim that larger budgets are better is not cleanly established.
Cross-paper evidence: This more-is-not-better phenomenon echoes LongVA: Video-MME scores 52.6 at 128 frames but falls at 384 frames to 51.8(LongVA Table 4). Two independent papers with opposite approaches—expanding versus compressing context—encounter the same obstacle: an LLM's effective context for long visual sequences is much shorter than its nominal context. This is also STORM's only acknowledged limitation: pretrained LLMs have shorter effective context lengths in practice. Three independent observations across three papers point to the same unresolved fundamental problem(see §6.1①).

2.5.5 Statistical significance

⚠️ The paper provides no standard deviations, confidence intervals, or repeated-run results. Every number in Tables 1 and 2 comes from a single run. This matters because many key Table 2 differences are on the order of 0.2–0.9pp (ATA vs. hard top-K 0.86pp; default vs. base prior 0.46pp; k_min 0.52pp; 4K vs. 8K 0.22pp), a scale comparable to typical single-run fluctuations on long-video benchmarks. Without error bars, these conclusions should be treated as directional indications rather than established findings. Only the 14pp adversarial-routing gap is statistically beyond dispute.

2.5.6 Efficiency analysis: a conspicuous omission

The paper repeatedly emphasizes ATA's O(1) complexity, single forward pass, and avoidance of autoregressive overhead. However,

❌ it provides no measured efficiency numbers: no wall-clock latency, TFLOPs, GPU memory, throughput comparison, or end-to-end speed comparison with VideoChat-Flash/STORM.

For a paper centered on efficiency, this is a serious gap. In particular, Tempo's SVLM runs a 2B-model forward pass for every segment, with segment count growing linearly with duration. For a 4101s LVBench video, 2 FPS × 4101s ÷ 8 frames/segment ≈ 1025 segments, namely 1025 forward passes through a 2B model. Is this actually cheaper than VideoChat-Flash's one-shot hierarchical compression?The paper does not answer, and public materials do not let me verify it. By contrast, STORM reports measured latency of 4.31s → 1.82s (−58.4%). Tempo's evidentiary rigor is clearly weaker here.

2.6 Assessment of Value

The Substantive Contribution

Neither small-model video compression (BIMBA already learns compression) nor query awareness (already in LongVU) is new. Tempo's actual contribution is making compression and routing two outputs of the same forward pass.

Previously, query-aware methods faced a tradeoff: heuristic scores (LongVU's DINOv2 similarity plus attention, cheap but semantically indirect) or external retrievers (accurate but expensive, with representations misaligned with the compressor). Tempo offers a third path: the compressor has already considered the question while compressing; simply read out that assessment. Table 2-D provides a clean comparison: the external dense retriever (63.14) is no better than the freely extracted internal prior (63.46).

Independently Reusable Designs

  1. Logit-difference projection for zero-shot relevance scoring s = σ((w_yes − w_no)ᵀh). This is general: any causal-LM system needing continuous confidence for a binary judgment can replace autoregressive decoding with an O(1) calculation. Applications include RAG reranking, agent tool selection, and data-cleaning scores.
  2. Retain the prefix, not the suffix (semantic front-loading). Table 2-C's +3.88pp (+9.7pp on LVBench) is a reusable empirical finding: causal-attention compressed representations concentrate information at the beginning. KV-cache eviction and token-pruning methods should default to removing the tail.
  3. Place memory tokens at the end of the causal sequence. This simple but crucial construction turns compression into attention-based reading without new operators.
  4. Continuous allocation > binary top-K as a general principle (Table 2-B, +0.86pp): a modest but clear direction.
  5. Train compression and reasoning separately(Stage 3 freezes the entire compression stack and trains only the LLM). The curriculum itself is transferable.

Implications for Future Work

Tempo opens a research space in hierarchical routing. Section 6 proposes turning the global LLM into an active routing agent that requests high-resolution representations of selected segments as needed. This converts one-shot compression and decoding into multiround agentic retrieval. If successful, long-video understanding would shift from compression to agent retrieval, converging with deep research and agentic RAG.

2.7 Limitations

Category 1: author-acknowledged limitations (Section 6, Discussion and Future Works)

  1. Routing is entirely zero-shot, without post-training. The authors propose SFT or RL to explicitly develop this capability.
  2. Compression depth is fixed and cannot adapt reasoning effort. Inspired by reasoning-model test-time compute, the authors nevertheless acknowledge the substantial optimization challenge of adaptive autoregressive extraction without creating a severe latency bottleneck.
  3. Multiround dialogue requires re-extracting all visual features. Query-conditioned compression means a follow-up question requires rerunning the whole video.

Category 2: additional critique (8 independent observations)

① [Underperforming subtask + argument gap] ATA is not optimal on the primary benchmark, LVBench, losing to three simpler alternatives

Hard top-K routing in Table 2-B scores on LVBench 52.7 > ATA's 52.3; Token Merging in Table 2-C scores 53.0 > 52.3; the Tempo SVLM with a standard prompt in Table 2-D scores 53.4 > 52.3. The last is the highest LVBench result in the table, 0.7pp above the main table's claimed SOTA of 52.7. The central narrative makes continuous adaptive allocation crucial for extremely long videos, yet continuous allocation loses to binary allocation on the longest benchmark, contradicting that claim.

A plausible mechanism is that LVBench's 4101s videos yield very large N; ATA's proportional fallback formula k_i = k_min + [B_res · ŝ_i / Σŝ_j] then, because Σŝ_j is too large, compresses each segment toward k_min and becomes approximately uniform. Hard top-K at least gives selected segments full capacity. The paper does not discuss ATA's large-N degeneration, leaving a clear gap.

② [Experimental design] Ablations do not control token budget

In Table 2-A, w/o Stage 3 with w/o ATA are measured at a 16K budget, while the default is at 8K. The claimed Stage 3 contribution of +3.80pp and ATA contribution of +1.34pp therefore both reflect confounding between budget and component. The paper supplies neither 8K-budget w/o ATA controls nor full Tempo at 16K. Table 2-A cannot isolate attribution.

③ [Missing fair comparison] The table structure downplays the gap to the strongest same-family model, Qwen3-VL-8B

Both Tempo components come from the Qwen3 family (Qwen3-VL-2B + Qwen3-LM-4B), but Qwen3-VL-8B leads on all three shared benchmarks in Table 1:

BenchmarkQwen3-VL-8BTempo 4K (6B)Δ
MLVU78.175.6−2.5 pp
Video-MME71.467.8−3.6 pp
LVBench58.052.7−5.3 pp
Three-task mean69.1765.37−3.80 pp

With more parameters but a simpler architecture, this same-family model beats Tempo on every shared benchmark, with gaps likewise growing with duration (−2.5 → −3.6 → −5.3). Tempo is correctly positioned as SOTA at 6B, but the paper does not ask: what happens with Tempo on an 8B backbone, or with Qwen3-VL-8B under the same token budget? Without this head-to-head, the central proposition that compression beats expansion is not established.

For context, Tempo's gains over its own compressor backbone Qwen3-VL-2B are +7.3 / +5.9 / +5.3pp (three-task mean +6.17pp). This is an honest positive result that could have been emphasized more.

④ [Underperforming subtask] LongVU, a 2024 heuristic method, wins on Video-MME Long

LongVU (ICML 2025, 64 tokens/frame, entirely heuristic without learning) scores on Video-MME Long 59.5, above Tempo 4K's 57.8(−1.7pp) and Tempo 8K's 57.0 (−2.5pp). This is the only subtask where an earlier, simpler method overtakes Tempo, and the paper does not discuss it. At a mean 2386s, Video-MME Long lies within Tempo's supposed advantage regime, weakening the claim that adaptive allocation broadly dominates long videos.

⑤ [Argument gap + unexplained counterintuitive result] The default is not the best ablated configuration

As §2.5.3-D notes, the base-model prior with explicit routing prompts averages 63.92 and wins 4 of 5 benchmarks, exceeding the default's 63.46. The paper neither explains why fine-tuning worsens the SVLM as a router nor updates the default. This is a methodological concern: if Tempo training harms discriminative calibration, sharing one forward pass for compression and routing introduces an internal tension—compression and routing objectives may compete. A simple experiment measuring routing AUC at Stage 0/1/2/3 checkpoints could test this hypothesis, but the paper does not conduct it.

⑥ [Experimental design] Training and inference use different segment windows without ablation

Training uses 4 frames/segment, while inference uses 8 frames/segment(§4.1), a 2× distribution shift. The paper neither explains the motivation—presumably covering more frames at fixed B_max —nor analyzes inference-window sensitivity. Because k_max = 128 is unchanged, 8 frames/segment gives each inference frame half its training-time memory capacity. This may be a hidden reason the 4K budget beats 8K: a smaller budget forces more aggressive segment discrimination, partly compensating for the shift. The paper does not connect the two.

⑦ [Reproducibility + metric validity] Efficiency claims lack measurements, while cost grows linearly with duration

As §2.5.6 notes, there are no latency/FLOPs/memory data. More specifically, roughly 1025 forward passes through a 2B model on LVBench may offset global-LLM token savings. The claimed O(1) describes only relevance scoring, not the entire compression pipeline. Presenting this local O(1) claim in the context of an efficiency-focused paper risks misleading readers. Future work should add a three-dimensional latency/memory/accuracy Pareto plot directly comparing VideoChat-Flash and STORM.

⑧ [Statistical validity] No error bars, while most key differences are near the noise scale

At least 5 key Table 2 gaps are ≤0.9pp: ATA vs. top-K 0.86; default vs. base prior 0.46; k_min=4 vs. hard pruning 0.52; 4K vs. 8K 0.22; Token Merging vs. default 0.82. Single runs without seed variance cannot support strong claims that design X beats Y. Just 3 seeds on MLVU and LVBench would substantially improve credibility.

Limitations of My Own Analysis (Disclosure)

3. Related-work retrospective

These five papers follow Tempo's citation lineage, forming a clear chain of problems addressed rather than a parallel list.

3.1 LLaMA-VID — November 2023 arXiv / ECCV 2024 main conference (pp. 323–340)

① Problem addressed. Long videos cannot fit into LLM context. LLaMA-VID offered an unusually aggressive answer: just 2 tokens per frame. A Q-Former generates queries from the user's instruction Q_t and aggregates through context attention into one context token; adaptive pooling produces one content token. EVA-G serves as visual encoder. This lets 64K context hold over 3 hours of video. Its core contribution: demonstrating that 2 tokens/frame is technically feasible.

② Unresolved gap. The authors acknowledge this explicitly in their conclusion:

"Although LLaMA-VID succeeds to represent hour-long videos in LLMs, it focuses more on temporal consistency and may lose spatial details in each frame. In the future work, we plan to maintain dense spatial information for each frame outside the LLM..."

The more fundamental gap is that the allocation of these 2 tokens is static. A crucial action and an empty shot both receive 2 tokens. Table 5 quantifies the cost: compressing content to 1 token loses 2%–6%. The gap is that compression ratio is a global constant rather than a local variable.

③ How the focal work responds. Tempo returns to roughly the same token scale (measured mean 2.8 versus LLaMA-VID's 2) but raises MLVU from 33.2 to 75.6 (+42.4pp) and Video-MME from 25.9 to 67.8 (+41.9pp). Its response is not that two tokens are insufficient, but that assigning exactly two tokens to every frame is wrong. ATA gives some segments 128 tokens and others only 4, while retaining a mean of 2.8.

④ Transfer of key designs. LLaMA-VID's context token(driven by user instructions and aggregating text-relevant visual cues) is the direct ancestor of Tempo's query-conditioned memory token . The transfer is: external Q-Former query generation → placing the query directly in the SVLM causal sequence. The former requires training an additional Q-Former; the latter reuses the SVLM's own attention, making it simpler and stronger.

3.2 LongVA (Long Context Transfer from Language to Vision) — June 2024 arXiv preprint (venue not found)

① Problem addressed. LongVA takes the opposite route: if compression loses information, expand context instead. Its central idea is long-context transfer: continue training Qwen2-7B-Instruct's Text context to 224K (RoPE base raised to 1B; 900M tokens / 1000 steps), then transfer this capability zero-shot to vision without video training. UniRes represents video as one long 336×(336·N) image, with N frames = 144N tokens. V-NIAH remains near perfect at about 2000 frames (≈288K tokens), beyond the training length. The core contribution is demonstrating zero-shot cross-modal transfer of long-context capability.

② Unresolved gap. Three gaps, the first two acknowledged by the authors:

The fundamental gap: expanding context does not decide who deserves bandwidth; it passes the problem to hardware. Uniform 144 tokens/frame has the same allocation structure as LLaMA-VID's 2 tokens/frame, with a different constant.

③ How the focal work responds. Table 1 directly addresses cost-effectiveness: LongVA uses 144 tokens/frame for Video-MME 52.6; Tempo uses about 3.6 for 67.8—40× fewer tokens, 15.2pp higher score. More fundamentally, §2.5.4 finds that Tempo itself degrades when budget doubles (4K 63.68 → 8K 63.46), echoing LongVA's 128→384-frame decline. Tempo's position is that when nominal context has negative marginal returns, the answer is greater information density per token rather than more tokens.

④ Transfer of key designs. LongVA contributes less through an inherited mechanism than by providing a clean counterexample that bounds context expansion. Its V-NIAH protocol—counterfactual questions plus perplexity scoring to prevent language-prior shortcuts—also became a standard diagnostic, continued by VideoChat-Flash's 10000-frame NIAH experiment.

3.3 LongVU — October 2024 arXiv / ICML 2025 main-conference poster

① Problem addressed. First implements query-aware compression as a complete spatiotemporal pipeline. Three steps: (i) DINOv2 computes mean feature similarity in J=8-frame windows and removes frames highly redundant with neighbors, roughly halving frame count; (ii) cross-modal text guidance scores frame features through attention to the query, retaining 144 tokens/frame (12×12) for the top-N_h frames and downsampling the rest to 64 tokens/frame (8×8); (iii) STC spatial token compression prunes spatial tokens in K=8-frame sliding windows when cosine similarity to temporal neighbors is >θ=0.8, reducing tokens further by an average 40.4%. One hour of video finally fits into 8K context, at about 2 tokens/frame on average. The core contribution is establishing the value of query-dependent resolution allocation(Table 3: adaptive 67.62 versus uniform 8k@64 66.84 and 8k@144 66.28).

② Unresolved gap. The lineage's most important gap is that LongVU compression is heuristic and training-free. θ=0.8, J=8, and K=8 are manually chosen; nothing is learned from data. DINOv2 similarity measures visual redundancy rather than usefulness for the current question. Two visually distinct empty shots may both be retained despite being irrelevant to when someone tightens a screw. The authors also acknowledge that video SFT reduces image-understanding ability(Table 10), and GPU limits prevented mixed-data training.

③ How the focal work responds. Tempo replaces the three handcrafted modules with one learnable SVLM: no DINOv2 similarity threshold, no top-N_h hard selection, and no STC cosine threshold. Compression emerges entirely from L_AR the single autoregressive loss. Table 2-B quantifies learned versus handcrafted allocation: ATA exceeds uniform subsampling by 2.00pp and random allocation by 3.70pp. Tempo's four-stage curriculum, mixing images/video/text across ~7.71M samples, also directly addresses LongVU's acknowledged image-capability degradation.

④ Transfer of key designs. Two direct inheritances: (i) different token counts for different segments, from LongVU's two levels (144/64) to Tempo's continuous [4, 128] range; (ii) text-guided relevance scoring, from LongVU's cross-modal attention to Tempo's SVLM yes/no logit difference. The concrete transfer is external attention scoring → internal discriminative confidence”.

Notable author overlap: LongVU and Tempo share Jun Chen, Zechun Liu, Yunyang Xiong, Lemeng Wu, Chenchen Zhu, Raghuraman Krishnamoorthi, Vikas Chandra, Mohamed Elhoseiny, and others, and both come from Meta AI + KAUST. Tempo can be viewed as the same team's direct iteration on LongVU, making this the most reliable link in the lineage.

3.4 BIMBA — March 2025 arXiv / CVPR 2025 main-conference poster

① Problem addressed. Where LongVU uses heuristics, BIMBA introduces learned compression by inserting a Mamba selective-scan module between the visual encoder and LLM. Frame patches are flattened into a long spatiotemporal sequence; query tokens advance with the scan, and input-dependent gates decide what to write or discard. Compression becomes content-dependent rather than uniform pooling. Three key designs initialize queries through adaptive 3D average pooling of spatiotemporal tokens rather than learned embeddings; queries are interleaved among video tokens rather than appended, removing positional bias; and bidirectional scanning recovers spatial structure lost by 1D scanning. Question conditioning prepends the LLM-tokenized question: Z' = [X; Z; Q]. Compression ratio: >16× (36,864 → 2,304 tokens). The central contribution is demonstrating end-to-end learned compression with subquadratic complexity.

② Unresolved gap. BIMBA has no Limitations section, itself worth noting. Three gaps can be inferred: (i) the compressed token count M and pooling ratios are fixed hyperparameters(1×2×2 / 2×2×2 / 4×2×2 by frame-count range), not adaptive to content or question difficulty; (ii) question conditioning is optional and implemented by prepending rather than architecture, preventing one-pass reuse across questions; (iii) efficiency is shown only through curves, without absolute numbers(no FLOPs, ms, or GB). In short, it learns how to compress, but not how much.

③ How the focal work responds. Tempo addresses (i): ATA makes each segment's k_i vary continuously across [4, 128] with relevance. Uniform subsampling (61.46) in Table 2-B is conceptually a proxy for BIMBA-like fixed-ratio compression; ATA improves on it by +2.00pp. But Tempo does not address gap (iii): as critique ⑦ notes, it also provides qualitative O(1) claims without measurements. This is the only gap left unfilled across two consecutive generations in this lineage.

④ Transfer of key designs. BIMBA's component-ablation methodology is clearly inherited: its Table 1 progresses from learned queries 67.67 to average-pooling initialization 68.61, +normalization 69.85, +bidirectionality 71.68, and +interleaving 73.57. The incremental presentation parallels Tempo's five Table 2 groups. More substantively, it passes on the architectural idea of a learnable compression bottleneck between visual encoder and LLM: BIMBA inserts Mamba layers; Tempo inserts an entire 2B VLM. The transition is specialized sequence operator → general pretrained model, reflecting a broader trend over the last two years.

3.5 VideoChat-Flash — December 2024 arXiv v1 / ICLR 2026 main-conference poster (v4: 2025-07-13)

① Problem addressed. Pushes token efficiency while preserving long-context capability. HiCo (hierarchical visual token compression) has two levels: clip-level video-encoder spatiotemporal attention plus similar-token merging compresses each frame to a mean of 16 tokens; video-level progressive visual dropout during LLM inference removes about 50% in shallow layers and uses attention-guided selection deeper, for total compression of approximately 1/50. It pairs this with a four-stage short-to-long curriculum (4 frames → 8 frames → 64–512 frames → post-tuning at 448 resolution). Context expands to 128K, supporting about 10,000 frames. The core result is that single-hop NIAH retrieval reaches 99.1% at 10,000 frames(versus LongVA's 92% at 3,000 frames and LLaMA-VID's 55%), largely solving long-video retrieval.

② Unresolved gap. Its own data reveal an instructive gap: retrieval is nearly perfect, but reasoning remains far from solved. On multihop NIAVH at 10k frames (Figure 6), CAP is only 31.3% and QA only 25.4%. Finding one frame and reasoning across several are very different capabilities. Mechanistically, HiCo's clip-level compression is query-agnostic: every frame gets 16 tokens without knowing the question. Seemingly minor details crucial in combination for multihop reasoning may be discarded during compression. The authors also acknowledge that video-level compression works only at inference because it is incompatible with training accelerations such as sequence parallelism.

③ How the focal work responds. Tempo directly addresses query-agnostic clip compression by injecting the query into the innermost compression stage. Table 1 shows an advantage growing with duration (LongVideoBench −0.2pp → LVBench +4.5pp): query-aware compression helps most on extremely long videos requiring cross-segment reasoning. Tempo's compression is also shared between training and inference, unlike HiCo's inference-only video-level compression, removing that mismatch.

④ Transfer of key designs. Two inheritances: (i) the short-to-long progressive curriculum is nearly identical: VideoChat-Flash uses 4→8→64–512 frames plus high-resolution post-tuning; Tempo uses 1→8→128→384 frames, with the same four-stage structure; (ii) the demonstration that very few tokens/frame can still achieve SOTA. VideoChat-Flash matches Qwen2.5-VL with 16 versus 1924 tokens/frame, paving the conceptual and empirical way for Tempo to reduce the budget another order of magnitude to mean 2.8. The transfer is a fixed tiny budget → a lower mean budget with dynamic variation”.

4. Technical evolution

4.1 ASCII evolution tree (nonlinear, with parallel branches and convergence)

2023.11 LLaMA-VID [ECCV 2024 main conference] Extreme compression: 2 tokens/frame · Q-Former context tokens · EVA-G MLVU 33.2 · Video-MME 25.9 · 3-hour video @64K context │ │ ✗ Gap: globally constant compression; acknowledged spatial-detail loss │ ├────────────────────────┐ ▼ ▼ ┌── Route A: expand context ──┐ └── Route B: smarter compression ──┐ │ │ │ 2024.06 LongVA [arXiv] │ │ Zero-shot cross-modal transfer of long context │ 224K text context → 288K visual extrapolation │ 144 tokens/frame · V-NIAH@2000 frames │ Video-MME 52.6 @128 frames │ │ │ │ │ │ ✗ Falls to 51.8 at 384 frames │ │ ✗ KV cache 100GB │ │ │ ✗ Still uniform allocation │ │ │ │ └── Route A hits a wall┘ │ (effective context << nominal context) │ ╲ │ ╲ ▼ ╲ 2024.10 LongVU [ICML 2025 main] ╲ Query-aware, but handcrafted thresholds ╲ DINOv2 deduplication (J=8) + text-guided selection ╲ + STC (θ=0.8,K=8) → ~2 tokens/frame ╲ MLVU 65.4 · VMME 60.6 · VMME-L 59.5 ╲ │ ╲ │ ✗ Nothing is learned ╲ │ Visual redundancy ≠ query usefulness ╲ │ ╲ ┌─────────┴────────────┐ ╲ ▼ ▼ ╲ 2025.03 BIMBA 2024.12 VideoChat-Flash ╲[CVPR 2025 main] [ICLR 2026 main] ╲Learned compression Hierarchical, highly efficient ╲Mamba selective scan HiCo: clip-level 16 tokens/frame ╲Interleaved queries + inference-only video dropout ╲+ bidirectional scan 128K context · 10000 frames ╲36864→2304 (16×) Single-hop NIAH 99.1%@10k ╲MLVU 71.4 MLVU 74.7 · LVBench 48.2 ╲VMME 64.7 │ ╲ │✗ Fixed ratio M │✗ Query-agnostic clips ╲ │ Knows how, │ Multihop only 25.4% ╲│ not how much │ Video compression inference-only │ │ └────────┬─────────┘ ▼ 2026.04 ★ Tempo [ECCV 2026] ← Convergence The compressor is itself a small model that reads questions SVLM (Qwen3-VL-2B): learned compression + same-pass relevance + ATA global adaptive budget, 0.5–16 tokens/frame (mean 2.8–3.6) MLVU 75.6 · VMME 67.8 · VMME-L 57.8 · LVBench 52.7 ↑ LLaMA-VID-scale token budget, MLVU +42.4pp

4.2 The internal logic of the evolution

The driving sequence: Static constants → handcrafted rules → learned operators → pretrained models → adaptive allocation

StageWhat determines compressionRepresentative workKey turning point
1. Static compressionA global hyperparameter (2 / 144 / 16 tokens/frame)LLaMA-VID, LongVA, VideoChat-Flash—
2. Handcrafted rulesManual thresholds (θ=0.8, J=8, K=8)LongVUFirst introduction of different budgets for different segments
3. Learned operatorsAn end-to-end trained specialized module (Mamba)BIMBACompression policy becomes learned rather than hand-coded
4. Pretrained modelsAn entire pretrained VLMTempoThe compressor becomes a model rather than an operator
5. Adaptive allocationRelevance scores produced by the model itselfTempo (ATA)How much to compress also becomes a model output

Three turning points:

  1. LongVU (October 2024): from treating all frames equally to query-dependent resolutions. A shift in problem definition that first recognizes bandwidth should be uneven.
  2. BIMBA (March 2025): from handcrafted rules to end-to-end learning. A shift in methodology that makes compression policy part of a differentiable objective.
  3. Tempo (April 2026): from learning what to compress to also learning how much. A shift in output space that turns compression ratio from a hyperparameter into a model-output dimension.

Shifts in Community Attention:

A problem no generation has solved: LongVA (128→384-frame degradation), STORM (effective context far shorter than nominal), and Tempo (4K beats 8K)—three independent papers and different technical paths all encounter degradation from more visual tokens. After five generations, none directly tackles this issue. In my view, it is the field's most valuable current gap (see §6.1①).

5. Related-Work Comparison

WorkPublication dateVenue / publicationCore contributiontok/frameKey metricsRelationship to the core paper
LLaMA-VID2023.11ECCV 2024 Main conferenceExtreme 2-token/frame compression; Q-Former context tokens2MLVU 33.2 · VMME 25.9Starting point for token budgets; Tempo gains 42.4pp at a similar scale
LongVA2024.06arXiv (venue not found)Zero-shot cross-modal long-context transfer; UniRes144VMME 52.6 @128 framesCounterexample and boundary; shows context expansion hits a limit
LongVU2024.10ICML 2025 Main-conference posterHeuristic spatiotemporal adaptive compression; text-guided frame selection~2
(Adaptive 144/64)
MLVU 65.4 · VMME 60.6 · VMME-L 59.5Direct predecessor(same Meta+KAUST team, multiple shared authors); Tempo replaces handcrafted rules with learning
BIMBA2025.03CVPR 2025 Main-conference posterMamba selective-scan learned compression; interleaved queries + bidirectional scanning~36
(16× compression)
MLVU 71.4 · VMME 64.7 · NExT-QA 83.73Origin of learned compression; Tempo inherits its architectural position and adds adaptive compression amounts
VideoChat-Flash2024.12ICLR 2026 Main-conference posterHiCo hierarchical compression; short-to-long curriculum; 128K/10000 frames16MLVU 74.7 · VMME 65.3 · LVBench 48.2 · NIAH 99.1%@10kStrongest direct competitor; Tempo inherits its curriculum and addresses query-agnostic compression
STORM
(Comparison)
2025.03ICCVW 2025 (Workshop)Mamba temporal projector; train/test spatiotemporal pooling64
(25%→12.5%)
MLVU 72.9 · LVB 60.5 · Latency −65.5%Positive example of efficiency evidence; the only comparison work reporting measured latency
★ Tempo2026.04ECCV 2026SVLM compressor + same-pass relevance extraction + ATA adaptive budget0.5–16
Measured 2.8–3.6
MLVU 75.6 · VMME 67.8 · VMME-L 57.8 · LVBench 52.7Point of convergence
How to read the table: Tokens/frame trace a decline followed by differentiation: 144 (LongVA) → 64 (LongVU/STORM) → 36 (BIMBA) → 16 (VideoChat-Flash) → dynamic 0.5–16(Tempo). Meanwhile, MLVU increases monotonically: 33.2 → 56.3 → 65.4 → 71.4 → 74.7 → 75.6. These opposing trajectories summarize the subfield's last 30 months(see Figure 2).

However, the final marginal gain is already small(MLVU 74.7 → 75.6, +0.9pp), while LVBench still improves substantially (48.2 → 52.7, +4.5pp). Compression gains on moderately long videos are nearly exhausted; extremely long videos retain room for progress.

6. Open challenges and research opportunities

6.1 Theory

① What is the upper bound on effective visual-token context?(This report's highest-value, lowest-barrier gap)

This is a concrete measurement problem, not a generic call to study long context. LongVA (0.8pp degradation from 128→384 frames), Tempo (0.22pp degradation from 4K→8K), and STORM (acknowledged shorter effective context) independently observe the same effect, yet none quantitatively characterizes the turning point.

An actionable experiment: Fix the model and video set, sweeping only the injected visual-token count B ∈ {1K, 2K, 4K, 8K, 16K, 32K}. At each B, measure (a) end-to-end accuracy, (b) pure retrieval-probe accuracy such as NIAH, and (c) attention-entropy distribution over visual tokens. The hypothesis: (b) keeps improving while (a) declines beyond some B* , localizing degradation to the Inference rather than Retrieval stage. If confirmed, effective context can be defined as B* = argmax_B accuracy(B), followed by asking whether B* scales with LLM size. This valuable gap could be investigated with one model in a week.

② ATA's degeneration bound at large N

As critique ① infers, when segment count N → B_max / k_min , ATA's proportional fallback approaches uniform allocation. Concrete question: Given B_max, k_min, segment count N , and score-distribution {ŝ_i} entropy H(ŝ), can one analytically bound ATA's performance gap to hard top-K? This would directly explain the LVBench result and yield an adaptive switching rule(automatically switch to top-K when N exceeds a threshold).

③ Do compression and discrimination objectives inherently compete?

Table 2-D shows the fine-tuned SVLM is a worse router than the untuned base model (63.46 vs. 63.92). Concrete experiment: Evaluate routing AUC for Tempo's public Stage0/1/2/3 checkpoints on identical segment/query/relevance-label examples. Monotonically declining AUC would support the hypothesis that compression training harms calibration, pointing directly to a multitask-loss remedy. All four checkpoints are public, making this experiment inexpensive to start.

6.2 Engineering and Applications

④ A three-dimensional latency/memory/accuracy Pareto benchmark

This gap persists across both BIMBA and Tempo. Each provides its own qualitative efficiency claims—curves for BIMBA, O(1) wording for Tempo—preventing direct comparison. Concrete proposal: Fix hardware, such as one A100-80G, and the full LVBench dataset; measure end-to-end wall-clock time, peak memory, and accuracy for LongVU, BIMBA, VideoChat-Flash, STORM, and Tempo. In particular: are Tempo's roughly 1025 2B-model forward passes on a 4101s video actually cheaper than VideoChat-Flash's one-shot hierarchical compression? This is valuable engineering work requiring no new method.

⑤ Compression reuse in multiround dialogue

Tempo's third acknowledged limitation: every new question recompresses the entire video, costing O(rounds × video length). Concrete question: Could a two-level cache combine query-independent coarse compression with query-dependent refinement? Cache the coarse pass once, then refine only top-k candidate segments each round. Key experimental gap: How much accuracy is lost relative to Tempo's single-level approach, and after how many rounds is cost amortized?

⑥ Online / streaming settings

All five generations are offline, assuming simultaneous access to the whole video. Real embodied and video-assistant applications are streaming: the video is still arriving and future questions are unknown. Concrete question: When s_i must be chosen before future segments arrive, ATA's min-max normalization, which depends on global max(s) with min(s))fails completely. An online alternative is needed: sliding-window quantiles, or a learned absolute threshold?This is a clearly defined and currently open direction.

6.3 Emerging Directions

⑦ From one-shot compression to active agent routing

Section 6 proposes a global LLM acting as a router that requests high-resolution segments as needed. Making this concrete: Long-video understanding becomes a tool-calling problem, where the LLM's tool is zoom_in(segment_id, resolution). The missing comparison is: one-shot optimal allocation (Tempo) versus multiround adaptive retrieval (agent), under the same total token budget. This untested head-to-head could determine the subfield's next two years.

⑧ Routing post-training: SFT or RL?

Tempo acknowledges entirely zero-shot routing and proposes SFT or RL, but does not argue which is better—an explicit comparative-experiment gap. SFT requires segment/query/relevance triples, constructible from ground-truth intervals in temporal-localization datasets such as Charades-STA and QVHighlights. RL can use final-answer correctness without intermediate labels, but its signal is sparser. Compare both under matched hardware and data budgets, particularly testing whether RL learns the degenerate policy of always requesting more tokens when reward does not penalize consumption. If so, an explicit budget penalty is needed, reconnecting to effective context in §6.1①.

⑨ Joint multimodal routing with audio and subtitles

Current relevance scores use only vision and the text query. Yet Video-MME with subtitles typically gains several points: VideoChat-Flash 65.3 → 69.7, +4.4pp). Concrete question: Could subtitles/audio provide a cheap routing prior? Retrieve candidate segments through text subtitles first, then run expensive visual compression only on candidates. This could reduce the 1025 SVLM passes in §6.2④ by an order of magnitude. What should the alignment objective be: comparable audio/visual relevance scores on one scale, or independent routing followed by a union? The problem remains insufficiently defined.

7. Other recent work worth watching

Not analyzed in depth here; all are CVPR 2026 Highlights or recent high-profile preprints in Tuesday's vision/multimodality rotation.

A Mixed Diet Makes DINO An Omnivorous Vision Encoder (2026, CVPR 2026 Highlight)

A DeepMind-affiliated team (Kabra, Ovsjanikov, Hudson, Carreira, Mitra, and others) revisits the data recipe for self-supervised visual encoders. Why it matters: DINO is now a default redundancy metric across video-compression methods, including LongVU; improving its generality would propagate through the downstream chain.
CVPR 2026 Highlights

ViCA: Efficient Multimodal LLMs with Vision-Only Cross-Attention (arXiv 2602.07574)

An efficiency direction orthogonal to Tempo: change how visual tokens enter the LLM—cross-attention instead of concatenation—rather than compressing them. Why it matters: Reading this alongside Tempo separates two independent axes: reducing tokens and changing how tokens are consumed.
arXiv

Video Generation Models are General-Purpose Vision Learners (arXiv 2607.09024)

Argues that video-generation representations transfer directly to discriminative tasks. Why it matters: If true, generative pretraining could replace the entire encoder side of long-video understanding, potentially disrupting this report's full lineage.
arXiv

PersonaVLM: Long-Term Personalized Multimodal LLMs (CVPR 2026 Highlight)

Long-term personalized multimodal LLMs. Why it matters: Directly related to Tempo's need to recompress video for each dialogue turn; personalized memory and query-aware compression offer a natural intersection.
CVPR 2026 Highlights

VS-Bench: Evaluating VLMs for Strategic Abilities in Multi-Agent Environments (CVPR 2026 Oral)

Evaluation work studying VLM strategic capability in multi-agent environments. Why it matters: Reflects the community shift from retrieval to reasoning discussed in §4.2.
Project page

Perceptual-Evidence Anchored Reinforced Learning for Multimodal Reasoning (CVPR 2026)

An RL method grounding multimodal reasoning in perceptual evidence. Why it matters: Directly relevant to routing post-training in §6.3⑧: using RL to learn where to look.
CVF Open Access

Unified Generation and Self-Verification for VLMs via Advantage Decoupled Preference Optimization (CVPR 2026 Highlight)

Unified generation and self-verification. Why it matters: Its advantage-decoupling idea may relate to the competition between compression and discrimination suggested by Table 2-D (see §6.1③).
CVPR 2026 Highlights