Content Analyzer

Max frames is a ceiling, not a count

Setting Max frames to 28 does not mean you get 28 frames back. Two things cut it down, and both are by design:

1. The cap is 16. Anything above that is clamped server-side. The number is the node's cost bound: every frame is about 258 input tokens to the vision model, and the flat price only stays honest while the worst case is bounded. The sidebar field is bounded to 1 to 16 so the value you save is the value that runs.
2. Frames are sampled at scene changes, not on a timer. The node cuts the video at its scene boundaries and takes one frame per scene, so a video with fewer scenes than your number returns fewer frames. A 12-cut ad returns 12 frames whether you asked for 16 or 28. Short or static videos return the fewest.

So read the field as "no more than this". The images output tells you how many you actually got.

The Analysis Brief replaces the default prompt

Analysis Brief is not an extra instruction bolted onto the built-in breakdown. Whatever you type there becomes the entire prompt, and the default forensic shot-by-shot brief is dropped. Leave it blank to keep the default.

That is a feature once you know it: you can ask for the finished artifact directly instead of running the breakdown and then chaining a second LLM node to reshape it. For example:

Break this down, then output only a production-ready Seedance prompt that recreates it for my product.

One node, one charge, and the text output is already the prompt you wanted.

The All Frames output is the full array

images carries every frame the vision model looked at, as an array, and the frames also render as a gallery on the node itself. Wire it into an Image Iterator to fan out one run per frame (regenerate each frame with an image model, then animate it). The single-frame collapse other IMAGE ports do does not apply here: the array only survives on the images handle, not through json.