BrainModular

Sub-Patch Exclude Nodes?

2015-02-13T08:17:58+02:00

Maybe this isn't what you mean, but the vertical position of modules influences their inlet/outlet position?

I agree though, the option to expose or not nodes for subpatch buttons, faders, etc. would be nice (depending on cost).

Statistics: Posted by CREDO — 13 Feb 2015, 07:17

Sub-Patch Exclude Nodes?

2015-02-13T03:19:39+02:00

I have been burying sub-patches, regardless though. I still have lots of confusion

Just wish there was a way to organize the nodes exposed to the outside world.

-S

Statistics: Posted by sephult — 13 Feb 2015, 02:19

Sub-Patch Exclude Nodes?

2015-02-12T09:28:51+02:00

I have complained about this for many years. The automatic exposure of certain module ins and outs to the parent causes so much confusion. I still do not understand the thinking.

You can nest your subpatches 2 deep, but don't know what the processing penalty on that might be.

Statistics: Posted by woodslanding — 12 Feb 2015, 08:28

Sub-Patch Exclude Nodes?

2015-02-10T19:18:29+02:00

See that is what I had thought too.

I tried to modify the current button-in template, with different variations....like the one you showed and some of the flow types, but with no positive results. I will approach again, make sure I wasn't doing something obviously wrong (seems to be happening quite a bit...lol)

There is an IML for the sub-patch, so I am wondering if there is a way from there to do exclusions, like all buttons do not display an input, etc..

I was thinking the same thing for the child, assuming that if I modified the button input it would have not shown in the parent subpatch.

-S

Statistics: Posted by sephult — 10 Feb 2015, 18:18

Sub-Patch Exclude Nodes?

2015-02-10T18:13:51+02:00

I think IML/templates engine will do it, I think you have to create a new template.

I believe the link on the parent is governed by this chunk of code in the template:
2 // none=0,in=1,out=2

I haven't used them though, not sure I'd want to go there yet!

If you change the base template, then all instances of the control will be affected. So I think you need to try to create a new control with new behavior.

Statistics: Posted by shawnb — 10 Feb 2015, 17:13

Sub-Patch Exclude Nodes?

2015-02-10T15:45:56+02:00

One difficulty I find is organizing sub-patch nodes on the parent output.

Any Rhyme or Reason that anyone knows in cleaning up these nodes logically?

There are many cases where I add buttons or knobs, and wish that these were not exposed to the parent patch.
I assume there currently is no way to specify that this happens. Any idea if there is a possibility?

Maybe IML defined for subpatch?

-S

Statistics: Posted by sephult — 10 Feb 2015, 14:45

Sub-Patch Exclude Nodes?

2015-02-13T08:17:58+02:00

Statistics: Posted by CREDO — 13 Feb 2015, 07:17

Sub-Patch Exclude Nodes?

2015-02-13T03:19:39+02:00

I have been burying sub-patches, regardless though. I still have lots of confusion

Just wish there was a way to organize the nodes exposed to the outside world.

-S

Statistics: Posted by sephult — 13 Feb 2015, 02:19

Sub-Patch Exclude Nodes?

2015-02-12T09:28:51+02:00

Statistics: Posted by woodslanding — 12 Feb 2015, 08:28

Sub-Patch Exclude Nodes?

2015-02-10T19:18:29+02:00

Statistics: Posted by sephult — 10 Feb 2015, 18:18

Sub-Patch Exclude Nodes?

2015-02-10T18:13:51+02:00

Statistics: Posted by shawnb — 10 Feb 2015, 17:13

Sub-Patch Exclude Nodes?

2015-02-10T15:45:56+02:00

Statistics: Posted by sephult — 10 Feb 2015, 14:45