Difference between revisions of "URY's Dante Network"
(added clocking info) |
|||
| Line 1: | Line 1: | ||
| − | This | + | ==Dante Clocking== |
| + | The Dante network uses a master/slave clocking architecture - there is a single master clock and everything else receives it's clock from there. The system can choose it's own master clock, or preferred masters can be defined. Some of the RedNet devices can also slave to external clocks. In URY, the Dante network master device is the RedNet 3 (Stores), which is in turn slaved to the Focusrite Scarlett 18i20 (USB'd to the broadcast server). | ||
| + | |||
| + | This was chosen as the clock master so in the case of network issues, or devices being added or removed from the network, the Scarlett doesn't break audio to the transmitter as it re-syncs it's clock (it's the master, so doesn't have to sync). The Dante network is slaved to this so the MADI links between the Scarlett and RedNet 3 don't have glitchy audio. | ||
Revision as of 18:42, 2 December 2018
Dante Clocking
The Dante network uses a master/slave clocking architecture - there is a single master clock and everything else receives it's clock from there. The system can choose it's own master clock, or preferred masters can be defined. Some of the RedNet devices can also slave to external clocks. In URY, the Dante network master device is the RedNet 3 (Stores), which is in turn slaved to the Focusrite Scarlett 18i20 (USB'd to the broadcast server).
This was chosen as the clock master so in the case of network issues, or devices being added or removed from the network, the Scarlett doesn't break audio to the transmitter as it re-syncs it's clock (it's the master, so doesn't have to sync). The Dante network is slaved to this so the MADI links between the Scarlett and RedNet 3 don't have glitchy audio.