🌱 Seedance 2.0 Batch JSON Viewer

Every generation node in this pack has a batch_count control that can spawn up to ten tasks at once, and every one of them returns a batch_json output summarizing the whole run. Seedance 2.0 Batch JSON Viewer is the small utility that sits between those two things: it takes that raw batch_json string, shows you a readable summary of what actually happened, and hands the data onward in a typed form that the batch result browser will accept.

It exists because of a deliberate design decision in the pack: Seedance 2.0 Batch Result Browser refuses to accept a generation node's batch_json directly - the tooltip is explicit that "Direct generator batch_json links are intentionally blocked." You have to route through this viewer first. The reason is stability. A generation node's batch_json changes on every re-run as new tasks are submitted, which would make a selection-based browser impossible to keep in sync. Freezing the JSON through this node means the data you're browsing is a stable snapshot, not a moving target.

How it works

Connect a generation node's batch_json output to the viewer's batch_json input and run it. If it's valid, the node parses the batch and displays a summary - label, number of items, per-item status. If it's malformed or empty you get a message telling you to connect a generation node and run the viewer first.

The node's output is batch_json, but with a twist: it's the typed SEEDANCE2_BATCH_JSON connection type, not a plain string. That type is what the Batch Result Browser's input expects. So the workflow is:

Seedance 2.0 Text-to-Video batch_json → Seedance 2.0 Batch JSON Viewer
Seedance 2.0 Batch JSON Viewer batch_json → Seedance 2.0 Batch Result Browser

Run the viewer once to freeze the snapshot, then browse freely. It's an output node with no return value beyond the typed passthrough, so it's pure plumbing - but it's the plumbing that makes batch browsing reliable.

Why you'd bother

Because batch browsing is the difference between paying for re-renders and not. When batch_count is 4 and you want to compare which of the four seeds produced the keeper, the browser lets you page through the results and pull out the winning video_url without resubmitting anything. Without this viewer as the stable middle step, that whole flow doesn't exist.

One honest note: it's a utility, not a feature. It earns its place in a batch workflow and is dead weight in a single-render one. Don't add it just because it's there - add it when you're about to browse a multi-task run.

Install: ComfyUI Manager → Install via Git URL → https://github.com/nnnnkatsu/seedance2-comfyui-byteplus, restart. No extra dependencies, no GPU, no cost - it doesn't touch the API at all.