Skip to main content
k2k audio logo k2k audio

Back to Slicing
Documentation tree

Slices Parser

Slices Parser is the "fan-out" node of the slicing workflow: it takes a SliceContainer and exposes each slice as its own ComplexBuffer output port, so you can…

Parameters

[Parameters not yet documented — likely declared in source outside register_animatable(). Add an override in _overrides/ if needed.]

Additional controls

Input — Single SliceContainer input. The number of output ports adjusts automatically to match the container’s slice count (visible in the panel as “Slices: N Outputs: N”). Connect from a Slicer’s “Slices” output, or from any other node that outputs a SliceContainer (e.g. Collage’s “Processed Slices”).

About Slices Parser

Slices Parser is the “fan-out” node of the slicing workflow: it takes a SliceContainer and exposes each slice as its own ComplexBuffer output port, so you can patch each slice into its own processing chain. Typical workflow: Slicer → Slices Parser → [different effect chain per slice] → Slices Concatener → CollageNode (or back into SliceMemorySlot for sampler export). No parameters of its own — output port count is purely derived from input slice count. If the input changes (different source, re-sliced with different mode), output ports auto-resize, which means downstream connections to higher-numbered slots get severed if the count drops. Plan that around your patching: bind connections to lower slot indices first when iterating on slice counts. Bypass routes the first slice to all outputs (useful for testing without changing patches).


Generated 2026-05-05 from K2K_Dev@96730bdc by scripts/gen_lexique.py. Edit _intros/ or _overrides/, not this file.