Skimmed_CFG
Skimmed_CFG copied to clipboard
Just wanted to say thanks for the extension! I ported it over reForge
Hi there, just wanted to say thanks! This extension alongside AutomaticCFG are pretty nice. I ported them over reForge and with the help of @pamparamm, they work absolutely great!
https://github.com/Panchovix/stable-diffusion-webui-reForge/tree/dev_upstream/extensions-builtin/reForge-SkimmedCFG
Awesome! Thank you! :D
I would also like to thank you for your work, it is very pleasant to use your nodes.
If you do not mind, could you answer the question:
-
Are the old and new Nodes not compatible at
import levelor only at theexecute level? That is, if our project have 20+ workflows, we should simultaneously transfer them to the new node? -
How to replace the standard old node with a new one - so that the result is as close as possible? Which of the three new Nodes should be used in the screenshot?
Thanks in advance
Edited: It doesn’t matter, I seem to have learned to make the behavior on the new Node very similar to the old one, and I’m quite happy with the result.
@Panchovix is it possible to use your implementation on the new Forge Gradio 4?
I would also like to thank you for your work, it is very pleasant to use your nodes.
If you do not mind, could you answer the question:
1. Are the old and new Nodes not compatible at `import level` or only at the `execute level`? That is, if our [project](https://github.com/Visionatrix/Visionatrix) have 20+ workflows, we should simultaneously transfer them to the new node? 2. How to replace the standard old node with a new one - so that the result is as close as possible? Which of the three new Nodes should be used in the screenshot?Thanks in advance
Edited: It doesn’t matter, I seem to have learned to make the behavior on the new Node very similar to the old one, and I’m quite happy with the result.
Sorry for not noticing your question, I only see it now. I am glad that you have found a solution.
I updated automatic CFG so to make it compatible with these nodes.
