Is there a parameter I can set or something else I can do to automatically route messages to a container containing a composition to a node inside.
For example I have a container containing a TCP/IP DAT and I want messages sent to the container to be considered sent to the TCP/IP inside
I’ve thought that it would be nice to have custom parameters on containers to be used for operators within them but at this moment there isn’t.
One method that could be useful is to use variables. If you make container called local at the same level as the containers you want to control and within it have a dat named variables with the names of the parameters you want to control (this could be done procedurally with scripting for automatic naming). Then in the nodes that you want to control simply have the variable name in the parameter value field, ei $PARVALUE. You’ll then need to use some sort of method for changing your variables either with scripting or chopto dats.
Another method could be to use variables local to each container. This is also useful because you don’t have to give each variable unique names and you can use variables such as $OPD (operator parent digits) to select channels or table entries.
Using select chops withing containers to select a number of channels such as cont1/levels/opacity with cont$OPD* and renaming from cont$OPD* to *. This will give you the ability to have multiple containers with same networks withing them and not have to re-export any channels after making the initial container.
cheers
Keith
Thanks for your answer.
I did not surely figure out how to use/declare container variables yet, but this might be a good exercice to do so :]
in a script, you use the cvar command to define a variable as usable anywhere in the script’s parent container.
Ok, did not use that method yet.
I’ve figure out the “local” component + define table way tho. It is quite useful and I’m wondering how I was doing before that 