In this analysis
Matching endpoint images does not uniquely specify the motion or invariants of the intervening shot.
Endpoint control left the path open
The October 15, 2025 Veo and Flow update provided earlier video-control context. Google I/O on May 19, 2026 preceded Omni 1.1’s August 27 release, which introduced first-and-last-frame interpolation. Specifying endpoints constrains where a shot starts and finishes. It does not uniquely determine how the shot gets there. Several visually plausible trajectories can connect the same images while telling different stories, changing object relationships or introducing motion that the creator did not intend.
Camera motion and object motion can be confused
An illustrative starting frame shows a product from the front and the ending frame shows its side. The transition could involve the camera moving around a stationary product or the product rotating before a stationary camera. The endpoints alone do not settle the choice. Lighting and background cues may make one interpretation more plausible, but a task requiring a particular movement should state it. This is a creative specification issue, not a reported model failure. It explains why matching endpoint images can coexist with an unacceptable intermediate sequence.
A trajectory has constraints between the anchors
A continuous shot may need to avoid a cut, preserve the object’s shape and maintain the relationship between foreground and background. These conditions apply throughout the transition, not just at its first and last images. A brief intermediate distortion can violate the task even when the endpoints match beautifully. Review should therefore sample the meaningful motion and inspect the whole sequence at playback. The appropriate scrutiny follows the intended use rather than an invented universal quality score or a promise that every interpolated frame remains physically exact.
A trajectory-choice fixture
A practical illustrative test supplies the same endpoint pair with an explicit instruction for camera motion. A contrasting version requests object rotation. Review whether the generated path reflects the distinction while preserving the stated invariants. No actual video or measured success rate is claimed here. The fixture separates adherence to the requested trajectory from endpoint resemblance, providing a concrete way to diagnose whether a disappointing result arose from ambiguous direction, an incorrect motion interpretation or a continuity defect between otherwise valid anchors.
Strong anchors still need direction
The August release gives creators a useful control surface, but control over endpoints is different from complete control over the transition. The retrospective lesson is to express the missing path constraints and evaluate them directly. A creator can leave some motion open intentionally; that is a valid creative choice. Problems arise when an unspecified degree of freedom is later treated as a broken guarantee. Naming which movement and invariants matter makes the workflow more reviewable without requiring every frame to be manually described.