Compact Infinity Core
9
Compact Infinity Core
Document generated: 13.06.18
2.4
System Setup
General terms
Node Id
Each element (desk, core, D23m I/O frames) in the mixing console system
is connected via Ethernet. The so called “Node Id” is used to identify each
element uniquely so the software can communicate correctly. Thus each Node
Id must be unique.
Cloud Id
It is often the case that several consoles will be connected together via Eth-
ernet for resource sharing (such as Studer’s Relink). It is therefore necessary
that each element must also have a second Id to allow each element to know
which mixing system it is a part of; each Vista desk must know which
Infinity
Core (or Core) is processing its audio. This second Id is known as the “Cloud
Id” and must be set uniquely for each system.
There are two different parts of the network which have the same Id :
The network part on which desk and cores communicate.
Eventhough the Cloud Id’s of the Mixercloud and the IOCloud are the same
on one mixing system, the communication is kept separate between deks-core
and desk-IO by using different Portnumbers and different UDP Multicast
groups. This is what differntiates the Mixercloud from the IOCloud.
Numbering Rules
The Node Id is normally used as the last byte of the elements IP-address.
Network configuration
With a new ordered Vista Mixing System these settings are already configured
correctly. The diagram on the next page shows a complete overview of the
network configuration of a multi Vista system.
• Mixerclo
• IOClo
The network part on which desk and I/O frames communicate.
