digital-garbage
ceac622f2c
Piece A of the H3 workflow port: the loader/SigmaShift/ImageTransformKJ/ R2V/sampler-at-CFG-1/decode/video-mux chain the H3 user runs by hand today, offered as a preset (GET /api/pipeline/presets) loadable into the same editable pipeline core/graph.py already supports -- not a second "default", which module-load order would make ambiguous. References are deliberately NOT pre-wired into R2V's ref_images autogrow; an unwired optional slot is what "not in use" means to that node (absent from its ref_images dict), not an empty image degrading its <Picture i> numbering. boot.js wires them per-run based on what's actually picked -- next commit. Building this against a real ComfyUI+KJNodes registration (not a fake schema) surfaced a genuine core bug: core/graph.py's from_comfyui() had no idea what to do with a V3 MatchType socket (ImageTransformKJ's own image input) -- its bare type name "COMFY_MATCHTYPE_V3" matched nothing, so a completely legal IMAGE wire into it was refused. Fixed generically in comfy_types.py (match_type_union()) and graph.py, for any node using MatchType, not special-cased to this one.
ComfyUI-FunPack v5 — "Cunning Cranberry"
FunPack v4.0.0 is going to be the latest release of classic FunPack. Next update is another milestone update, or shall I say, a full rework.
Maintenance of current FunPack became a mess — forgetting to add or remove buttons from/to UI, finding functions that don't do anything but still present in the code absolutely randomly, trying to keep the UI neat while it has no strict boundaries on how it should look like, and of course — making it easy for users to understand how FunPack operates and how you can operate it — this is all time, money and token-consuming.
General idea behind the FunPack v5 rework is writing it from scratch, with a new architecture where a feature can't be forgotten, where a wire can't be missed, where one failing module never stops whole process from executing. Loaders and features would tell the UI by themselves what sorts of inputs they need and where to put it — and UI will compose them according to design guidelines it would have. Samplers would become independent from features — if a feature is available and enabled, sampler would call it. If it's not — it gets skipped and doesn't even appear in the UI so it won't confuse you.
Most of this comes from a FunUI backend draft that got shelved after understanding on how much time has to be invested into polishing it. Without a community support and wide usage it would become another dead project only one person in the world needs but no one else.
Come to think of it, FunPack already became something alike, with an exception — this project is more than alive, and while I can, I will support it.
Final goal is to make FunPack an ultimate answer for a novice's question "I don't know how to generate — what do I install and how do I start?" and for a professional's question "I need a UI with all the cutting edge techniques available on day 0 — which one?"
Preparation for the v5 had started.
FunPack v5.0 "Cunning Cranberry" — coming fall 2026.
This branch is a clean start. Classic FunPack lives on main.