i’m Max, i use an Avantis Solo since June, i have some troubles with Dante.
I use an Dante 64X64 Card an get some Clicks when i’m playing audio back in virtuell soundcheck mode.
I record these already with the Avantis and the Dante Card and there are no clicks in the recording when i’m listing it back direct in Nuendo.
I’ve set the Clock in the Avantis to internal and the Dante Card in the Dante Controller to Enable Sync To External and Preferred Leader.
What else could be wrong?
And the next strange thing, when I’m use my newest MacBook Pro 16" i’ve got some Tx Errors in the Status Bar (Dante Control, DVS) i’ve ordered a new Ethernet adapter maybe that could be the problem with the new MacBook? In the first described problem i use an older MacBook with i7 Chip.
If the clicks aren’t in the recordings, then you clock settings are probably OK. (If there was a clocking issue, it would likely result in clicks going out from the console which would be captured on the recording). Having too short/small a buffer setting can also cause clicking, so I would recommend increasing the size of the buffer (starting on the playback side of things because if the Dante card buffer was too small, you would likely have outgoing clicking which you are not). Also, the computer itself could be inducing clicking as it plays back the audio if the system isn’t powerful enough to handle the load. It takes much less CPU power to record multitrack audio than it does to play it back.
I don’t think you set Dante up right. You should NOT set Dante Controller on the Avantis to Enable Sync to External. Leave that off. It should be Dante as the clock source.
Make it the Preferred leader. Also you might have a latency issue causing clicks. Maybe check what it is and bump it up a little. 2 or 5 ms.
The way the OP has it set up, the console runs it’s own clock, the console’s Dante I/O card uses the console’s clock and then passes that clocking information on to the Dante network where the I/O card is the master Dante clock. This way, everything is clocking from the console’s internal clock. It’s also the way A&H recommends setting this up. I can see the value in setting it up like that because it allows the console to retain it’s own clock. If the Dante network takes a dump, it won’t be affected by clocking issues (or the potential loss of the clock completely).
Now I know some people swear they get better results by making Dante run a clock for the entire system including the console. Personally I have never seen a difference between the two ways of setting up the clocks however, and therefore I would tend to agree that A&H method is the preferred method.
Obviously it also depends on the situation. I am sure there are more complicated Dante setups that might require this to be set up differently.
I’ve updatet the Firmware of the Dante Card (Same Firmware, but it works now) and updatet the Mac to the newest OS and now it works without clicks and tx errors.
I have also had a Dante 64x64 on board for a few days. Unfortunately, I have massive dropouts in playback. Even if only one track is transmitted, the latencies are on the verge of dropouts. As soon as you open even one window in the computer, the performance collapses, although the processor is only used 12% according to the CPU monitor. It all looks like the ASIO driver of the virtual soundcard is causing a problem with Windows 11 or another installed program. I’m still searching, but it would be helpful if someone has had similar experiences and would like to share here.