Skip to content

Guides: which render quality to ask for (review versions take none) - #143

Merged
shinyobjectz merged 2 commits into
mainfrom
render-quality-guide
Nov 13, 2026
Merged

shinyobjectz merged 2 commits into
mainfrom
render-quality-guide

Conversation

@shinyobjectz

Copy link
Copy Markdown
Owner

Agents were rendering every review version, and every shot to be joined, at --quality master, because the guides name it for exports and say nothing about the versions in between. On one Mac that came to 38 GB of video in 1,010 files, most of it at 90 to 100 Mbit/s for 1080p.

Measured

Eight seconds of 1080p24 film footage through raea render at each setting, VMAF against the master encode:

setting bitrate VMAF mean worst frame
default (no flag) 16 Mbit/s 99.5 95.8
high 30 Mbit/s 99.7 97.4
master 87 Mbit/s reference
draft 6 Mbit/s 98.9 93.9

Flat motion graphics (the titles bench, 20 s): default 10.1 Mbit/s, high 2.5, master 11.5, VMAF 97.6 to 97.8 against master.

The footage was itself a 21 Mbit/s encode, so detail finer than that is not in the comparison; a render straight from a scene may separate the settings a little more.

What the guides say now

  • A version made for notes (a cut to review, a shot that will be joined, a preview) takes no --quality flag.
  • A film delivers at --quality high; master is for the delivered file when it is motion graphics or type.
  • When a version is replaced, delete the one before the last, and a shot's file once the joined film has it.

sdk/guides/craft/motion/rendering.md ("Which to ask for") and delivery.md. The skill's copies and its own SKILL.md and delivery.md lines are in the raea-skills PR linked below; this lands with that one and the pin, since L1's skills step compares the two.

…vers at high, master is for delivered motion graphics and type
@shinyobjectz
shinyobjectz merged commit 2bbf017 into main Nov 13, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant