what protocol does dante use to assign ip addresses to devices?

Dante Network Considerations

SERVER and SERVER IO DAN-ane Carte du jour

The Dante DAN-1 card, based on Audinate's Brooklyn Two Module, allows Tesira SERVER or SERVER IO devices to share digital sound with other Dante-enabled devices, both from Biamp and other manufacturers. Each DAN-i card can transmit upwards to 64 channels of audio and receive upward to 64 channels of sound using up to 32 flows in each direction.

Each input and output block of channels can exist defined with betwixt 1 and 64 channels of audio (for a total of 64 inputs ten 64 outputs allocated to all blocks per DAN-i menu ). Each Dante aqueduct will have an explicit proper name. Dante DAN-one card Hostnames are maintained in the respective Server'southward Device Maintenance dialog. The device will need to be reset (configuration cleared) to be able to rename or modify the Host Proper name and IP Accost.

TesiraFORTÉ Dante

The Dante-enabled versions of TesiraFORTÉ, based on Audinate's Brooklyn II Module, allows the unit to share digital audio with other Dante-enabled devices, both from Biamp and other manufacturers. Each unit can transmit up to 32 channels of sound and receive up to 32 channels of sound using up to sixteen flows in each direction.

Each input and output block of channels tin can exist defined with between 1 and 32 channels of audio (for a full of 32 inputs x 32 outputs allocated to all blocks per unit). Each Dante channel will have an explicit name. Dante Hostnames are maintained in the corresponding Server'due south Device Maintenance dialog. The device will need to exist reset (configuration cleared) to be able to rename or alter the Host Name and IP Address.

Audio-Technica Microphone

Up to 32 Audio-Technica Dante microphones can be associated to a DAN-i card. xvi may be associated to a TesiraFORTÉ device. Delight review the Audio-Technica Mic, Audio-Technica Mic Networking Considerations and Audio-Technica Dante Mic Hardware sections for more than details on this device.

SHURE Microphone

Upwards to iii SHURE MXA910 Dante microphones or 6 MXA310 Dante microphones tin exist associated to a DAN-ane carte. Ane MXA910 or three MXA310 Dante microphones may exist associated to a TesiraFORTÉ. Please review the SHURE Mic, SHURE Mic Networking Considerations, SHURE MXA310 Dante Mic and SHURE MXA910 Dante Mic sections for more details on SHURE'south MXA series.

Attero Tech Wall Plates

Delight review the Attero Tech Wall Plate, Attero Tech Wall Plate Network Considerations and the unDX2IO+-B / unDX4I-B / unD6IO-B hardware pages for more details on these devices.

Dante

Dante is a proprietary digital media networking solution, developed by Audinate and licensed by Biamp, which operates on 100Mbps and Gigabit networks using standard Internet Protocol (IP) over Ethernet. A Dante stream distributes sound plus integrated control data over the network. It allows for transporting depression latency uncompressed audio over standard IP Ethernet networks with sample accurate synchronization, automatic device and channel discovery, and easy to use point routing.

Many of the properties of the Dante streams (or channels) are configurable only through Audinate's Dante Controller software. Most importantly, routing of audio signals from transmit to receive between devices is achieved in Dante Controller.

• Channel naming can be washed in Tesira software only when offline, the information is sent to the DAN-1 carte or TesiraFORTÉ Dante enabled device on upload to the Dante network.
• In one case Online, routing and aqueduct assignment can only be washed in Dante Controller software.

Alarm

Do not rename transmit and receive nodes while online using Dante Controller. The names may go corrupted or lost in translation back to the Tesira software. Firmware updates and resetting of the device via Dante Controller is Not supported. These functions must be performed through the Tesira software.

AES67 Back up

Tesira iii.9 release supports utilise of AES67, which is a technical standard for sound over IP and audio over ethernet interoperability. AES67 is a layer 3 protocol suite and is designed to allow interoperability between a variety of IP-based audio networking systems. For Tesira, this support is specific to Dante-enabled equipment and will let interoperability between other networking systems such every bit RAVENNA, Livewire and SVSi.

The Dante controller (described below) allows engaging devices that have firmware installed that supports AES67 - this is required in order to configure for AES67 mulitcast streams through the Dante controller. Note that Dante devices cannot subscribe to AES67 flows from other Dante devices. See the Dante Controller support documentation for more than data on enabling AES67.

Dante Domain Director Back up

Tesira 3.eleven release supports Dante Domain Manager which makes audio networking more secure, scalable and manageable. Integrators can ascertain specific AV device groupings by room, edifice and site, allowing for the creation of contained Dante Domains that enable a single Dante Domain to encompass multiple network subnets.

Dante Domain Manager is available from Audinate every bit a virtual appliance for various hypervisors. Please review the Dante Domain Director User Guide for more than details.

Firmware Updates

Normal Dante card firmware updates volition be handled with a regular Tesira firmware update that is processed through Tesira Device Manager.

If a Dante firmware update or recovery from crash is needed you will use Audinate's Firmware Update Manager software, refer to the Dante carte du jour Failsafe Recovery Department.

Audio

The standard bit charge per unit for the Tesira Dante is 48kHz / 24-bit.

Dante automatically converts among the PCM word sizes when necessary. Dante won't connect incompatible sound devices. In practice, if Dante Controller software allows a connection to be made, it should pass sound.

Dante Controller and channel routing

The Dante audio network'due south point routing must be done via Audinate's complimentary Dante Controller software on either a Mac or PC. It tin can be downloaded from Audinate. Further data can exist plant on the Audinate website under Support > Documentation > User Guides.

In order to connect two Dante devices, the user must specify both endpoints using Dante Controller. Unlike CobraNet and AVB, Dante provides per-channel routing, and then each Dante receiving channel tin conceivably come from a different Dante-enabled device. Dante supports multicasting, or fan-out on the network, assuasive more than one receiving device and channel per transmitting channel. There is not a limit to the number of receiving channels for a multicast stream.

Dante Controller software operates in real time, and reflects the current country of the network to which it is connected. For this reason, audio routes cannot be pre-configured before deploying a Dante network. Additionally, you tin can monitor device status and clock condition via Dante Controller.

Once the system has been prepare the Dante Controller software can exist close down or removed. The routing information is stored in the Dante-enabled devices themselves.

Since Dante aqueduct routing is washed after the Tesira layout has been compiled information technology is non possible to predict streams and bandwidth requirements as can be done with AVB.

Flows: Unicast and Multicast

Each DAN-1 card tin can transmit up to 64 channels of audio and receive up to 64 channels of sound. A TesiraFORTÉ Dante enabled device can transmit upwardly to 32 channels of sound and receive up to 32 channels of audio A ready of channels from a particular device is encapsulated in packets called a menstruum. A flow is a standard container for upwards to 4 channels which is created automatically when yous configure Dante routing. In connections to the aforementioned receiver, no new flows will exist created until all iv channels in the most recently created menstruum are filled.

If a transmitter runs out of the bachelor flows, multicast is necessary to reduce the number of transmitted flows. You can bank check the number of transmitted flows using the Dante Controller software (under Transmit Flows in the Transmit tab of the Device View). A notification will appear if there are not enough available flows.

Also, it's possible for receivers to not have enough flows in special cases, such every bit when single channels are received from a large number of devices. In such a case, multicast will not reduce the number of flows, and then it's necessary to reconsider the routing itself.

If there are non enough flows available for transmission, use the Dante Controller software to configure multicast, and reconfigure the network then that less flows are used. Be conscientious to keep the number of multicast flows (channels) to the minimum, considering multicast flows increment the load that the switch is subjected to. Up to eight channels can exist grouped into a multicast menstruum, further increasing their efficiency.

Finally, to aid manage the multicast traffic on the network it is recommended to enable IGMP snooping on your switches.

Network Connections

The DAN-i carte du jour connects via standard CAT-5e or college network cabling to a network switch, aforementioned as a TesiraFORTÉ Dante enabled device. This is a split up connection from the SNC-ane, SNC-2 or Control network control port on the Tesira, and requires its own cablevision. It can share the same network switch hardware network control port if necessary.

Unlike AVB (Sound Video Bridging) or CobraNet, Dante does not require special switch hardware, protocols, or VLANs, allowing it to operate with current "off-the-shelf" network hardware along with standard network traffic. As a rule of thumb, a separate, dedicated Dante network is recommended for loftier aqueduct-count applications.

• Audinate states that Dante is fully compliant with AVB IP protocols; still, Dante is not AVB and cannot communicate with or pass audio to or from AVB devices. Certain Dante hardware is sold as "AVB ready" meaning that firmware may be upgraded at some future date to support AVB when compliance standards have been completed.

Wireless LAN (Wifi) is non supported. While possible in principle, the practical limitations of current wireless engineering science (802.11a/b/thousand/north) render reliable performance unachievable.

Note

Any switch that supports Diffserv (DSCP) QoS with strict priority and 4 queues, and which has Gigabit ports for inter-switch connections should be appropriate for apply with Dante.

QoS is recommended for Gigabit switches on networks that share information with services other than Dante. A Gigabit interface is required for channel counts above 32 10 32 48kHz/24bit.

Dante supports the use of mixed 100Mbps and Gigabit hardware, audio with mixed sample rates and bit depth, and allows the pattern of network zones with different latencies.

For low aqueduct count (<32) applications, a 100Mbps switch may be used every bit long as information technology supports proper QoS, and QoS is active. The use of 100Mbps switches without QoS is non recommended or supported.

Although ability management should be negotiated automatically in switches that support EEE, it is a relatively new technology, and some switches do not perform the negotiation properly. This may cause EEE to exist enabled in Dante networks when it is not advisable, resulting in poor synchronization performance and occasional dropouts.

If y'all employ managed switches, ensure that they allow EEE to be disabled. Make sure that EEE is disabled on all ports used for real-time Dante traffic. If you use unmanaged switches, do not use Ethernet switches that support the EEE office, because you cannot disable EEE functioning in these switches.

Single-link network limitations:

• Gigabit: 512 x 512 48kHz/24bit audio channels tin be sent over a unmarried link, giving a total of 1024 bi-directional channels. (Tesira does not offering 96kHz sample charge per unit support.)
• 100Mbps (Fast Ethernet): 48 10 48 48kHz/24bit audio channels can exist sent over a single link, giving a total of 96 bi-directional channels. (Tesira does not offering 96kHz sample rate support.)

The number of channels that can traverse one link in a network is proportional to the link speed. A link volition always slow downwards to the lowest speed connector on that link; for example if a Gigabit port on switch A is continued to a Fast Ethernet port on switch B, the link speed volition exist 100Mbps Fast Ethernet. This is proficient, because it allows you to mix link speeds in a network without having to do anything complicated.

Audio is transmitted over the network in UDP/IP Packets. A single IP packet may contain audio samples from several sound channels, and may comprise multiple audio samples for each channel.

Audio packets can be transmitted using either unicast or multicast addressing. By default they are sent using unicast, but the user tin can change this to multicast using the Dante Controller. Multicast and unicast tin can be used at the same fourth dimension on a Dante device. Channels are individually selectable for multicast transmission.

Device Discovery

When connected to an IP/Ethernet network a Dante-enabled device will automatically configure its own IP address and advertise itself to other devices on the network. Dante-enabled devices volition automatically discover 1 another over the network and learn each other's capabilities (number of input and output channels, sample rates and bit depths supported, etc.).

Dante devices obtain IP addresses automatically past default - so there should exist no need to specify static IP addresses unless it is a specific requirement for your network.

• You lot can configure static IP addresses for one or both of the Ethernet ports (for supported devices) via the Network Config tab of the Device View for the device in Dante Controller.
• If your network has a DHCP server, Dante devices will receive their IP configuration using the standard DHCP protocol.

• On a network without DHCP, a Dante-enabled device will automatically assign itself an address using 'Bonjour' Nada Config auto addressing protocol by Apple. Devices volition automatically assign themselves an address in the range 169.254.*.* (172.31.*.* for the secondary / redundant network, if present).

The secondary port constitute on the DAN-ane card is not to be used for daisy chaining – this is for Dante back-up only. Dante offers a full-time redundancy pick with permanent principal and secondary sound manual. Redundancy requires a second distinct IP network. Cantankerous-connecting the two networks volition cause errors seen by Tesira as run time faults. Dante Controller must be used to identify bug in Dante streams. TesiraFORTÉ Dante enabled devices characteristic simply 1 Ethernet port which is designed to be connected to the primary Dante network. Because there is simply one Ethernet port on a TesiraFORTÉ Dante enabled device, redundancy is not supported.

Since Dante uses IP and non Layer two addressing, with Audinate'due south Dante Netspander software installed on a qualified rack-mount server Dante digital media tin be transported across up to forty subnets and across IP routers for large scale installations.

Dante devices are connected via a network switch, which most oftentimes means a "star" topology – all devices are continued to a unmarried central point, which minimizes the number of "hops" through which data must pass. This also avoids the scenario in which the failure of ane device causes the entire "daisy chain" to break.

Because Dante works with standards based networking technology, using fiber is simple. Utilise a switch that supports cobweb connections to ship Dante information over a fiber optic cablevision. Ethernet is non copper or cobweb based, it is independent of the cabling medium. Many organizations may accept fiber already in place from other projects and this can simply exist re-used on a Dante network.

Setting Tesira Dante card Network settings

The Network settings of the Dante cards tin can be adjusted in Device Maintenance > Network. In a SERVER or SERVER IO the Principal and Secondary interface IP address can be specified independently.

Selecting the Interface Condition push will show the relevant settings beingness used.

Naming rules for Dante

In Dante, devices and audio channels are identified past names and labels which can be customized. Names can exist assigned to channels while offline in the Tesira software and they will be offered to Dante Controller for use. It is strongly recommended that naming is done while offline, in the Tesira software just, to protect against names being lost or corrupted in the event of a power cycle or reboot of the Tesira device.

Initially all channels will be given names in the class

• <Instance Tag>_<Channel number>, where Example Tag is the default value when the block is created and aqueduct number is within the cake, starting with 1.

If working with the SHURE MXA Series microphones, all channels will be given names in the course <Instance Tag>_Lobe<channel number> or <Instance Tag>_Mix<channel number>, where Instance Tag is the default value when the block is created and channel number is within the block, starting with one. The Lobe channels are betwixt one and 8, depending on the number of lobes selected at the fourth dimension of cake creation. Also, the Mix output volition be shown if the choice was selected at the time of block creation.

All Dante names and labels are up to xxx characters in length. Proper noun and label comparisons are case-insensitive; "Guitar" and "guitar" are treated equally the same label. Unicode and non-roman characters are not supported.

Tesira Dante hostnames will be unique, following the convention TesiraServernnnnnnnn-Slotnn where the Tesira's Serial Number and Bill of fare Slot Number are appended to the string "TesiraServer".

Device names should follow Domain Proper noun Arrangement (DNS) hostname rules. Legal characters are A-Z, a-z, 0-9, and '-' (nuance or hyphen). Device names must begin with A-Z (or a-z).

Aqueduct labels may use any character except '=' (equals), '.' (full stop or period), or '@' (at). Aqueduct labels must exist unique on a device.

Channel labels practise non need to be unique on the network every bit they are ever qualified by device (aqueduct@device).

Device Names and Aqueduct Labels

Dante routing is performed using the device names and channel labels. A receive channel can be subscribed to the name of a transmit channel at a device. Instance: "Analog L@my-transmitter" describes a channel labelled "Analog L" on a device named "my-transmitter". Device names must be unique on a Dante network. Aqueduct labels must be unique on the device.

If a device or aqueduct is renamed, Dante routing considers it to be a unlike device or aqueduct. If a new device or channel is then given the old name, Dante routing will road from the new device in place of the previous device. Example: The power supply on "stage-box" fails and "stage-box" needs to be replaced. The sometime "stage-box" is removed, and a new box is plugged in and named "stage-box". Dante receivers previously subscribed to the old "stage-box" will at present automatically restore their subscriptions to the new "phase-box".

Device names must exist unique on the network. If you lot endeavor to rename a device using Dante Controller to a proper noun that is already in use on the network, Dante Controller will notify you and refuse the proper name alter. Case: There is an existing device on the network called "MY16-slot1". If user attempts to rename another device to "MY16-slot1" Dante Controller will notify the user that the proper noun is already in use. The device will not exist renamed.

If a new device is added to the network with a proper name that already exists, a name conflict is detected, and one of the devices will rename itself by appending (two) to its name. This device will not be able to transmit sound until it is renamed.

NOTE: A device that has been renamed with (2) appended (east.g. "MY16-slot1(ii)") will non be able to transmit sound until information technology is renamed. The device name must be changed by the user to be a valid non-conflicting proper name before the device can become fully functional.

Tesira device names will be defined by default as "TesiraServernnnnnnnn" where the string TesiraServer is appended by its series number. Equally with the channel names, the device names can be changed to better reverberate the utilise case associated with the device.

In Tesira inputs and outputs will be assigned names in the gild that the blocks are created. The names denote which block and aqueduct within the block is associated with a given stream on a given device. The first input block would brainstorm with "IN1_1", the second input block will begin with "IN2_1", etc. Output channels will be allocated in the same mode, beginning with "OUT1_1" and so on. The input and output blocks are a Tesira software convention which are not "seen" past Dante Controller, it but cares that the Tesira DAN-ane has 64 in and 64 out available.

DAN-1 Menu Redundancy

Dante offers a total-fourth dimension redundancy option with permanent primary and secondary audio transmission on each DAN-1. Card Redundancy requires a 2nd singled-out IP network, either using a second switch network (recommended) or via a VLAN isolating the network traffic.

Dante redundancy requires that both the primary and secondary interfaces on any redundant card are connected using the same link speed.

If the secondary network is connected to a device that supports redundancy, information technology is enabled automatically. Audio information is transmitted on both the chief and secondary networks simultaneously. In the event of a failure on one network, audio will still go on to exist received via the other network.

TesiraFORTÉ Dante enabled devices that do non support redundancy must exist continued to the primary network only.

Dante Controller must exist connected to the primary network.

The secondary port plant on the DAN-1 card is for Dante redundancy only, it is not to exist used for daisy chaining devices.

Cantankerous-connecting the 2 networks will cause errors seen past Tesira as run time faults. Dante Controller must be used to identify issues in Dante streams.

Faults

If there is a major fault where all of the channels in a Dante block aren't passing audio Tesira volition report "Ane or more Dante flows inactive".

Cross-connecting primary and secondary Dante networks will cause network faults and errors.

Further diagnosis of faults requires the utilise of Dante Controller.

Clocks

An extremely high-quality clock is provided past the Tesira backplane, the card bus references that clock for Master Clock duties within the network unless a higher priority clock is available, such every bit AVB (when present) or Dante. If these college priority clock sources are present and so Tesira'southward clock will sync to their clocks.

Dante clocking guarantees that all devices are synchronized to within 1 microsecond or less, and that all devices tin play out audio at the level of sample accuracy.

As with AVB, Dante uses a distributed Master Clock ballot protocol that automatically selects the all-time clock for the network, based upon information advertised by each Dante device. This information includes the quality of its clock, clock source, link speed and other parameters, and results in the best clock being elected as the Chief Clock. One device is elected as the Main Clock to which other devices are synchronized. Past default this choice takes identify automatically, with no need to manually assign a Primary Clock.

In the issue the Master Clock drops offline sound will continue to flow and a backup Master Clock will take over. If the Chief Clock fails for any reason, a new Master Clock will be chosen from the existing slaves within a few seconds. The transition from 1 clock master to the other does non result in whatsoever loss of audio. Slave devices "free run" during the period of master clock transition.

Well-nigh of the time, you practise not demand to be involved in the Master Clock selection process. Dante guarantees that the Master Clock device will be by default the strongest candidate.

To force a specific device to become the Master Clock apply the Dante Controller to set a Dante device to be "Preferred Master". If more than than one device is selected as the "Preferred Master", the device with the lowest MAC address will exist chosen during a clock election. Tesira will advertise its DAN-i cards every bit "Preferred Master" devices by default.

If AVB cards are present in a Server they will impose their clock on the Dante network. The DAN-ane in that chassis will show "preferred principal" and "slave to external word clock" in Dante Controller. Other Dante devices will be slaved to that "preferred master". In the issue a Dante device sees multiple "preferred primary" devices, the Dante devices will negotiate betwixt themselves to determine the correct "preferred master" device.

In a system with AVB and Dante cards the AVB network must provide the clock. (Tesira will negotiate this automatically.)

Dante cannot be used as a "bridging" protocol between 2 or more than Tesira AVB systems.

• AVB and Dante have different ballot processes to determine the clock main device in their corresponding networks. Dante allows an external clock to be imposed upon information technology, via the "preferred master" and "slave to external word clock" settings. For a Tesira arrangement with Dante and AVB, the Dante network clock main must be provided past a Tesira chassis with an AVB bill of fare.
• The AVB clock "Grand Master" Tesira Server does not need to have a Dante card installed. The Dante device with the lowest MAC address in an AVB-enabled Tesira will become the "preferred main" for the Dante network - referencing its clock from the AVB network.
• If an AVB card is imposing its clock on a DAN-1 carte du jour, and the Dante network is likewise imposing its clock on the card via another "preferred master" Dante device with a lower MAC address, a conflict volition outcome as we cannot strength non-Biamp Dante devices to submit to the Tesira media clock. Faults will be seen in this case. This should be considered during the design phase of a system.

Dante devices each comprise a very loftier quality VCXO clock, and are synchronized with one another over the network using the IEEE 1588 Precision Fourth dimension Protocol (PTP). This synchronization requires the use of Diffserv (DSCP) QoS with strict priority and 4 queues in the Dante network's switches.

The source of the Main Clock can exist:

• The internal VCXO clock generated within a piece of Dante enabled equipment, or
• An external clock source which is internally connected to the Dante device (e.g. AVB in a Tesira Server).

There are sure circumstances in which the automatic Master Clock selection may be inappropriate. For example, a organisation may have a device that is periodically continued and disconnected, e.thousand., an input to the network from a phase box or mixing console. This device may not be e'er present and thus would be a poor choice for a Master Clock. Using the Preferred Main setting in Dante Controller, you may designate as a Master Clock a device (or devices) that is ever present for the entire time that the network is required to function.

Slave to External Word Clock

A Dante device with "Slave to External Word Clock" prepare will use the external word clock from its host equipment to tune its onboard VCXO. A Dante device with this attribute set will go the PTP Master Clock, unless there is another Dante device present with "Preferred Primary" prepare.

Preferred Master

Sometimes information technology may be necessary to force a item device to provide the PTP Master Clock. A Dante device with "Preferred Master" gear up will always be chosen as the PTP Master Clock.

If a device set as a Preferred Master is added to a Tesira Dante arrangement, and that device's Dante MAC address is lower than that of the Tesira Server, it will become the Principal Clock device. Since Tesira'due south clock protocol requires information technology to be the Master Clock for the organization this scenario volition crusade a (major) system fault. The mistake can be resolved past unchecking the Preferred Chief selection for the offending device.

In a redundant network, the clock synchronization protocol operates over both chief and secondary networks. Each network will take a designated PTP Master Clock; unremarkably this volition exist the aforementioned device on both networks. If this is not the case (e.g. if a non-redundant device is designated Preferred Main) and then ane device volition bridge the clock synchronization information from the primary to the secondary network, ensuring that all devices derive their clock from the same source. Redundant PTP Slave clocks will synchronize their local clocks based on information from ane of the networks they are connected to. In upshot of a failure on i network a redundant device will continue to receive clock synchronization information over the other network.

Troubleshooting clock issues:

Supported devices are constantly monitored by Dante Controller to constitute the accuracy and stability of their clock synchronization with the Dante network primary clock. If a device clock is exhibiting significant instability, it becomes at risk of losing sync with the master clock, and Dante Controller can brandish a 'Clock Instability Detected' popular-upwards, identifying the device.

In Dante Controller a "Clock Instability Detected" popup indicates a network configuration or hardware result that is causing inconsistent bundle timing. For example:

Result	Resolution
Energy Efficient Ethernet ('Dark-green Ethernet') functionality is active on a switch.	EEE is a ability-management organization for Ethernet switches, and can easily interfere with clock synchronization. Audinate recommends that you avoid unmanaged switches with EEE functionality, and fully disable EEE on whatsoever managed switches.
At that place is a 100 Mb switch or link where a Gigabit connection is required.	If your devices require Gigabit connections, make sure there are no 100 Mb links or switches in the chain. Audinate recommends ever using Gigabit switches for network backbones.
One or more than of your switches are incorrectly configured, or are not suitable for Dante networking	Ensure that you are using switches that support QoS, and Dante traffic is properly prioritized.
Network stress from other sources.	If you are running traffic from other sources across the network, it may be causing bandwidth issues that are interfering with Dante parcel timing.
Excessive multicast traffic.	Using multicast flows where they are non actually necessary can overload a network, specially if there are any 100Mbps switches or links nowadays. Consider switching some subscriptions to unicast to have the pressure off the slower nodes in your network. The Dante multicast audio bandwidth for the network is displayed in the Dante Controller menu bar. Every bit a rule of pollex, total bandwidth utilization (including multicast and unicast) on whatsoever given link should non exceed 70% of the supported bandwidth for that link. Utilization in a higher place seventy% of supported bandwidth can adversely impact clock synchronization (especially if there is also non-Dante traffic on the network). It is too recommended (for this item issue, and in full general) that you lot ensure all your Dante devices are using the latest firmware, and that you are using the latest version of Dante Controller.

Latency

In Dante, variation in latency in the network is compensated for at the receiver. Each receiver has an Rx latency setting. This setting defines the latency between the timestamps on the incoming audio samples and when those samples are played out. The typical default latency for a Dante device is i ms. This is sufficient for a very big network, consisting of a Gigabit network core (with up to 10 hops betwixt edge switches) and 100 megabit links to Dante devices.

Dante uses a network-centric approach to synchronization using standard VoIP QoS to prioritize clock sync and audio traffic over other network traffic allowing synchronized playout over different audio channels, devices, and networks over multiple switch hops.

In order to bring latency downwards to the everyman possible values, a gigabit network should be used. This allows greater liberty to build a high performance, flexible network that maintains fantastic latency performance. Dante offers sub-millisecond latency for all products.

Latency in a Dante organisation is deterministic and guaranteed. Receivers that are listening to the same audio transmitter using the aforementioned latency value are guaranteed to exist sample aligned. A Dante receiver introduces an additional latency before playing out audio to account for delay variation in the network or cease device.

The Biamp DAN-1 menu supports 1 ms and 2 ms latency. The minimum latency available for a device connected to a 100 Mbps network port is i ms.

Adding new devices to a network does not affect the latency of devices already in the network. The latency of hardware devices does not depend on the number of sound channels routed, however some devices (due east.g. the Dante Virtual Soundcard) may demand to use college latency to reliably process loftier channel counts. Routing boosted audio channels does not modify the latency of audio already passing through the network.

Dante DSCP / Diffserv priority values when configuring QoS

Some switches require special configuration to recognize and prioritize specific DSCP values. The table below shows how Dante uses various Diffserv Code Points (DSCP) packet priority values.

Priority	Usage	DSCP Characterization	Hex	Decimal	Binary
High	Fourth dimension critical PTP events	CS7	0x38	56	111000
Medium	Audio, PTP	EF	0x2E	46	101110
Low	(reserved)	CS1	0x08	eight	001000
None	Other traffic	BestEffort	0x00	0	000000

Dante Virtual Soundcard Firewall Configuration

The Dante Virtual Soundcard communicates over UDP using the following ports:

• Dante Clock Synchronization: 319, 320
• Dante Audio Routing: 4440, 4444, 4455
• Dante Control and Monitoring: 8700-8704, 8800
• Dante Multicast and Unicast Audio: 4321, 14336-14600

jonesbuthent.blogspot.com

Source: https://tesira-help.biamp.com/Network_Considerations/Dante_Network_Considerations.htm