digital-garbage
963250a761
Two corrections to the commit before this one. A rank-1 latent's length is in the NODE that builds it and never in the format: core turns seconds into samples with a 44100 rate and a 2048 hop that latent_format does not carry, and the same rank means tokens of geometry for Hunyuan3D. Deriving `length` samples gave StableAudio a latent of 1 where core's own default is 1024 -- three orders of magnitude short, reported as success. Refused now, with the reason and the way out: a module for that model. The sweep claimed to skip H3 and did not. H3 has a rank-3 latent, so it was derived and passed at 32 channels for a video branch that has 24 -- a test passing on a model it is not correct for. So the previous message's "produces exactly what core's nodes compute for every single-tensor model" was wrong on both counts, and the sweep now says what it actually proves: the derivation agrees with what a model PUBLISHES, which is a floor and not a certificate. Rejected from the same report: an absent model module letting H3 fall through to the generic shape. Core cannot detect that without naming models, which is the one thing it must not do; a module that fails to import is already reported as a Warning, which is the level that can see it.
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.