-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLIP Text Encode (Advanced) errors as of new ComfyUI commit #12
Comments
I'm finding a similar issue with the regular KSampler too.
Reverted back to the native Text Encoder (New) and the workflow runs without issue. |
Same problem here. I'm using Efficiency custom nodes, I set positive and negative input from text and they work fine til the last update of ComfyUI.
Switch to regular text encode works no problem. |
Same problems... first, I got some color noise corrupt images, then KSampler stop working and gave me those errors... |
should be fixed now |
@BlenderNeko |
@liulsg I can't really do anything with that. Are these my nodes or someone else's? what are the current commit short hashes of both ComfyUI and ComfyUI_ADV_CLIP_emb? (you can check this by running |
works for me now |
Yeah, I updated it by running those 2 bat files in the update folder. |
list indices must be integers or slices, not str |
Latest ComfyUI gives this error:
for |
update comfyui, be kill 99% of problems |
Hi, have you solved it? I met the same problem. |
Hello! Please tell me how to switch to this encoder in ComfyUI |
Hi, as of ComfyUI commit comfyanonymous/ComfyUI@e60ca69 the node seems to throw out the following error down below, refusing to begin generating at all. Reverting to comfyanonymous/ComfyUI@6ec3f12 fixes this issue, leading me to believe that the changes in the tokenizer are responsible for this issue:
Thank you for your help in advance!
The text was updated successfully, but these errors were encountered: