-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
ApplyCLIPSeg+ Input image size (352*352) doesn't match model (224*224). ERROR in PINOKIO Comfyui #5642
Comments
You need to downgrade transformers package. |
I have this error in Pinokio ComfyUI. I understand I need to install (downgrade) transformers==4.45.0. I did that with anaconda and pip install transformers==4.45.0 but in E:\pinokio\api\comfy.git\app or where in which folder should it be installed? I also didn't find any test_modeling_clipseg.py, only a modeling_clipseg.py. |
You need to downgrade the package in the Python environment where ComfyUI is running. For the correct method to downgrade the pip package in the Pinokio environment, it would be best to consult Pinokio's repository. As long as the transformers package is downgraded, there's no need to worry about other parts. |
comfyUI in pinokio updates always transformers to the latest version 4.46.2 I need transformers 4.45.0 for "Apply Clipseg+" to work |
ComfyUI cannot independently resolve actions that occur within Pinokio. |
Go into the folder Pinokio\api\comfy.git\app ... Shift right click on the folder window. Choose "Run Powershell from here" once the shell opens type "env\Scripts\activate" you should now see a green (env) . |
Your question
How can I solve this error "ApplyCLIPSeg+
Input image size (352352) doesn't match model (224224)." in PINOKIO ComfyUI?
thanks for any feedback.
Logs
System Information
Devices
Logs
Attached Workflow
Please make sure that workflow does not contain any sensitive information such as API keys or passwords.
Additional Context
(Please add any additional context or steps to reproduce the error here)
The text was updated successfully, but these errors were encountered: