What settings? The basic thing to try if having trouble is reduce the number of channels configured, and increase the latency. Also increase the buffer size in the ASIO settings.
That seems pretty optimal for settings. Have you tried any other software to try to isolate whether it is a system problem, or an Ardour problem?
My primary system is Linux, so I am a lot more familiar with the performance tuning there. There are some settings which may be possible to try in windows, for example using task manager to change Ardour to realtime priority (if it is not already, Ardour can use realtime scheduling itself in Linux, but I am not sure what the capabilities are on Windows).
Try 512 for the buffer size, not 2048. Going off memory Dante is VERY picky about that, which makes sense considering you can set dante to .5mS latency round trip or lower.
The virtual sound card has separate settings for Dante buffer size (shown as latency in the Dante settings) and ASIO buffer size. I think that indicates that the driver has extra buffering so that the application can only be called ever 2048 samples to refill the buffer, but the kernel driver will break that down into multiple smaller buffers to put in the network packets.
I’ve been testing severeal system, with different CPU and memory settings
last system is an HPZ4 based on a Core i9-10980
32GB of Ram
SSD System drive
Nvidia Quadro RTX 4000
this system should be powerful enough not to have any issues
however I’m experiencing exactly the same problem
it looks that there is some sort of incompatibility between Ardour and the Dante Virtual Soundcard
I haven’t run it in a while but I have run ardour and Dante on windows with no issues before other than as I mentioned above making sure to set my buffer to 512.
I use Dante and Waves Tracks Live (based on ardour) fairly regularly on Mac OS though.
Install DVS and set it up with ASIO, any kind of I/O or buffer
Install Ardour
Run Ardour and create a new session with the DVS ASIO audio device, any kind of buffer
When the session is runnig you will see that xruns are growing constantly
At this point just add an input with a Dante source connected (Dante rx 1)
xruns will stop growing and will never do it again!
So, since I was seeing xruns growing I’ve never tried to connect a source…
It looks that Ardour is having some issue with DVS until it do not receive a source
That makes perfect sense. The dante virtual device does not have it’s own clock source and relies on getting it from the network. If you have a dante network with only one device, that device is the network master clock. until you connect to it, the DVS has no clock and xruns are expected. Someone with better dante knowledge could likely be more specific.