DMX In

Easy, it's not in the manual because the Eos family consoles do not have a DMX In capability.

Expression did, is that what you're thinking of ?.

This seems to be the third message about DMX in recent months.

One of the main goals for some is actually DMX merging. Blending two consoles or other sources can be done in two ways. First is a specific device to do just that, made by several great companies. Second is less well known in that sACN when gets merged when pulled out of a network by gateways and dimmer racks.

I won't go into details, there are many. Its just a thought that might help with your situation.

So, setting an output of a 4 port gateway to "input" is in essence merging?

Effectively, yes.

Just as a Net 3 gateway takes sACN in and spits hardline DMX out, it can also do the reverse, taking DMX in and adding it onto the network as sACN.

There are some nice options in the gateway config as well, not only can you take a whole universe of hard line DMX and send it to any sACN universe you choose, but you can also use an Advanced Input Patch (AIP) to distribute specific addresses from the incoming univesre across different sACN universes.

This subsequently means you can also block access to specific sACN addresses from the incoming DMX.

Effectively, yes.

Just as a Net 3 gateway takes sACN in and spits hardline DMX out, it can also do the reverse, taking DMX in and adding it onto the network as sACN.

There are some nice options in the gateway config as well, not only can you take a whole universe of hard line DMX and send it to any sACN universe you choose, but you can also use an Advanced Input Patch (AIP) to distribute specific addresses from the incoming univesre across different sACN universes.

This subsequently means you can also block access to specific sACN addresses from the incoming DMX.

Thanks for the reply. I was ill informed. 

sACN also has priority by address. The possibilities boggle the mind.