At the unveiling of our new product releases and updates at ISE 2014 in Amsterdam, we received the expected response for our DAN-1 Dante networking interface card: “Yeah, cool. This is great, I can definitely use this today. Now, tell me about TesiraFORTÉ. When can I register for training?” (The answer to that is March 3rd, by the way.)

We created the DAN-1 because our integrators are not only still installing audio systems that run on Dante networks, but also because their customers are locked into existing legacy systems, infrastructure, and licenses that don’t necessarily make it cost-effective for them to switch networking protocols at this time. By giving Tesira the added capability of running Dante protocols (it can already run CobraNet® with our SCM-1 card), our integrators can prepare their customers for the future of audio networking, while simultaneously supporting their current investments and legacy systems.

DAN-1 Dante Network Interface Card

DAN-1 Dante Network Interface Card

As networking needs continue to expand across installation environments, audio system architecture will have to be able to flex in response. We see this happening now, and we see it picking up speed with each new industry innovation. In response, and again, part of why we created the DAN-1, Tesira SERVER and SERVER-IO can accommodate multiple networking interface cards that allow end users to monitor and control AVB, Dante, and CobraNet networks within a single chassis. The audio channel counts (420 x 420 for AVB, 64 x 64 for Dante, 32 x 32 for CobraNet) remain the same.

Networking in Tesira SERVER

Within the Tesira SERVER chassis, you can have up to two network interface cards, one of which must be an AVB-1 interface card. The other card can be either the DAN-1 card or the SCM-1 CobraNet card. Both networks can be monitored and controlled via the same third-party control devices or a Biamp Canvas control file.

SCM-1 CobraNet Network Interface Card

SCM-1 CobraNet Network Interface Card

Also, that second slot doesn’t have to have a networking card, it can be left blank and filled-in later, or be configured with any of our analog or telephony cards.

Networking in Tesira SERVER-IO

Within the Tesira SERVER-IO chassis, you can have up to three network interface cards in any combination as long as there are no more than two of a kind. For example, you can have:

  • one AVB-1 card,
  • one DAN-1 card, and
  • one SCM-1 card within a single SERVER-IO.

All three networks can be monitored and controlled via the same third-party control devices or a Biamp Canvas control file. You can also have:

  • one AVB-1 card and
  • two DAN-1 cards.


  • one DAN-1 card and
  • two SCM-1 cards.

There cannot be three of the same card in the chassis. Other than that, any combination of the three is possible within in SERVER-IO.

AVB-1 AVB Network Interface Card

AVB-1 AVB Network Interface Card

(Note: While a combination of the three networking protocols can be run within a single Tesira SERVER or SERVER-IO, Tesira devices still only ever communicate with each other via AVB.)

The Long & Short of 3 Networking Cards in 1 Chassis

The ability to monitor and control all three networking protocols in a single chassis gives our integrators the ability to prepare their customers for the future, and it gives their customers the ability to leverage the power of Tesira DSP technology. Now, your customers no longer have to choose between the three, and potentially sacrifice system functionality: they really and truly can have it all.

When/if they decide they want to switch from one protocol to another, or that they want to streamline them all onto AVB, they can–easily and without having to invest in new network infrastructure. The cost would be that of the necessary card(s) and the labor of their friendly, neighborhood audio integrator. It’s a recipe for audio networking success. That’s what we were going for.

One thing we’d like our integrators to specifically keep in mind is that there will be specific clocking requirements that will have to be addressed. The SERVER and SERVER-IO will need to be specified as the master clock during setup. Our applications engineers are here to support you should you need help with this.

Next week’s post will be about the inside of TesiraFORTÉ by our newest blog contributor, mechanical engineer Kim Porter. Trust me when I say you won’t want to miss it.