Rendering — FAQ & troubleshooting — VidVertex Docs

Rendering

A render fails immediately. Check the job log in the hub — the last lines name the cause. The usual suspects: the main content file was moved/renamed (re-assign it), or a widget points at a deleted asset.

The render ended with "N variants failed". The finished variants are on disk; the failed ones are named in the log with their reason. Fix the cause and render again — only the missing variants are rendered.

"Already being rendered by …". Only one render per stack runs at a time — two would overwrite each other's files. Wait for the other render to finish, or cancel it where it runs. If the message names a process that is long gone, it clears itself within two minutes.

The message says Who is rendering
the VidVertex app this window's render queue
the assembly line an assembly-line run
an assistant (MCP) Claude, Codex or another MCP client
the command line a render started from the CLI
the watch folder a job spec the watcher picked up

Renders are slow. Hardware encoding needs a supported NVIDIA card and a current driver — Settings → Render settings shows which encoder is active and why. Resolution and length dominate the rest. The hub renders one stack after the other on purpose; across processes the rule is one render per stack, so an assistant and the hub can work on different stacks at once.

Renders come out quiet. Current versions normalize the finished mix to −14 LUFS, the level TikTok, Instagram and YouTube play at (stack editor → Sound tab → Loudness, on by default). Files rendered by an older version are roughly 6 dB quieter and are deliberately not marked stale — re-render a stack to bring it up.

TIP

Render preview in the editor header runs one variant through the whole pipeline at reduced resolution — captions, hook, endcard, ducking, loudness. It is the accurate check before a batch; the live canvas approximates.

The hub says "stale" but I didn't change the video. Something render-relevant changed — layout, assets, captions, hook, zones, order, the audio settings. Post texts (titles/descriptions/comments/hashtags) and the cover frame deliberately do not mark renders stale.

The hook is in the render but not on the canvas. Hook lines live in up to three places: the per-language pools, the Hook tab's list, and — when an assistant wrote them — per brand on the hook widget itself. Current versions resolve all three, so the canvas and the voiceover preview show the line the selected brand renders, and the Hook tab names the case.

WARNING

An empty Hook tab list next to renders that carry text is the per-brand case. A line typed there replaces every brand's own.

The editor says "changed outside the app". Something else wrote the stack while you had unsaved edits — an assistant, the assembly line, a sync tool. Your edits are kept; choose load external or keep mine.