Closed amanjain1397appy closed 3 months ago
will fix soon today
Has this been resolved? The test still doesn't work!
Same problem still. The original version of sd-webui-animatediff (2.0.0a) also has got the problems in the API mode when adding ControlNets. The same payload configuration that used to be working well under 1.13.1 now fails.
Hope they can be fixed ASAP
FYI I made an unofficial hacky fix to v2.0.0a and the A1111 API now seems to work correctly for Animatediff+ControlNet .
I guess a similar fix can be applied to the forge versions v2.0.1f as well by modifying the related codes
hopefully in today's new version it is working properly. if not, let me know.
Is there an existing issue for this?
Have you read FAQ on README?
What happened?
I have installed the latest sd-webui-forge and also added this sd-forge-animatediff extension. In the UI, the AnimateDiff process is working fine, but as soon I try to replicate the process via the API, I am getting the following error.
I am using the following payload:
Steps to reproduce the problem
What should have happened?
I should have gotten a list of base64 strings in the response.
Commit where the problem happens
webui: Forge 1.7.0 (latest) extension: sd-forge-animatediff
What browsers do you use to access the UI ?
Google Chrome
Command Line Arguments
Console logs
Additional information
No response