Owner's manual
SD7 - Getting Started
1-10
The section below the graphical rack picture allows configuration of either the cards or slots and sockets (including custom
naming, phantom power and pad selection), or card splits and control sharing. The Cards & Sockets and Splits & Sharing
buttons define which elements are displayed for configuration.
The local I/O configuration is fixed, so no hardware changes are possible. You can, however, change the Port Name, the Group
Names (relating to name of each physical card) and the Socket Names (the name of each physical connector on a card).
1.5.4 Opto V220 (DiGiRacks) and Opto V221 (SD Racks) .............
SD Series consoles can operate with either one of two different Optocore firmware versions - V220 and V221.
V220 is compatible with DiGiRacks and MiNiRacks and cannot be used with SD Racks or DRacks.
V221 is compatible with SD Racks, SD MiNiRacks, NaNoRacks and DRacks, and cannot be used with DiGiRacks and MiNiRacks.
Note: Any type of rack can be used with an SD Series console if it is connected with Coaxial BNC MADI irrespective
of the Optocore version that the console is using.
Sessions that have been created using Optocore connected DiGiRacks and MiNiRacks can be used with SD Racks and DRacks
but a procedure must be followed to acheive this.
Sessions created using Optocore connected SD Racks and DRacks can also be used with DiGiRacks and MiNiRacks but this also
involves a “conversion” procedure.
Note: For detailed information on Optocore system setup please refer to the user manual appendix - DiGiCo
Optocore V221 - For SD Rack Optocore Operation
1.5.5 Automatic Conforming .........................................................
Once all hardware is connected, go to System/Diagnostics/Optocore. This will list all connected Optocore devices either SDeng
(console engines) to SDrack (SD Rack or D Rack) by ID. If any expected devices are not listed, please check all physical connec-
tions, Optocore ID’s and Fibre Speeds. Once all devices are present, close the Diagnostics panel.
Irrespective of the type of rack being used, the system needs to be conformed. This involves the console checking the type of
racks connected and their I/O capability
There are three levels of automatic conforming:
- globally, using the red Conform All Ports button in the bottom left of the window;
- on a rack-by-rack basis, using the conform rack button just below the rack view
section of the window;
- on a card-by-card basis, by selecting a socket from the card in the graphical display
and using the conform card button next to the Card/Slot type button selector in the
lower section of the window. (Note that the Cards & Sockets button towards the
bottom-left should be selected)
Pressing any of these buttons will correctly select the card types for the range in question. Once complete, all of the Card Labels
beneath each slot should turn green.
1.5.6 Network & Mirroring .............................................................
The SD7 console is fitted with two separate Engines, and as such, offers built in redundancy. In order to take advantage of this
redundancy, you need to verify the console networking is working, and synchronise your session between the two Engines.
Before the Engines can be mirrored, you should ensure that a standard cross-over network (Ethernet) cable is connected
between the two Engines. Without this connection, the two Engines will not “talk” to each other.
To open the Network window, touch the Network button at the top of the Master Screen.
Press here to Mirror To or From
the selected device
Press here to send a session
to the selected device
Press here to receive a session
from the selected device
Press the Select button to choose which
device to send to or receive a session from
When highlighted in orange
the Audio Master button indicates th
at
this audio engine is currently active
Once synchronised, session detail
for both Engines will match
Optocore ID
As mentioned earlier in this chapter, if your console is equipped with Optocore connections, please check the Optocore IDs of the
engines before proceeding. Each console engine should have a unique Opto ID within the system