Skip to content

v1.43.0

Choose a tag to compare

@myzie myzie released this 26 Oct 05:35
· 11 commits to main since this release
d266aaf

Highlights

Veo video generation now works on Vertex AI. Before this release,
google.MediaProvider.GenerateVideo always failed on Vertex with the genai
error "method Download is only supported in Gemini Developer API mode". Dive
now reads the video bytes from the operation result. It downloads the file only
on the Gemini API backend. On Vertex, a Veo 3 video has audio. Veo 2 does not
support audio, so Dive does not request it for Veo 2.

On both backends, Dive now sends media.Config.Duration, and it sends the
first image in media.Config.ReferenceImages as the start frame. Before, Veo
ignored these values. If Veo does not support the duration or the start image,
the call now returns an error. Before, it returned a video with default values.
Veo accepts whole seconds only: 4, 6, or 8 for Veo 3, and 5 to 8 for Veo 2.
Dive sends whole seconds and drops any fraction, so 4.5s is sent as 4s. Dive
does not send a duration under one second, so Veo uses its default length.

The VideoGeneration toolkit tool offers only the durations that the Veo model
accepts, and it rejects other values before it calls the provider. Other models
keep a free-text duration. Upgrade providers/google to v1.43.0 to get the
fix. No code changes are necessary.

Pull requests

  • fix(google): make Veo video work on Vertex AI (#349)

Changelog

Fixed

  • Google Veo video works on Vertex AI, with audio except on Veo 2. Gemini
    API calls now also send Duration and the first reference image (start frame);
    Veo fails on values it rejects. VideoGeneration offers only valid durations.