How To Use Dante Devices in AES67 Mode with WheatNet-IP Devices

How To Use Dante Devices in AES67 Mode with WheatNet-IP Devices

If the Dante device supports AES67, this is how to integrate it into Wheatnet-IP:


NotesNOTE: The Wheatnet System must be running at 48K (Dante cards does not support 44.1 for AES67)

  • Put your Dante device on a static address in the WNIP subnet.
  • You need a PTP clock. The Dante device should provide this. Look in Dante Controller under Clock Status - as long as you have a Primary v2 Multicast Leader, you have PTP clock already. If not, you'll need a PTPv2 clock running in the WNIP subnet.
  • You will need to obtain a PTP license for Navigator (no charge) to lock the WNIP clock master to PTP.

 Then go into Navigator and go to the Info tab. Look under Clock Master Info.


Set the Primary External Reference to AES67-PTP. Navigator will prompt you for a license. Copy the seed and send it to us and we'll generate a key. no charge. After you have pasted in the key to unlock the feature, you will see the PTP Status go green. The domain should remain set to zero. If the status light for PTP is green, you're good.

Older versions of Navigator/Blade might not show the MAC address of the Grand Master (GMID) or show that it is locked, but the indicator will be green. That's okay. Newer versions of Navigator will show the green dot and display the GMID address and how long the clock master has been locked to PTP.

At this point, what is happening is that your WNIP blade that is clock master is locking itself to the PTP clock. All the blades will lock to the WNIP metronome from the blade, all of the AES67 devices will lock to the PTP clock, and everyone will be time aligned.

Next step is to turn on AES-67 mode for the Dante device in Dante Controller. In Device Info, double click on the device and choose the AES67 Config tab. Set it to Enable. There is a place where you choose the RTP Multicast Address Prefix. Dante only lets you change the second octet and it chooses the other octets randomly. WNIP is by default 239.192.192.0 and above. 


NOTE: The valid multicast range depends upon what kind of blades are in your system. Of the 23 bits available for multicast addresses, on Blade 3 hardware, the upper 7 bits are static in that they are fixed for all the addresses in a blade and the lower 16 bits can be anything in the 64K space. Blade 4 has the full 23 bit range, but if your system is a mix of Blade 3 and Blade 4 hardware, you must abide by the Blade 3 rules.
So, if there are any Blade 3 units in the system, the second octet needs to be the same. The default range of a Blade 3 system is 239.192.192.0 to 239.192.255.255. The stream you create must be within this range. Whether you are Blade 3 or Blade 4, the address you use must be within the range set in the Info tab of Navigator. Take care to choose address space that is well away from your blades.
We will need to create our own multicast address manually within the allowed range. To see what addresses are in use, click on the System View button in Navigator:

Then click on the Source Streams tab in the window that pops up.

Click on the Multicast Addresses tab to sort the list by address (tip, click it twice to sort in descending order) and look for an open range of addresses. In our example system, there are many open addresses between 239.192.195.167 and 239.192.255.240 so we can use something in that area.

Switch back to Dante Controller, and double click on your device to enter the Device View. Go to the Transmit tab.

We need to create a Multicast Transmit Flow, so click the Add button.
Change the flow to AES67. For Destination address, click Manual.
Enter a multicast address within the valid WNIP range that doesn't conflict. For port, enter 50100. Check to add both left and right channels to the flow.
Click Create. 

Now let's go to Navigator and create the WNIP source for the stream that we just created.

Go to the Devices tab (below System) and pick AES67 Devices. Click the Add button on the far right.


Give it a name. Fill in the IP address of the Dante card (NOT the multicast flow!). Give it a host blade. The sources and destinations for this device will appear grouped with the host blade in the crosspoint grid. Save.


Now in the system tree, click on the device you just created.


You want to be on the Sources tab, not the Destinations.
NOTE: We will not use the destinations tab to send audio to Dante devices. To send a WNIP source (including mix buses) to a Dante device, edit the source and check AES67 1ms Support to create the 1ms stream that your Dante device will use. Refer to the Navigator manual for more information on this process.

Click Add.


Give your source a name and then click on the Stream Info tab.

See how there's an entry there already? Click the Edit button so we can modify it.


Change the Multicast Address to match what is in your flow. In our example, we have a Multicast Address of 239.192.253.0 and a Port of 50100. Leave Payload Type at 100. The packet rate for the Dante card is 1ms. Ignore the section about Reference Clock, we don't need it.


Click OK. Finish. Now you can route the audio coming from the Dante card to a destination on a blade.

Repeat the process to create a multicast flow for each microphone/device and matching source for each flow. This will put Dante sources into Navigator so you can route Dante sources to Wheatnet IP destinations

On the Dante Controller side, you will use the External SDP sessions function.

Go to Navigator and find a source that you want to send to the Dante device. For example, we'll choose the Utility Mixer A output from a Blade.
Idea
As the Navigator manual points out, using a Utility Mixer to send audio to an AES67 device is handy, because you can use salvos, scripts, and X-Y controllers within WNIP to change the router crosspoints into the Utility Mixer, which is easier for board operators to understand and operate.
Notes
Most Blades default to creating .25ms packets; AES67 requires 1ms packets. On Blade-3 hardware, you need to set at least one Blade-3 to act as an AES67 translator to make a 1ms copy of the source for AES67 devices to use. Enabling the Translation feature on the Blade Admin tab will turn off the Utility Mixers on the selected Blade. The sources translated can be from any Blade-3 (not just the one where you turned on the translation feature), and the translator blade is capable of creating 8 1ms translations. Blade-4 hardware can do their own translations without using another blade as proxy because they are capable of processing more data.
Click on the desired source and Edit it. Check the AES67 1ms Support box, then click Finish.
Notes
This checkbox is greyed out when the source is routed to any destinations. To enable the feature, unroute the source, check the box, then route it back to where it needs to be.
Once you have clicked Finish, the translation has been created. Now we can create a SDP file to paste into Dante Controller with the source's information.
Right-click the source and choose Show SDP.

Since there are two streams for this source (0.25ms and 1.00ms), you will need to click on the 1.00 ms tab.
Click the Copy button. You don't need to highlight the text; we'll copy everything in the window for you. You can also click Save to save this to a file.
Now, back in Dante Controller, click the Add button. It will have a template of text that is highlighted. Paste what you copied from Navigator into this window to replace the template text. Click Add. Then Close.
A moment or two after closing the window, the source you just pasted in will appear as a source in Dante Controller so you can connect it to your Dante device.
    • Related Articles

    • Sample Rates and Clocking In WheatNet-IP

      en you installed your first Wheatstone Blade, you were asked to select a sample rate for that Blade. You either chose 48000 samples/second, or 44100 samples/second. As you installed additional Blades, you presumably selected the same sample rate for ...
    • Wide Orbit WheatNet-IP Logic Setup

      These instruction sets apply to WideOrbit Automation for Radio versions 2.x to 3.7.x. Newer versions are likely similar. WideOrbit can address SLIO’s on blades via the Wheatnet ACI. For this setup you will need WO automation for Radio Device Server ...
    • Wide Orbit WheatNet-IP Logic Setup

      These instruction sets apply to WideOrbit Automation for Radio versions 2.x to 3.7.x. Newer versions are likely similar. WideOrbit can address SLIO’s on blades via the Wheatnet ACI. For this setup you will need WO automation for Radio Device Server ...
    • WheatNet-IP Micro Blades Cannot Become Clock Master

      The WheatNet-IP Micro Blade, which is the WheatNet-IP card built into the Tieline Gateway, Eventide BD600W+, and Wheatstone Stagebox, is designed to only follow the WheatNet-IP metronome generated by the Clock Master Blade. It is not capable of ...
    • The Wheatnet-IP Meter App

      What is the Meter App? The IP Meters software for Wheatnet-IP gives you a fully customizable and nearly limitless display of meters from your Wheatnet system including but not limited to audio peak levels, average levels, signal density, FFT graphs, ...