Search the Community
Showing results for tags 'dante'.
We have a system using the Focusrite RedNet Dante card. It works in 6.2.2 (although we have other audio issues), but we’ve tried upgrading to 6.5 and 6.6.5 and we get no output. We've confirmed sample rate is 48kHz on both the production and display computers. ASIO4ALL seems to have the same issue, but direct output from the sound card seems okay.
Has anyone successfully outputted multi channels of audio out of Dante Virtual Sound (DVS) card using WATCHOUT? I am doing a large museum exhibit that has its audio system set up using a Dante and I have six channels of audio that I’m trying to push from a WO server computer using the Date Virtual Sound card, which is digital audio over IP using a second NIC on the WO server PC. I have done multichannel analog audio with WO many times, but using Dante and WO I can only access one stero pair at the same time. In the WATCHPOINT software on the server computer I can pull the audio device men
I just had an opportunity to use some Dante AVIO USB Adapters. They are an outstanding plug-n-play audio solution. I'm seeing more and more audio professionals in the live event and permanent installs using Dante. With these dongles, you don't have to mess with nic card issues or load software or drivers. They have a small form factor, simple plug-n-play and WATCHOUT sees them as a Dante USB Transmit(Dante USB I/O Module) [WASAPI]. They are limited to two channels for each USB dongle. If you need more Dante audio channels then the USB to Rj45 converter is the way to go, but that requ
Hi, I have tried to install the Dante Virtual sound card on a WO display computer in April 2012. The display computer had 2 physical ethernet ports on the motherboard. One was used with a separate gigabit switch for the Watchout network exclusivly, the other one was used with a different gigabit switch for Dante. WO IPs were 192.168.x.y Dante IPs were 169.254.x.y (thats what they default to, its a feature not a missing DHCP). Subnet mask on both interfaces was class b or c / 255.255.0/255.0. So from a networking standpoint all WO traffic should have been routed to interface 1,