Reply to thread

Message

<blockquote data-quote="Chris Johnson" data-source="post: 120888" data-attributes="member: 975">Re: New Yamaha QL Console at FrankfurtCompletely agree Scott. By moving our audio onto these existing pieces of network infrastructure, we now need to not only be aware of those standards and how to verify them, but also how the two things (audio and IP networks) might interact.Fortunately, I have a CCNA, and spend a lot of my life dealing with network and comms issues, so I feel pretty well positioned to spec/troubleshoot these systems.When we had these issues, network &#039;health&#039; (cable spec &amp; verification, switch behaviour, etc...) were our first port of call, which is partly why some people near to these problems began to not think very highly of Dante. However, it became clear through various &#039;soak tests&#039; (running the consoles with audio and various configurations for several days at a time), that the issue was with the CL. Yamaha looked into this and were clearly working on it, as subsequent versions of firmware seemed to resolve the issues.Here is a quote from Yamaha&#039;s v1.61 Bug Fix notes:<ul>
<li data-xf-list-type="ul"></li>
</ul></blockquote>

[QUOTE="Chris Johnson, post: 120888, member: 975"] Re: New Yamaha QL Console at Frankfurt Completely agree Scott. By moving our audio onto these existing pieces of network infrastructure, we now need to not only be aware of those standards and how to verify them, but also how the two things (audio and IP networks) might interact. Fortunately, I have a CCNA, and spend a lot of my life dealing with network and comms issues, so I feel pretty well positioned to spec/troubleshoot these systems. When we had these issues, network 'health' (cable spec & verification, switch behaviour, etc...) were our first port of call, which is partly why some people near to these problems began to not think very highly of Dante. However, it became clear through various 'soak tests' (running the consoles with audio and various configurations for several days at a time), that the issue was with the CL. Yamaha looked into this and were clearly working on it, as subsequent versions of firmware seemed to resolve the issues. Here is a quote from Yamaha's v1.61 Bug Fix notes: [LIST] [/LIST] [/QUOTE]

Verification