Closed suede299 closed 1 year ago
I should be able to make a real README for these nodes in a day or so, finally wrapping up work on some other things. But for now, the info I can impart is that you can either connect the CONTROLNET_WEIGHTS outpu to a Timestep Keyframe, or you can just use the TIMESTEP_KEYFRAME output out of the weights and plug it into the timestep_keyframe input on the Load ControlNet Model (Advanced) node directly. The TIMESTEP_KEYFRAME output on the Weight basically creates a Timestep Keyframe internally, so that you can use it a shortcut if you are not connecting anything else to a Timestep Keyframe node like latent keyframes.
These two connections are identical, is what I'm trying to say ^
Thank you. I tried that and it worked. But load controlnet model(advanced) is not able to load control lora of sdxl. i am using an openpose model to test that it works.
Hmm, I think a PR I just accepted a few hours ago broke SDXL ControlLora support.... thanks for the heads up. To see if that's right, can you try to get this commit for this repo and see if SDXL COntrolnet works? 15e438100fb6f7e946da0112c08d44a78e8e54e2
Just pushed out an update that should fix the SDXL controlnet issue - at the very least, the LoRA controlnets should no longer throw an error. But in general, SDXL ControlLora stuff will not be affected by the weights, if there is a "my prompt is more important" option in auto1111 that works with ControlLoras, i'll need to dig in the code there to see how they implemented it.
Let me know if that fixed it, and if not show providing an error message and/or screenshots will help! I haven't messed too much with SDXL yet, so I do not have a workflow ready to test for it.
Right now I don't know how to use it. But it does need similar functionality.But it does need similar functionality like the controlnet plugin in sdwebui