Prism Sound MDIO-PTHDX, Руководство по эксплуатации, Страница: 16 / 35

Prism Sound MDIO-Dante Module Operation Manual Revision 1.01
©2019 - 2020 Audio Squadron Limited
16
allow you to hear the audio. Likewise to record into your DAW, you will need to route an Atlas Transmitter to
the DVS Receiver, and then assign that particular channel for recording in your DAW software.
Clicking in the cross-point between a Transmitter (a.k.a. TX) and a Receiver (RX) creates the routing – the
software thinks about it for a moment and then if the routing is successful, the cell shows a green ‘tick’ icon.
Dante calls a routing a ‘
subscription’
.
(If the routing is
not
successful – see below – ‘Synchronisation’).
The picture in the example above shows a very simple setup with just two Dante devices :-
•
Atlas (named ATLAS-0132e8)
•
A computer running Dante Virtual Soundcard (named DVS).
The cursor (where the darker blue lines meet) is over the routing between
DVS TX 01 - i.e. channel 1 output of the DVS driver/ your DAW software and
Atlas’ RX Analogue Out 1 – i.e. Atlas’ Analogue Output number 1.
You can see that I’ve also routed DVS’s TX 02 to 08 to Atlas RX Analogue Out 2 to 8, and so in your DAW,
outputs 1-8 are connected through to Atlas’s Analogue outputs 1-8.
And in the lower left quadrant of the grid, I’ve also set up routings for Atlas’ Analogue Inputs to map them to
the DVS’ RX1-8 and hence to the audio inputs of your DAW.
It’s worth noting that Dante receivers and transmitters have an ‘address’, like an email address, to help you
work out where they belong. In the yellow pop-up box in the picture above, the analogue output of the Atlas is
referred to as
Analogue Out 1@ATLAS-0132e8,
and the DVS output is
01@DVS.
These names can be customised – see the
‘Renaming Channels and Devices’
section below.
However… before you can start designing some routings, you must check that the devices you wish to route
between are synchronised.
Synchronisation
Multiple sample rates can exist in a Dante network, however there is no sample rate conversion, and so you
can only make
connections
between devices that are at the
same sample rate.
In addition, the devices on the Dante network must be synchronised. This can be automatic – it’s possible to
synchronise the audio to the Dante network’s clock, but in the case of Atlas, we have retained the ability to
synchronise the audio to external sync sources, such as Word Clock or digital input.
In addition to options for Local Sync and Sync to Word Clock/DI, the Dante version of the Atlas Control Panel
has a Sync Source option for ‘PTP’, which stands for ‘Precision Time Protocol’ and when selected means that
Atlas will take its sync from the Dante network clock.
From the Dante network’s perspective, an Atlas on Local clock, is actually
externally
sync’d (external to the
network sync).
The Dante network has methods for automatically ensuring devices are in sync. You can elect a ‘preferred’
Master, which the Dante network will make it the ‘Grand Master’ for sync if it’s present (and if there are no
other competing ‘preferred’ sync masters on the network).
The simplest way to sync the Atlas units on a Dante network is to set them all to ‘PTP’ using the Sync Source
Control on the Atlas Control Panel. You can elect a Preferred Master there if you wish. The Dante network will
take care of which device is the master clock.
Alternative Sync regimes…
1. Set one Atlas to Local (in the Atlas Control Panel) and set it to be ‘Preferred’. Set all other devices to
‘PTP’. The devices on the network will sync to #1 Atlas’s clock via the network.
2. Set one Atlas to Local and set it to be ‘Preferred’. Set all other devices to Sync Source = Word Clock.
Then you must connect from the #1 Atlas’s Word clock out, to the next device’s word clock in, and
chain it on to other devices in the network. (Of course this may not be so easy due to location of the
devices).