Meta bypasses latent space with raw-waveform WavFlow
Meta just unveiled WavFlow, an audio model that generates 44.1kHz sound directly in raw waveform space without using a VAE. It can add synced Foley and music to silent videos, though Meta's policies mean the public repo only includes training scripts rather than the full production checkpoint.

Turning silent video into sound with AI usually follows a standard script: compress the audio into a latent space, generate the tokens cheaply, and decode it back. Meta just decided to rip up that script.
Meta unveiled WavFlow, a multimodal audio model that bypasses latent-space compression entirely. Instead of relying on a variational autoencoder (VAE) to handle intermediate representations, it generates high-fidelity 44.1kHz audio directly in raw waveform space. Think of it as the audio equivalent of generating images directly in raw pixel space.
Carving audio straight from the waveform
Raw audio signals are notoriously hard to model because of their high dimensionality and low-energy dynamics. Meta tackled this by slicing raw waveforms into 2D token grids through waveform patchify, paired with amplitude lifting to balance signal scales. From there, it uses flow matching with direct x-prediction.
Connecting video, text, and audio is a 1.03B-parameter MMDiT backbone. To get the temporal alignment right, Meta curated an automated pipeline of 5 million video-text-audio triplets.
The sync looks genuinely good on screen. Feed it silent footage of someone drumming or strumming distinct guitar chords, and the generated sound hits right on beat. On VGGSound benchmarks, WavFlow scored a 59.98 FD_PaSST, 17.40 IS_PANNs, and a 0.44 DeSync score, matching or edging past latent-based rivals like MM-Audio. On the AudioCaps text-to-audio test, it hit a 10.63 FD_PANNs.
That said, it has glaring blind spots. In piano demos, the system fell apart. It sees fingers striking keys, but it clearly does not understand which key maps to which pitch, resulting in random, out-of-tune notes.
The classic Meta release catch
There is another catch waiting in the GitHub repository. Meta published the code, setup instructions, and training scripts, but explicitly noted that organizational policies prevent them from releasing the full production checkpoint.
You essentially get an architecture framework rather than a turnkey model. Community members quickly pointed out that Meta has grown noticeably stingier with public weights across its niche research projects.
Why it matters
For video editors and game developers, automated Foley generation that does not sound muffled is a dream. WavFlow proves that you do not need latent compression to achieve crisp, synchronized sound. However, because you cannot simply download the full production weights and run them locally, its immediate practical utility remains low for day-to-day production.
For the AI research world, this is a major conceptual win. Latent space became the default because it saves compute, but it also baked in permanent information loss. We think WavFlow’s real value lies in challenging that orthodox architecture: it shows that with smart patchifying and flow matching, brute-forcing raw waveforms directly is entirely viable. Expect competitor labs to rethink whether their VAEs are truly necessary.
Sources (1)
- arxiv.org(opens in a new tab)Originalarxiv.org