This evaluation release will be delivered along with a time-limited Access Token (access_token.c), which is necessary to run the DAL library. This source file contains a cryptographic string, unique to your company and is used to provide proof of access to the Dante Application Library. The access token has an expiry time built in, and visible in the source file. After this time, you will no longer be able to use the DAL evaluation release. At this time we encourage you to contact your Audinate sales representative to discuss further access.

Please provide feedback regarding your evaluation of DAL via email with [email protected] or your sales representative.

• ETS-5467 / DS-2102: Changes to code protection for PTP libraries to prevent PTP process restart in certain situations.
  • Customer Impact: Ensures more stable and reliable performance
• DS-1153: mDNSResponder fixes addressing several critical security vulnerabilities
  • Customer Impact: Enhances the overall security of the system, and protects customer data

• N/A

• DS-521: If a Dante Via device is running on the same computer system as the DAL device and there are no other hardware devices to act as clock leader, the DAL device will not be able to obtain clock sync from the local Dante Via clock leader. Workaround: Add a Dante hardware device to the network, or run Dante Via on another PC system.
• SAG-1244: When running DAL with a private instance of mDNS Discovery on a Windows computer, Dante Controller might not correctly show the DAL device. Workaround: Restart the ConMon service and Dante Controller.
• SODA-1324 / DS-698: The “rxname” and “txname” command line arguments in the C++ examples are incorrectly interpreted when run in Windows Powershell. Workaround: Run from Command Prompt or your IDE.
• HD-222: In specific installations containing Crestron UC-160 running Windows 1803, audio stalls have been observed after continuous runs over multiple days in networks under load. The issue is possibly related to Windows high resolution counter peculiarities on specific hardware platforms. Symptoms include:
  • All DAL RX packets are late (with avg. and max. close to the same value)
  • All DAL TX packets are early (absence of latency data or consistently late latency data)
  • Restarting DAL does not fix the issue
  • Workaround is to upgrade to a newer Windows version.