Dante Via v1.4.0.5 (Windows)

What's New

• Support for Dante Director
  • Dante Via devices can now be enrolled in Dante Director sites
• User interface updates
• Security updates

Bug Fixes

• DS-2119: Missing access control request after unlocking device
• DS-2093: Fix endpoint text warning overlapping with device name
• DS-2084: Access request popup sometimes not showing when making subscription
• DS-2081: Notify user that only 48k devices will appear in the UI
• DS-2080: Some strings are truncated when the device or endpoint names are too long in the Access Control Request message
• DS-2078: "Enable Dante" and "Stop" texts are cut off on Windows at 150% Display Scale
• DS-2069: The channel count for Dante Via Device doesn't go down to 0 even after all channels are disabled.
• DS-2068: Subscriptions made in the Via UI may use the wrong channel names
• DS-2049: Update aud_utime_get calls to aud_utime_get_for_timing/reporting
• DS-1970: Windows Via Session Manager crashing
• DS-1944: Handle the ProcessIsRunningUnderCurrentUser exceptions better
• DS-1882: Windows UI Audio device description string can be too long for the UI
• DS-1860: Migrate Via binaries from 32bit to 64bit
• DS-1857: Spamming stop/start on audio app can force a restart of the Windows VSC
• DS-1853: Update / replace licenser app with latest version
• DS-794: Non-default date-time format can crash Via UI
• DS-524: Keepalives are impacted by large wall-clock time changes
• DS-511: Disconnecting from a Remote Desktop session while running Dante Via may cause the Dante Via Session Manager to crash
• DS-347: Add conmon srate and encoding messages but with FIXED mode
• DS-30: If selected network interface is missing on Via manager startup, it remains unselected when available
• DS-29: Unable to launch DanteViaScbHelper if the username has a space in it

Known Issues

New known issues (v1.4.0.5)

• DS-2125: Via doesn't show up in Dante Controller immediately after the valid interface is selected for the first time.
• DS-1874: New Warning message showing in Dante Controller with a self-subscribed Via device
• DS-2130: If after a computer reboot an audio application starts playing audio before Via, Via will not send or receive audio for that application. Workaround: Restart Via.
• DS-2270: Via audio occasionally fails to recover after restarting Via. Workaround: Change the default audio device to another output and then switch it back to Via. This restores audio output.
• DS-2135: Dante Devices enrolled in Director do not reappear in Via if the Ethernet cable is unplugged and the interface is changed. Workaround: Restart Via.
• DS-2239: Audio Devices do not always enable automatically when 'Make Audio Devices available on the Network automatically' is checked. Workaround: Enable the audio devices manually if they are not already enabled.

Pre-existing known issues (v1.3.2.1)

• VIA-2354: Duplicate application names can cause duplicate channels on the Dante network.
• VIA-2641: Subscriptions between Dante Via devices may not automatically recover after rebooting DDM. Workaround: Resubscribe the affected channels.
• VIA-2642: Enrolled Via starts up unenrolled if restarted with DDM offline. Workaround: Stop and restart Dante Via.
• VIA-2639: When enrolled in a domain, Dante Via might not display the correct domain manager hostname if it has changed.
• VIA-2612: When two (or more) network interfaces are available on the computer, Dante Via may still appear on the network that is not currently selected.
• VIA-2582: Application icons in a multi-channel device are sometimes not displayed correctly if subscribed from Dante Controller.
• PP-26: Avast Business Antivirus can prevent Dante Via from installing correctly. Temporarily disable Avast to install Dante Via.
• PCS-623: The click, response area of buttons on the Dante Via UI can move as Windows screen scaling increases beyond 175%
• PCS-2573: Windows can block the detection of audio applications on the Dante Via Virtual Soundcard. If Dante Via is the default soundcard and it still cannot detect audio applications correctly, please contact Audinate support for more information on a possible fix.