09 ZMongo Content Pack Add Image Sequence
Bundle an animation's frames as one sequence — ZMongo 09 Content Pack Add Image Sequence
- content_pack
- images
- content_pack
- content_pack_json
- manifest_json
- preview_markdown
- aliases
- data_types
- indexed
- success
09 Content Pack Add Image Sequence is the middle sibling in the content-pack image family - the one that stores a whole frame run as a single named field instead of a pile of numbered ones. Where Add Image gives you hero_image and Add Images gives you image00, image01, …, this node gives you one field, image_sequence, whose value is the entire ordered set. Same idea as Add Images, different shape.
Why care about the shape? Because downstream nodes that understand "a sequence" can consume it as one thing - a rehydrated animation or a frame-order-preserving asset - instead of having to reassemble a numbered pile. If you're building video/animation workflows where the frame order is the data, this is the storage mode you want. It's also a deliberate hint that ZMongo's content packs lean toward video content (the pack's example workflows are all LTXV video pipelines).
How it works
The node takes your IMAGE batch, encodes the frames (storage mode inline_base64_png_sequence - the single choice, and note the _sequence suffix vs. the plain inline_base64_png on the other two nodes), and stores them as one field under field_alias (default image_sequence). The supporting inputs:
label- default "Image Sequence".source_path- provenance, defaultload_image.images.replace_existing- default true, so re-running with new frames replaces the old sequence rather than appending.max_images- optional cap (0 = no cap, up to 4096). Watch out: no default cap means a long video batch could encode a very large pack.
Outputs are the standard pack family set: content_pack, content_pack_json, manifest_json, preview_markdown, aliases, data_types, indexed, success.
The inputs that matter
content_pack- required.images- required.field_alias- the name you'll retrieve the sequence by.max_images- set this. Default 0 (unlimited) is a footgun for long videos; a 1000-frame base64 sequence is megabytes you probably didn't mean to inline.
Install
Standard:
cd ComfyUI/custom_nodes
git clone https://github.com/CentralFloridaAttorney/ComfyUI-ZMongo
cd ComfyUI-ZMongo
pip install -r requirements.txt
or ComfyUI Manager → "ComfyUI-ZMongo" → restart. No session or downloads needed.
Troubleshooting
- Pack exploded in size - no
max_imagescap by default. Set it, or pre-downscale the frames; inline base64 on full-res frames adds up fast. success: false- a frame failed to encode. Checkpreview_markdown; batch tensors with odd shapes are the usual cause.- Only some frames present - check
max_imagesand whether your batch is actually a batch (a single 3D tensor is one frame, not a sequence). - Wrong field name later - remember the sequence lives under
field_alias, notimage00-style names.
Add Image Sequence is the choice when order matters - animation passes, video frames, anything you want to rehydrate as one ordered asset rather than reassemble by hand.
Inputs (9)
| Name | Type | Default | Description |
|---|---|---|---|
| content_pack | ZMONGO_CONTENT_PACK | — | |
| images | IMAGE | — | |
| field_alias | STRING | image_sequence | — |
| label | STRING | Image Sequence | — |
| source_path | STRING | load_image.images | — |
| storage_mode | COMBO | inline_base64_png_sequence | 1 options: inline_base64_png_sequence |
| replace_existing | BOOLEAN | true | — |
| max_imagesopt | INT | 00–4096 | — |
| refresh_tokenopt | STRING | — |
Outputs (8)
| Name | Type | Description |
|---|---|---|
| content_pack | ZMONGO_CONTENT_PACK | — |
| content_pack_json | STRING | — |
| manifest_json | STRING | — |
| preview_markdown | STRING | — |
| aliases | * | — |
| data_types | * | — |
| indexed | STRING | — |
| success | BOOLEAN | — |