mexicat/pdoom-video

选用指南

AI 根据 README 整理 · 2026/10/14 14:36:31

使用方式

通过命令行使用，提供预览和渲染命令，支持多种模式如视频、静帧、联系表、性能测试和板块生成。

查看 README 依据

- `scripts/render.ts` — offline renderer (headless Chrome → raw frames over WebSocket → ffmpeg). - `out/` — renders (not in the repo). ## Requirements [bun](https://bun.sh), Google Chrome (the offline renderer drives it headless through playwright-core) and ffmpeg with libx264. The analysis tools need [uv](https://docs.astral.sh/uv/); the renderer doesn't. ## Preview ```sh cd app bun install bunx vite ``` Open http://localhost:5173 and use the keys below. `?t=23` starts at a given time. | Key | Action | |---|---| | space | play / pause | | ← / → | seek ±1 s (±5 s with shift) |

- **Other modes:** `stills`, `sheet` (contact sheets, `--cuts` for every scene boundary), `perf`, and `plates` (regenerates `public/plates/`, the stills used by the outro's rewind montage; rerun it after changing a scene). ### 4K ```sh cd app bun scripts/render.ts video --scale 2 --samples auto --shutter 0.2 --x264 aq-mode=3:rc-lookahead=30 --out ../out/pdoom-4k.mp4 ```

部署要求

需要 bun、Google Chrome（离线渲染通过 playwright-core 驱动）、ffmpeg 和 libx264；分析工具需要 uv，但渲染器不需要。

查看 README 依据

- `scripts/render.ts` — offline renderer (headless Chrome → raw frames over WebSocket → ffmpeg). - `out/` — renders (not in the repo). ## Requirements [bun](https://bun.sh), Google Chrome (the offline renderer drives it headless through playwright-core) and ffmpeg with libx264. The analysis tools need [uv](https://docs.astral.sh/uv/); the renderer doesn't. ## Preview ```sh cd app bun install bunx vite ``` Open http://localhost:5173 and use the keys below. `?t=23` starts at a given time. | Key | Action | |---|---| | space | play / pause | | ← / → | seek ±1 s (±5 s with shift) |

已知限制

渲染是 GPU 密集型的，在 M5 Pro 上整个歌曲渲染约需 57 分钟，内存峰值约 23 GB；4K 编码文件较大，默认 CRF 16 时约 670 Mbit/s。

查看 README 依据

- **Cost:** GPU-bound. A frame takes from about 40 ms (a still frame) to several seconds (the ray-marched rooms at 108–324 sub-frames). The whole song takes about 57 minutes on an M5 Pro. Memory peaks at about 23 GB: up to 6 GB for each headless Chrome, and ffmpeg at about 3.5 GB for most of the render (the shorter x264 lookahead above keeps it down) but up to 10 GB near the end.

- **Encoding:** the film grain is rendered per 4K pixel, which is expensive to encode: at the default CRF 16 the file runs at about 670 Mbit/s (13 GB for the song, 8× the 1080p file), `--crf 18` gives about 450 Mbit/s and `--crf 20` about 230 Mbit/s. - `--scale 2` works with every mode. `stills` then saves full-resolution PNGs, and `perf` measures 4K frame times. In the browser preview, add `&scale=2` to the URL. ## Regenerate the timing data The committed `data/*.json` files are all the renderer needs. Regenerating them needs the stems and intermediates, which are not in the repo: