Back to Feed
Multimodal / Benchmarks & Evals

Benchmarking Real Time Omni Modal Assistants

Original: OmniAssistBench: Assistant-style Interaction Benchmark for Omni-LLMs

Listen to the summary

Uses a voice available on your device

Audio options
On this page 4 sections
Related concepts 2 concepts

Key Takeaways

  • OmniAssistBench provides a standardized way to test assistant-style interactions that involve dynamic video inputs.
  • The evaluation framework ranks models on a 100-point scale based on perception and goal-oriented task performance.
  • Gemini-3-Pro leads current results with a score of 66.4, while Qwen3-Omni-Instruct follows at 51.2.
  • Current models frequently struggle with context retention and responding to specific timing events in video streams.

Summary & Methodology Analysis

The researchers developed OmniAssistBench to address the difficulty of evaluating large language models that process video and audio in real time. Standard static datasets often fail to capture how a model response influences future user behavior. To solve this, the authors created a pipeline that filters video content to ensure suitability for assistant interaction, logically deduces user goals, and segments these into multi-turn clips. These clips are then processed by the model, which must handle inputs provided via text-to-speech and subtitles to mimic a live assistant environment. The evaluation uses an automated judge to score responses against a 5-point rubric that penalizes hallucinations and redundant information across two tiers: perception and goal-oriented tasks. Performance is summarized by a total score out of 100 points, where the proprietary Gemini-3-Pro achieves 66.4 and the open-source Qwen3-Omni-Instruct achieves 51.2. The evaluation reveals significant bottlenecks in how these models process transient information. Specifically, models often fail to delay their output until a target event occurs, which is a critical requirement for synchronizing actions with video timestamps. Furthermore, they struggle to interpret visual prompts such as hand gestures, which suggests a gap in fine-grained perception for interactive agents. A major limitation is the loss of cross-turn context, where models forget the user goal when new visual stimuli appear in subsequent turns. This tendency to drift suggests that while these models can process multimodal data, they lack the robust state management required for long-running, goal-directed assistance.

Interactive System Flowchart

Click diagram to expand and zoom

Cross-Examination & FAQs

A deeper dive clarifying mechanics, constraints, and baseline evaluations.

Q1. What is OmniAssistBench?

It is a new benchmark designed to evaluate how multimodal language models perform in real-time, assistant-style interactions using video content.

Q2. Why is evaluating these models difficult?

Standard static datasets cannot handle the diverging interaction paths that occur when a model response dynamically changes the subsequent behavior of the user.

Q3. How do the leading models compare on this benchmark?

Gemini-3-Pro achieved a score of 66.4, while Qwen3-Omni-Instruct achieved 51.2 out of a maximum of 100 points.

Q4. What specific visual tasks do the models struggle with?

Models currently struggle with interpreting visual prompts such as hand gestures.

Q5. How does the evaluation framework handle multi-turn interactions?

It segments source videos into multi-turn clips and assesses the model ability to maintain historical context throughout the sequence.

Q6. What is the primary cause of context loss in these models?

Models tend to lose cross-turn context when they are distracted by new visual inputs in later parts of the interaction.

Q7. Are there issues with response timing?

Yes, models often fail to delay their responses until a specific target event occurs within the video.

Q8. What is the scoring methodology used by the benchmark?

The paper uses an LLM-based automated judge to assign a score based on a 5-point rubric that penalizes hallucinations and redundant information.

Q9. What is the computational overhead of the benchmarking process?

The paper does not specify the computational overhead or requirements for running the evaluation.

Flag an issue

What is wrong with this summary?

What is wrong?