VideoGenReview

What each AI video model's release notes say changed

Terse logs and wordy posts

Makers write notes for different readers. PixVerse's API changelog is a table of one-liners, V5.5 released or Upscale feature released, and says nothing about behaviour. Luma writes a post per change, with a stated purpose and examples. Kling's API log sits between, one heading with a few lines of parameters. From 3 source pages, read 2026-09-25 to 2026-10-25; no maker pays to be listed.

Where this note's examples come fromThe examples in this note come from 4 entries across 3 model lines.ExamplesKling AI1 entryLuma Ray1 entryPixVerse2 entries
Fig. 1 Each example links to its line page.

A terse log is easy to date and hard to interpret; a wordy post is the reverse. The register keeps each entry's value to what the note states, so a one-line note gives a one-line entry.

The style also shapes the counts. A maker that logs every parameter change, as Kling does in its API updates, collects many entries for small steps; a maker that posts once per model, as MiniMax does, collects few entries for large ones. Neither count is a measure of how much the model improved.

The entries this note draws on, read 2026-09-25.
DateLineVersionWhat changed
2 June 2025Luma RayNot named in the noteModify Video keeps a performance and changes the world around it
2 December 2025PixVersePixVerse V5.5V5.5 is released
15 December 2025Kling AIKling 2.6Kling 2.6 launches with a switch for generating sound
16 June 2026PixVerseNot named in the noteUpscale is released

Inclusion rule. Entries used as examples in this note. Order. By date, oldest first; undated rows last.

1In the notes

With Modify Video, you can keep what matters and evolve everything else.

Luma, Modify Video post

Released V5.5.

PixVerse, API changelog

Control whether to include audio when generating videos through the sound parameter.

Kling AI, API updates

Added the Video Upscale endpoint.

PixVerse, API changelog

2A pipeline on current models

Release notes such as “Terse logs and wordy posts” matter once a pipeline runs the models; SceneMixer's guides describe how it does:

Dubbing replaces the audio of a finished clip; the picture was generated for a different line, so mouth shapes, pauses and shot length all belong to the original language. Native-language generation gives the video model the line in the target language before it renders the shot, so the performance, the pacing and the cut points are built for that language.

SceneMixer, Native-Language Dialogue vs. Dubbing in AI Video (2026): Why the Cast Should Speak the Line (read 2026-10-13)

SceneMixer writes dialogue into the script analysis, assigns each line to a shot with a speaker and a short delivery note, and the video model performs it — picture and audio generated together, so the mouth forms that sentence in the language you chose.

SceneMixer, AI Dialogue Generator (read 2026-10-13)

3Other reading notes

4Notes read