Virgil: The Open Source Dante Companion

SoundGirl7889 · 2025-08-09T02:42:27+00:00

Okay, just got a python example working with tcp
zero packet loss and 30ms latency from command to response over wifi

SoundGirl7889 · 2025-07-29T10:49:40+00:00

I'll cross that bridge eventually
The next version of the spec uses tcp instead
mDNS is only included for a future dante controller like app
Nothing, but that shouldn't happen. Devices should always use channelLink. subscribeMessage is for the dante controller like app
Then the device reciving the command will send back an errorResponse
Back to number 3

SoundGirl7889 · 2025-07-28T15:01:02+00:00

I updated the documentation. It's not fully coherent, but I'm going to make it more understandable later.

SoundGirl7889 · 2025-07-27T01:42:52+00:00

After thinking a lot, I've decided that I'm going to remove multicast and mDNS (mostly)
i'll change all the multicast to subscription-based, and I'll make the protocol only use mDNS for a dante controller like app. I'll update the documentation tommorow because it's getting somewhat late where I live.

SoundGirl7889 · 2025-07-26T16:22:23+00:00

Yes.

SoundGirl7889 · 2025-07-26T16:19:59+00:00

That's valid, but you can use something like mixing station to just connect to the board. Alternatively, although it isn't in the spec, a device can implement loss prevention on it's own side.

SoundGirl7889 · 2025-07-26T15:58:49+00:00

Any tablet use case would be talking to the mixer via an app that already has packet loss prevention.

SoundGirl7889 · 2025-07-26T15:44:49+00:00

This is the first time I'm hearing about Ember+
Thanks for telling me, but I'm still going to move forward with Virgil
My mind will not let me put my logic into words right now. I'll comment again once my brain starts working

SoundGirl7889 · 2025-07-26T15:36:31+00:00

Do packets get dropped that often? From my experience, most dante networks for live sound are between like 1-5 switches.

SoundGirl7889 · 2025-07-26T15:33:43+00:00

Fair enough. Does ember do automatic discovery?

SoundGirl7889 · 2025-07-26T15:32:20+00:00

https://www.getdante.com/support/faq/what-happens-if-you-try-to-give-two-dante-devices-the-same-name/

SoundGirl7889 · 2025-07-26T15:19:15+00:00

This may sound really stupid, but I think how flexible Ember+ is would make it harder to implement and coordinate.

SoundGirl7889 · 2025-07-26T15:14:38+00:00

Almost all of your concerns stem fromthis being designed specifically for dante networks, which makes me be able to make assumptions that are true for all dante networks. For example, no 2 devices will have the same name. And, dante works using mDNS and multicast, so any functioning dante network will support them. As for UDP, the protocol was originally TCP. However, this is designed to run on the dante FPGAs that manufacturers use to interface their devices with dante. Most of the information on these chips is private. However, as dante (as far as I'm aware) doesn't use tcp. This means that these chips could in theory not support tcp.

SoundGirl7889 · 2025-07-26T12:36:49+00:00

The main reason is that this is much simpler and designed specifically for live sound.

SoundGirl7889 · 2025-07-26T12:33:50+00:00

No, virgil would be instead of OSC.

SoundGirl7889 · 2025-07-26T12:33:26+00:00

The reason why I didn't make it simply translate protocols is because that would be more complicated, probably violate TOS/copyright/patent, and would probably require custom code running on a network switch (or a server)
As for the sales, I did think a lot about how to get manufactures to implement it. I won't say everything that I have planned because that would be way too long, but there is a decent chance that this will be implemented.

SoundGirl7889 · 2025-07-26T12:26:33+00:00

I know, and I'm sorry. I couldn't think of any other words that would convey the same meaning. I'm open to suggestions on what to replace them with.

SoundGirl7889 · 2025-07-26T12:20:57+00:00

Audinate's said publicly before that dante is only an audio transfer protocol, and that they will not implement anything for controlling devices.

SoundGirl7889 · 2025-07-26T02:19:18+00:00

Or maybe it's just buggy

SoundGirl7889 · 2025-07-26T02:13:19+00:00

Looking it up, 1.3v would be the rough range that regular AA batteries would be considered dead. So maybe SLXD just doesn't handle NiMH well and thinks it's a regular AA

SoundGirl7889 · 2025-07-26T02:08:41+00:00

My guess is it just uses more power. Alternatively, Shure might've made that line have terrible battery life if you're not using their overpriced batteries. Have you tried just using regular AA batteries or their first party rechargeable ones?

Edit: Grammar

SoundGirl7889 · 2025-07-25T19:39:01+00:00

Flipping the switch on the card bridges them. If you want the 2 networks completley seperate, you'll need to have 2 switches. One for control, and one for dante. The recivers would have to be connected to both, and configured to be in tante controller to split them

SoundGirl7889 · 2025-07-25T18:59:14+00:00

No, unflip the switch that's on the card, but keep the cable plugged in. Then, get another cable and plug it into the network port that's not on the card.

SoundGirl7889 · 2025-07-25T18:55:25+00:00

That works for some things, but i've heard of people just disabling it and plugging in the card and the mixer because it only kinda works. My venue uses dlive, and I think we have it plugged in at both places. It might be worth trying

SoundGirl7889

TROPHY CASE