multi-channel Bidirectional Automation Block Interfaces, Advanced Multi-Channel Automation Wire and Channel Filter Automation Blocks

[The Plum Gate]

Bidirectional Automation Block Interfaces, Advanced Multi-Channel Automation Wire and Channel Filter Automation Blocks...

May also be referred to as a muxer/demuxer blocks, multichannel automation wire, channel filter blocks.

Let me explain by describing the logic: The muxer/demuxer block is a no operation logic block - it does not alter the signal, so it's a NOP block. However, it also condenses the signals into one port for use with multichannel automation wire. For example, A 2x2 NOP block with three input/output ports (T1,T2,T3 corresponding to 3 seperate automation signals, C1,C2,C3 ) - these transmit in either direction and have the same automation priority as toggle switches. This bit is important for bidirectional signal propagation and it embraces pre existing implementation. An additional 4th port, in this example, is a special "wiring harness" type port for multichannel channel wire. So..

Advanced Automation Wire: Following my example above, 3 automation channels ( ex: it takes 15 refined metal and 5 plastic to make a section of it. It's advanced, needs to be costly am I right? This channel count could be scaled up to some arbitrarily higher number so that more than 3 channels can exist and other functionality becomes available. A material cost balanced number preferably ). The advanced automation wire can be run like any other automation wire, but importantly, it can run to another multi channel or single channel  NOP block where the signals get transmitted to the the channels according to the channel filters. Following the 2x2 block example C1,C2,C3  to T1,T2,T3, etc.

Running a regular automation wire into advanced automation wire could result in undefined behaviour unless it defaults to channel 1 - in which case we have a solution for tapping channel one, but not the other channels. Therefore, channel filter automation blocks, again being bidirectional NOP blocks with a channel filter selection method, would be a 1x2 block with an Advanced Automation Wire port and a normal automation wire port. The channel filter would be an aspect of user interaction - some button corresponding with a channel in the multichannel wire and would set the channel of input and output between the advanced and normal sides of this automation block.

I can't think of any specific examples, but it may as well be possible to use the multichannel wire with any of the existing logic gates as they are. So multichannel wire on OR gates, AND gates, etc would just take notice of all channels on either input. I can think of a dozen ways this could get screwy however. This is why I suggest specific multi channel ports on specialty automation and not generic ports everywhere. The flip side of this idea is, that you could just add channel filters to every automation port, default to channel one, on everything, then the player could manually set a filter on each - this is getting cumbersome, so I digress.

So, I have exemplified multichannel wire and how it might get tapped or muxed and demuxed for multi channel automation wire, single channel bidirectional taps and multichannel muxing/demuxing blocks such that a number of automation channels can exist on an advanced automation wire.

A closely related, additional block that might be useful under advanced automation conditions is explained here as a NOP diode ( spoilers, it's an old post and essentially there are already workarounds, but they're a bit cluttered ). A NOP diode would not be bidirectional, and would isolate a section of wire from another so as to prevent back signaling.

 

[TG pro]

Umm