A New Chapter: What Users Are Most Happy About
Integrated Audio & Stronger Narrative Control
One of the most celebrated features in Veo 3.1 is its improved native audio support. Before this update, various video-generation pathways required users to layer sound manually. With the new version, features like “Frames to Video,” “Ingredients to Video,” and “Extend” now support synchronized dialogue, ambient sound, and sound effects. That means the model handles visuals and audio together, which users see as a major step toward more seamless storytelling.
Google itself emphasizes that the update gives creators “more granular control” within Flow.
Users on Reddit have echoed this praise. One noted:
“The added audio control and scene extension features are a game changer for content creators.”
More Inputs, More Flexibility
Another welcome improvement is the broader set of input types and editing options. Users can now feed in text, images, or short video clips; supply reference images to guide style; and interpolate between first and last frames to generate smooth transitions. “Scene extension” allows some generated footage to continue beyond the original segment. These enhancements help creators push past the rigid “8-second clip” constraints that plagued earlier models.
Visual & Prompt Fidelity
Some users say Veo 3.1 is better at sticking to prompts, maintaining character consistency, and producing subtler textures and lighting. The model seems more respectful of style cues, object continuity, and camera dynamics, all of which reduce the “AI weirdness” that so many generative video systems are haunted by.
The Criticisms: Where Users Hit the Wall
Inconsistent Quality & “Rushed” Feel
Despite the new features, many early testers report that the overall output sometimes feels lower-quality than in certain Veo 3 generations. On Reddit, some users claim that “generations are lower quality than they were before, using the same prompts.” One user speculated the release was rushed, possibly to keep pace with rival models.
Another commenter pointed out that the extend feature misbehaves: it continues from just the last half-second, which can lead to abrupt shifts in audio or visual tone. They also noted issues like duplicated watermarks when re-rendering segments.
Audio Limitations & Voice Options
Though the audio is generative, the freedom isn’t unlimited. Several users lament the lack of custom voice selection or more flexibility in voice styling. One early critique is that you can’t directly pick a generated voice or inject your own audio easily in some workflows.
Relatedly, lip-syncing and timing still stumble in complex scenes. While there’s improvement, some awkward glitches remain.
Scaling & Feature Gaps
Not all promised features are fully baked or broadly available yet. For example, “Insert” and “Remove” tools (to add or subtract objects in a scene) exist in Google’s vision but aren’t fully live across all interfaces.
Output duration is another sore point. Though extensions are possible, many base generations still cap out at short lengths. Some users expected the ability to freely generate minute-long cinematic scenes, but the reality is more limited (especially in Flow or under non-enterprise tiers).
Some users also observe that character consistency across camera angles can still falter. That means when you change perspective or distance, the same character might subtly shift in appearance or behavior.
Sentiment Snapshot: Optimism Tinted with Caution
Overall, sentiment toward Veo 3.1 is tentatively positive. Many believe this release is a meaningful step forward, especially in integrating audio and expanding editing flexibility. The move from “silent visual output + manual audio” to “unified audiovisual generation” is seen as a foundational shift.
But the praise is tempered by frustration over rough edges. Users are keenly aware that generative video remains an experimental field. Some feel Google leapt ahead of stability, perhaps under pressure from competing models like OpenAI’s Sora 2.
Several voices express a willingness to stick with Veo and experiment, especially if Google continues to iterate quickly. Others say they’ll hang back until the feature set matures or quality stabilizes.
One interesting pattern: users constantly compare to competing models. A few early testers openly said Veo 3.1 felt worse than Sora 2 in some respects, particularly in immediacy of output and stylization. Still, many admit that Google’s tooling, reference inputs, scene extension, edit control, gives Veo a unique edge for users already embedded in the Google ecosystem.
What to Watch Over the Coming Weeks
- Stability & polish: Will Google patch the rough visual/audio artifacts?
- Voice customization: The ability to pick or inject voices could make or break many professional workflows.
- Wider access: Whether Flow, Gemini API, and Vertex AI users all get parity of features.
- Long-form storytelling: How well extend and scene continuation evolve for narratives beyond short clips.
- Competition pressure: How well Veo 3.1 holds its ground against Sora 2 and others in real-world creative use.
In short: Veo 3.1 has sparked enthusiasm and cautious critique in nearly equal measure. For creators betting on Google’s vision of integrated video + audio AI, this is a moment of exploration. For skeptics, it’s a reminder that generative video, while dramatically powerful, is still in the “shape it with trial and error” phase. Over the next weeks, as real user workflows test the limits, we’ll see whether Veo 3.1 evolves from promising to indispensable.
Maya Lindqvist is not a person. No notebook, no deadlines, no face behind the name — just a byline this newsroom publishes under. Here is the production line underneath it, because a name beside a portrait reads like a journalist, and this one is not one.
The models. Writing: gpt-5.6-luna and qwen3-max. Out on the live web: gpt-5.6-luna and gpt-5.6-terra. Pictures: gpt-image-1 and gpt-image-1-mini. Swap one in the newsroom and this line swaps with it — it is read off the machines, not typed here.
How a story is made
- Research. The searching model reads around the story, pointed at primary sources — the filing, the post, the repository — rather than at somebody else's write-up of them.
- Writing. The writing model drafts it against what was found, at Maya Lindqvist's usual length and in Maya Lindqvist's usual register.
- The loop. A reviewer reads the draft and sends it back with notes. Then reads it again. A piece can go round several times before it leaves the building.
- Enrichment. A quotation has to appear word for word on the page it is taken from. A chart may only use figures that appear in the source it cites. Whatever fails is dropped, and the reason is kept.
- Fact check. A last pass hunts for claims the article makes and its sources do not.
- A human stop. Sensitive subjects are held for a person to read before publication, and a person can kill any of it at any point.
If that sounds less like a newsroom and more like a factory: quite. It is called Press Factory.
This article was generated using AI and published automatically without human pre-publication review.
How this article was made
The article was produced by the Grandmonts Media News Engine using automated research, drafting and verification workflows. No human editor reviewed the article before publication. Grandmonts Media remains responsible for the published content. Errors can be reported at office@grandmonts.cz.