In one of my Last projects we had eight stage boxes with one Yamaha CL5 console in a modern Cisco house network with two VLANs for primary and secondary Dante. One stage box was in another building in that area that was connected via 10gbit fire connection to the main building. We had two clock master units (one ‘in house’ and a second from that in a different building) in Dante controller although it was one network and that should not happen as I know. When we pinged the IP address of the stage box in the other building and it was around 400uS, but the Dante Latency tool showed up 25-35mS. How can that difference between ping and latency monitor happen and as a more general question: how can it happen that more clock masters appear in a Dante network?

https://www.symetrix.co/faqs/in-one-of-my-last-projects-we-had-eight-stage-boxes-with-one-yamaha-cl5-console-in-a-modern-cisco-house-network-with-two-vlans-for-primary-and-secondary-dante-one-stage-box-was-in-another-building-in/

This is typically caused by multicast traffic being filtered or blocked between to parts of the network. When this happens, the two parts of the network cannot "see" the clocks from the other part, and two master clocks are elected.

I’ve had issue where it was saying no more unicast flows left. I then turned the Rio box and other devices off, then turned back which allowed me to patch. Why was it not allowing more flows?

https://www.symetrix.co/faqs/ive-had-issue-where-it-was-saying-no-more-unicast-flows-left-i-then-turned-the-rio-box-and-other-devices-off-then-turned-back-which-allowed-me-to-patch-why-was-it-not-allowing-more-flows/

In most cases, Dante devices place four channels in a single flow. If you are manually patching a device, Dante will add four consecutive patches to a single flow (e.g. 1,2,3,4 then 5,6,7,8 then 9,10,11,12, etc.). Once a flow has…