Many, many, module connections

[tulamide]

The attachment Bobs1-1ExpanderTest.fsm is no longer available

Hello Gang,

In my never ending quest to make schematics cleaner I came up with this idea. Now this is NOT a real project that I am working on at all and is just for demo-ing the idea. By combing an input and output primitive into a module I can make cleaner looking schematics. Now this is a little over kill of course, but I just wanted to show that it does seem to work just fine.

Is this ok, or does anyone see problems with this idea?

Many thanks!
Later then, BobF.....

To be honest, I think my edit of your schematic is cleaner, but that might be a matter of personal taste. Apart from that: Each module you create is a place for Flowstone to look for, even if it's empty. So, having like a hundred of them might slow the schematic down, but other than that there's nothing that could hinder you from doing so.

[BobF]

Hello tulamide,

I confess that is really neat and I do try to us that method as much as possible. It's when I have a schematic that has lets say 50 plus components and they have 10 to 20 connections each it gets very confusing. Even using horizontal and vertical straight lines it still gets very complex and hard to see whats going where. I have a project I started a while back that got so bad I just gave up on it. Any way I may try tackling it again and use your way, mine, and maybe some wireless. Maybe that is the key, just a little bit of everything to keep something really big clean looking.

Thanks for reply!

Later then, BobF.....

[Nubeat7]

why not closing the gui, like this you have much more space, i personally always try to avoid curving connections at all.. i also try to avoid having more connections overlayed becasue you cannot follow them and you don't know how much are overlayed..

wireless would also be a solution specially when you have one source and multiple targets but normally i avoid to do this with the main (sound-) stream (mostly for gui parameters), to have the gui directly in the stream section is totally confusing and needs lot of space which makes the schematic much more "unreadable" so i normally link the gui controllers wireless to keep the main stream as straight forward as possible

the second thing where i use wireless links are modulation sources like lfo's, envelopes or arp's

and of course midi..

for your example i would do it that way..