← Latest papers
💻 computer science

TempAct: Advancing Temporal Plausibility in Autoregressive Video Generation via Planner-Executor RL

TempAct introduces a planner-executor reinforcement learning framework that leverages hierarchical group exploration and tailored rewards to optimize temporal decomposition and step-conditioned execution, thereby resolving ambiguity and error propagation in autoregressive video generation while ensuring temporal plausibility and visual quality.

Original authors: Jing Wang, Xiangxin Zhou, Jiajun Liang, Kaiqi Liu, Wanyuan Pang, Zhenyu Xie, Tianyu Pang, Xiaodan Liang

Published 2026-07-03
📖 5 min read🧠 Deep dive

Original authors: Jing Wang, Xiangxin Zhou, Jiajun Liang, Kaiqi Liu, Wanyuan Pang, Zhenyu Xie, Tianyu Pang, Xiaodan Liang

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The Big Problem: The "Confused Dog"

Imagine you are asking a video generator to make a clip of a dog. You give it one single instruction: "The dog sits, then pounces on a ball, then brings it back."

In current video AI systems (specifically "Autoregressive" ones), the AI tries to build the video frame-by-frame (or chunk-by-chunk). The problem is that it gets temporal confusion. It hears the whole instruction at once but doesn't know when to do each part.

  • The Result: The AI might show the dog sitting while it's already holding the ball, or it might start running before it even sits. It's like a movie where the scenes are all jumbled together. The AI knows the story, but it can't keep the timeline straight.

The Old Fixes (And Why They Failed)

  1. The "One Prompt" Approach: You just tell the AI the whole story once. Result: The AI gets confused about the order of events.
  2. The "Step-by-Step" Approach: You try to tell the AI, "Now do step 1," then "Now do step 2." Result: The AI gets stuck. When you switch from "Step 1" to "Step 2," the AI often forgets the previous context, blends the two actions together (e.g., the dog is half-sitting and half-pouncing), or carries errors from the first step into the second.

The paper argues that simply training the AI on more examples (Supervised Fine-Tuning) doesn't work because the AI learns to copy the teacher, not to understand how to switch gears correctly when the story changes.

The Solution: TempAct (The Director and the Actor)

The authors propose TempAct, which treats video generation like a theater production with two distinct roles working together:

1. The Planner (The Director)

Think of this as an LLM (Large Language Model) acting as a Director.

  • Job: Before the video starts, the Director reads your big instruction and breaks it down into a script. It decides exactly when the dog should sit, when it should pounce, and when it should return.
  • The Twist: Instead of just writing one script, the Director writes several different versions of the script (e.g., "Maybe the dog sits for 3 seconds, or maybe 5?"). It explores different ways to break the story down.

2. The Executor (The Actor)

Think of this as the Video Model acting as the Actor.

  • Job: The Actor takes the Director's script and actually performs the scene. It generates the video chunks based on the specific "step" it is currently on.
  • The Challenge: The Actor has to switch from "Sitting mode" to "Pouncing mode" instantly without stumbling or forgetting what it was doing.

How They Learn Together: The "Group Tryout"

This is the core innovation. Instead of just one Director and one Actor trying once, TempAct uses a hierarchical group exploration strategy. It's like a massive audition process:

  1. The Planning Group: The Director generates 4 different scripts (plans) for the same story.
  2. The Execution Group: For each of those 4 scripts, the Actor tries to perform it 8 different times.
    • Scenario: The Director says, "Let's try Script A." The Actor tries to act it out 8 times. Then, the Director says, "Let's try Script B." The Actor tries that 8 times.

The Scoring System (The Judges)

After the auditions, a "Judge" (another AI) scores them to decide who gets the job. The scoring happens on two levels:

  • For the Director (The Planner):

    • Did the script make sense? (Plan Quality)
    • Did the final video actually follow the story order? (Temporal Consistency)
    • Reward: If a specific script leads to a video where the dog actually sits before pouncing, the Director gets a high score for that script.
  • For the Actor (The Executor):

    • Did you switch smoothly? (Step-Following)
    • Did you look good while switching? (Aesthetic Quality)
    • Reward: If the Actor switches from "sitting" to "pouncing" without blurring the image or making the dog look weird, the Actor gets a high score.

The "Credit Assignment" Analogy

Imagine a relay race.

  • Old Way: If the team loses, everyone is blamed equally.
  • TempAct Way:
    • If the Director gave a confusing map, the Director is penalized, even if the runner (Actor) ran fast.
    • If the Director gave a perfect map, but the Actor tripped at the exact moment of the handoff (the prompt switch), the Actor is penalized.
    • This allows the system to learn exactly what went wrong: Was the story broken, or was the performance messy?

The Result

By training both the Director and the Actor together using this "try many, score many" method, TempAct creates videos where the events happen in the correct order.

  • Before: The dog might be holding the ball while sitting.
  • After (with TempAct): The dog sits, then drops the ball, then pounces. The timeline is logical, and the visual quality remains high.

In short: TempAct fixes video AI by adding a "Director" to plan the timeline and a "Coach" to train the "Actor" on how to switch scenes smoothly, using a massive group audition system to figure out the best way to tell the story.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →