There's not really such a thing as "
ETC sACN" for almost all purposes.
sACN is standardized at this
point (It would be like saying
Strand DMX).
Not entirely true,
ETC "Net 3" contains *more* than just standardized E1.31
sACN. But broadly speaking, yes.
In our
venue, we just got an
Ion Xe to refresh our primary
desk (Which was a Win 7
Ion), in large part to finally displace the MA 1 Ultralight that we use in our
Ballroom.
The update to
EOS that dropped Net 2 (EDMX) compatibility happened right before we got our Xe in (Which is inherently incompatible with Net 2 because it's a Win 10 based
desk), so our architecture is now as follows:
Desk into lighting
switch, with one
sACN node outputting three ports in
FOH: one to
plug into the input going to the ENR dimmers, and two
DMX outputs feeding into a Net 2
Node, which gets data to our 4 LX pipes +
Cyc lights via the corresponding Net 2 nodes we have in the air.
Elsewhere, we have
sACN nodes each side of
stage (
downstage, behind
proscenium) for feeding anything we need on the
deck, as well as one output which makes it's way up to a
truss we have suspended over the pit.
Technically, the
FOH sACN node is redundant, but feeding it all this way allows for renters touring with their own
desk to only need one
ethernet line run to their
desk. As opposed to one
ethernet and three
DMX lines.
I'll try and make a pretty little diagram later, but the simplified summary is this:
As far as any
console is concerned:
E1.31
sACN.
The complete internal architecture summarised as:
1x
DMX line (
Universe 1)
2x Net 2 Universes (2 and 3)
4x
sACN Universes (1 through 4)
EDIT: not that anyone has needed it, but I can also accept
ArtNet through the same nodes as well.