From Tokens to Faces: Investigating Discrete Speech Representations for 3D Facial Animation
This paper evaluates four families of discrete speech representations for 3D facial animation, demonstrating that encoding phonetic classes yields accurate predictions and enabling the introduction of an Audio Visual Text-to-Speech (AVTTS) pipeline that utilizes shared discrete representations to simultaneously decode speech and 3D facial motion.
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
Imagine you are trying to teach a robot how to talk and move its face at the same time. You have the robot's voice, but how do you tell its face what to do? Do you give it a detailed script of every muscle movement? Do you give it a raw audio file? Or do you give it a set of simple, coded instructions?
This paper, titled "From Tokens to Faces," is essentially a taste test. The researchers wanted to find out which type of "instruction code" works best for making a 3D animated face look natural when it speaks.
The Four Types of "Instruction Codes"
The researchers tested four different ways to translate human speech into data (called "representations") that a computer can understand:
- The "Semantic" Code (HuBERT): Think of this like a translator who understands the meaning of the sentence. It knows what words are being said and the context around them. It's great at understanding the "idea" of the speech.
- The "Acoustic" Code (WavTokenizer): This is like a high-speed audio compressor. It focuses purely on the sound waves and how they feel, ignoring the meaning or the specific letters. It's very efficient at recreating the sound, but it doesn't really "know" about words.
- The "Hybrid" Code (SpeechTokenizer): This is a mix of the two. It tries to understand both the meaning of the words and the texture of the sound at the same time.
- The "Label-Based" Code (CosyVoice2): This is like a strict teacher using a checklist. It breaks speech down into specific, discrete labels (like specific letters or sounds) and focuses on the structure of the language rather than the fluid sound.
The Experiment: The Face Decoder
The researchers took these four different codes and fed them into two different "face drivers" (decoders):
- The GRU: A step-by-step driver that looks at one frame of the face at a time.
- The Transformer: A driver that looks at the whole sentence at once, like reading a paragraph to understand the flow.
They then measured how well the resulting animated faces matched the real human faces using three methods:
- Math: Measuring the distance between the robot's lips and the human's lips.
- Smoothness: Checking if the face was jittery or moving smoothly.
- The "Human Eye" Test: They had real people watch the videos and rate how realistic they looked, similar to a blind taste test.
What They Found
Here are the surprising results, explained simply:
- Meaning Matters: The "Semantic" code (the translator) and the "Label-Based" code (the checklist) were the winners. They produced the most realistic faces. It turns out that for a face to move naturally, it needs to know what is being said (the phonetic classes), not just how the sound waves vibrate.
- Too Much Sound is Bad: The "Acoustic" code (pure sound) and the "Hybrid" code (sound + meaning) performed poorly. It seems that if the computer is too focused on the raw sound details, it gets confused about how to move the lips. The "noise" of the sound actually got in the way of the facial animation.
- The Best Driver: The "Transformer" driver (the one that looks at the whole sentence) worked much better with the discrete codes than the step-by-step driver.
- The "Label-Based" Surprise: The "Label-Based" code, which was originally designed for text-to-speech, worked almost as well as the complex "Semantic" code. This is a big deal because it's simpler and more structured.
The Big Idea: The "All-in-One" Machine
The most exciting part of the paper is a new idea they call AVTTS (Audio Visual Text-to-Speech).
Usually, to make a talking head, you have to do it in two steps:
- Turn text into audio.
- Turn that audio into a moving face.
The researchers showed that because the "Label-Based" code is so good at representing speech, you can use it as a shared language. You can feed text into the system, and it can spit out both the audio and the moving face at the exact same time, perfectly synchronized, without needing a middle step. It's like a conductor who can direct both the orchestra (the voice) and the dancers (the face) from a single sheet of music.
The Bottom Line
To make a robot face look real, you don't need to feed it every tiny detail of the sound wave. You need to feed it a clear, structured understanding of the sounds and letters being spoken. If you give the computer a clear "map" of the speech (like a checklist of sounds), it can figure out how to move the lips perfectly, even if it doesn't have the raw audio file to start with.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.