WHAT NEW IN X11.06 FRI

X 上的 AI 合集档案 · 23 个合集 · 70,791 条

opus-5.5VIDEO

用 Opus 5.5 逐帧渲染 720 帧无缝循环动画

有开发者称 Opus 5.5 无法直接导出视频文件,于是把这一缺口变成方法:固定画布、按帧号调用 draw(f)、ffmpeg 编码,720 帧 12 秒循环每帧可复现。

Karmi
@0xKarmi27 天前收录原推发布于 2026.10.09
Karmi @0xKarmi原推发布于 2026.10.09
在 X 上打开原推

Picture a butterfly with no memory of its last wingbeat. Ask it for frame 720 and you get frame 0, pixel for pixel. 720 frames. 12 seconds. 6 counters. All at 0. Opus 5.5 can't hand over a video file, one builder says. He made that gap the method. > STAGE - one fixed 1000x1080 canvas, fonts baked in > RENDER - a windowless engine calls draw(f) once per frame number > ENCODE - ffmpeg writes H.264, pixel aspect ratio declared > CHECK - three passes after every build By his account the model writes only the first, a drawing program. The other three get reused. Each picture depends on its number alone: no clock, no timer, no dice that land differently each run. So any frame renders the same every time. A fix is a small edit and a re-render. The sample loop is 720 pictures in 12 seconds. A hand animator at 12 drawings a second would need 144. The smoke test plays one loop unseen and counts six kinds of defect, from script errors to text on text. Six yes/no gates before a human looks. The seam check puts frame 0 against frame 720. One changed pixel means some motion isn't periodic. He reports a last render of 1,820 frames with six zeros. At the sample's 60 fps that would be about half a minute. Let one frame read a clock and the same number stops giving the same picture. We drew the rule as an X-ray butterfly, its wingbeat computed from the frame number ↓

这条是引用着另一条写的:x.com/0xkarmi/status/2108207473379180586

x.com/0xkarmi/status/2108495927988129839采集于 2026.10.10 10:14