rgthree
managing nodes that are not groups
case: there is “group 1” inside this group there is a node “node 1” and there are “group 2” and “group 3”. In the “Fast Group Muter” node we see “group 1”, “group 2”, “group 3”.
we turn off all the groups, we turn on “group 2”. In this case, “group 3” remains disabled, “group 1” is enabled (because it is a parent). but “node 1”, which is part of “group 1” and is not a group, is not enabled. thus, “group 1” seems to be enabled, but the nodes included in it that are not groups remain disabled.
It is necessary to make nodes that are not groups obey the same rules as the groups themselves: if their group is enabled, the nodes must be enabled as well. and vice versa.
I am new to this, so take this with grain of salt.
Try to move the group. Is the node coming with it, or is it behind the group. Happens to me all the time, but with groups within groups. But sometimes when I select several groups, some nodes don't stick to the group. Can't really reproduce this. It's just a hunch.
A more generic tip. I have a lot of groups and groups within those groups etc.
What I do is that I colorize the groups within a group brown and I keep the group muter within the main group and let it only control brown colored groups. Plus I also enter the names of the groups the muter should control in the properties of the fast group muter node.
Hope this helps. It keeps the muter nodes really clean, even with hundreds of nodes and groups in one workflow. There's a lot of power under the hood of those nodes!
