Closed ghostsquad closed 5 months ago
related to #171
I found a workaround using the Repeater Node.
The toggleRestriction
is only enforced when you actually toggle an item (by clicking on the toggle) and not if the nodes' modes are changed outside of the muter.
This is in the README and in the Node Help as well:
All to say, when you change a group to "enabled" that has it all linked to the Enable Processing?
Fast Muter, it's not that Fast Muter is just updating the status, it's not doing anything functionally. (Also, the mute/enable status of that Fast Muter itself also has no bearing on functionality).
I'm glad you found a workaround! I can't think of something else off the top of my head, tbh.
I have a Fast Muter inside a group. It's to manage ControlNet Preprocessors. It's in a group because I may not want that instance of controlnet to run at all. When I unmute the group, this node turns all options to "yes", despite the toggle restriction. Forcing me to click them all/most back over to "no".
Maybe there's a better way to handle this. I'm open to suggestions. Thanks!