Closed spacepxl closed 5 months ago
Thanks for the heads up. Could you list every class of model that you were able to see AnimateDiff working with? (separated by SD1.5/SDXL)? It would be a great help.
class SD15_instructpix2pix(IP2P, BaseModel)
(works with sd1.5 motion modules)
class SDXL_instructpix2pix(IP2P, SDXL)
(works with hotshot and xl motion modules)
I think the pix2pix models should be properly whitelisted as SD15/SDXL models now, would you be able to check on your end with the most recent version of AnimateDiff-Evolved to verify?
I tested and can confirm that it is working with the normal KSampler now. However, with SamplerCustomAdvanced (useful for controlling the dual CFG for ip2p), it fails, usually with the following error:
Except for one time when I got this error instead:
Here's a test workflow: ip2p_AD_SamplerCustomAdvanced.json
However, I think these are general issues with any model between AnimateDiff and SamplerCustomAdvanced, not related specifically to ip2p. I tested SamplerCustomAdvanced with AnimateDiff on a normal 1.5 checkpoint and got the same device mismatch error. The basic SamplerCustom doesn't have this issue, it works just fine.
I bypassed the model compatibility check, and confirmed animatediff does work with sd1.5 ip2p and sdxl edit/ip2p models, with animatediff and hotshot motion modules. Not sure how you would want to change the compatibility check, maybe by partial string matching or a hardcoded compatibility list. It makes sense that it would work without any other modifications, since the only difference between a vanilla model and an ip2p model is the number channels on the input layer (8 instead of 4).
example test workflow