Closed setothegreat closed 2 months ago
Yeah, I've encountered the same issue before, but it's not so simple to fix. It requires lots of patching in adv_encode.py
. I'll probably fix that later by duplicating Advanced CLIP nodes into my extension.
Yeah, I've encountered the same issue before, but it's not so simple to fix. It requires lots of patching in
adv_encode.py
. I'll probably fix that later by duplicating Advanced CLIP nodes into my extension.
No worries, and take your time. Because your NegPip, AttentionCouplePPM and GuidanceLimiter nodes improve multi-subject images so much it's still a drastic improvement over just using Comfy++ on it's own
I've added support for all weight interpretations. It requires Advanced CLIP Text Encode extension to be installed under default name in custom_nodes/ComfyUI_ADV_CLIP_emb
.
I've added support for all weight interpretations. It requires Advanced CLIP Text Encode extension to be installed under default name in
custom_nodes/ComfyUI_ADV_CLIP_emb
.
Still getting the same error. Updated PPM and reinstalled ComfyUI_ADV_CLIP_emb with a new workflow just to confirm.
Thanks for report! Selecting weight interpretations from ADV_CLIP by using STYLE keyword from ComfyUI prompt control extension worked correctly, so I didn't bother to check nodes from just ADV_CLIP - my mistake :( . There was a bug in hijacking process causing some troubles with nodes from ADVCLIP (with `BNK` prefix) - I've pushed a fix, they should work now.
I'll mark this issue as a completed. If the problem still occurs on your side - feel free to re-open it.
Hey there, and thanks for the great node additions! They've been a massive improvement over previous solutions in my limited testing so far, and will be super helpful for my workflows!
That being said, I have encountered an error when using Advanced CLIP Text Encode by BlenderNeko, and I would imagine the same issue would appear in other nodes that use the same re-weighting functions:
This occurs when using any weight interpretation method other than Comfy. It doesn't occur with any of the token normalization methods so long as Comfy is the selected weight interpretation. Being that Comfy++ tends to perform better than normal Comfy with longer prompts, it would be appreciated if this could be remedied.
This is the full error: