DARASK Prompt Cell Output (CLIP Encode)

The DARASK Prompt Cell builds the combinations; this node is where they actually become images. DARASK Prompt Cell Output (CLIP Encode) is the end of the prompt chain: it takes one or more set inputs (each the product of a branch of cells), encodes them through your CLIP, and hands you CONDITIONING. Its three modes are the whole game - batch everything, iterate one at a time, or grab a single index for debugging.

The three modes

• All as Batch (default) - stacks every pattern into one CONDITIONING batch and reports total_count. Wire that to your empty latent's batch_size (convert the widget to an input first) and one queue press generates every image. This is the "all combinations in one pass" workflow.
• Iterate (auto-advance) - one prompt per queue, cursor advances internally. Important, not a bug: a single Queue press produces exactly one image. To run the whole set you must turn on Auto Queue (instant) in the queue panel. This is the low-VRAM path.
• Index - renders one specific pattern by index. For A/B comparisons and debugging a specific prompt.

The set inputs are dynamic like prev on the cells - connect a leaf cell, an empty slot appears, up to 16. This is the sanctioned place to merge branches: the output node just unions what it receives, so each branch's patterns stay independent instead of cross-multiplying. total_count reflects the sum across all connected leaves.

Outputs

conditioning - into your sampler's positive (or negative, with a second node). current_prompt - the prompt being rendered right now, handy for a Show Text log. current_index and total_count - progress bookkeeping; total_count is also the number you wire to batch size.

Install and the one-socket rule

Pack install: Manager → search DARASK → install, restart. Needs a clip input from your text-encoder loader. Nothing else to fetch.

The cluster of beginner mistakes here, from the README's own troubleshooting: leaving batch_size at 1 in All as Batch mode (the sampler just repeats the first prompt), forgetting Auto Queue in Iterate mode, and wondering why total_count isn't visible - it's an output socket, not a widget, so connect it somewhere to see it. Also remember the cursor state persists per node ID, so editing the workflow lightly won't reset your position; reset = true forces it back to zero.