Roblox's PixVid Drops the VAE to Hit 960p at Nearly 480p Cost
PixVid skips the VAE and renders video directly in pixel space, enabling 960p generation at 480p cost and 34ms control-to-screen latency.
- PixVid lifts Wan2.1-14B into pixel space by swapping the VAE for a causal convolutional head.
- Beats latent baseline on VBench (84.78 vs 84.05) after 1.3M clips of finetuning.
- Control-to-screen latency drops from 495 ms to 34 ms at 29.4 FPS on one B200.
- Generates 960p video at the same token count as 480p by doubling patch size.
- Keeps 98% of source motion in depth-conditioned editing versus 83% for latent models.
- Code release pending internal review; paper on arXiv.
Video generators including Sora, Veo, Wan, and Cosmos typically compress clips with a variational autoencoder (VAE) before processing them with a diffusion model. Researchers at Roblox and UC Merced have introduced PixVid, which removes the VAE from the generation path and converts a pretrained latent video model into a pixel-space generator. The change targets three limits of compressed video: resolution costs, coarse temporal control, and motion artifacts during editing.
Starting from Wan2.1-14B, PixVid reached quality comparable to the original model after 20,000 fine-tuning iterations. It generates 960p video with the same transformer token count used for 480p, preserves fast motion during controlled editing, and can reflect user input in the next rendered frame.
Compression now gets in the way
A video VAE compresses pixels into a smaller grid of latent values, often combining four consecutive frames into one temporal block. A diffusion transformer, or DiT, then denoises that compact grid. The compression made large-scale video training practical because the transformer processes far fewer tokens.
Spatial and temporal compression also constrain later stages of the pipeline. Doubling both output dimensions produces four times as many latent tokens at a fixed compression ratio. Frame-level conditions such as depth, pose, or user input must pass through shared temporal blocks. At 30 frames per second, a four-frame block spans 133 milliseconds before inference and system overhead are counted. Fast objects can occupy several positions inside that interval, producing blur or distorted motion.
This story is for Pro members
You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.