reelflow review · baseline-20261007-210059 · workflow a89d6d9cc714

Reference render — main

main @ 70b62bd — These are the reels every workflow change is compared against.

Render time
44 s
CPU
735 s
Avg cores
16.7
Speed
65.2 fps
Peak memory
4.96 GB

Golden reels

01_fiction_platforms

Reference render
main
Length25.2 s
Render time28 s
CPU141 s
Cores used5.1
File size16.4 MB

02_retcon

Reference render
main
Length35.2 s
Render time39 s
CPU267 s
Cores used6.8
File size21.0 MB

09_burn_bridges

Reference render
main
Length28.8 s
Render time33 s
CPU190 s
Cores used5.8
File size12.1 MB

10_infosys

Reference render
main
Length25.4 s
Render time16 s
CPU137 s
Cores used8.5
File size16.5 MB

How to approve

Watch the reels above. Happy? Approve and merge the pull request — the change is on main. Then run reelflow baseline on main so these become the reels the next change is compared to. Not happy? Leave a comment on the pull request; nothing reaches main until it's merged.

How reels are judged. Timing is checked exactly, from every word's position on the reel's timeline. The picture score is SSIM with film grain blurred out — "looks the same" is ≥ 0.99; the same code rendered twice scores 0.9994, a visible grade nudge 0.9886. "Fine detail" is plain SSIM and only informational: grain re-encoded with different encoder settings drops it to ~0.985 with no visible difference. ffmpeg's text overlay can also land a cut one frame early or late from run to run (it did before reelflow too), so a couple of frames at cuts may differ in any comparison.