HAVE A FLEET OF CODECS? DO THIS.

If you have a fleet of codecs, you’re either dealing with a lot of live sports or news feeds coming into the studio or you’re really into logistics. 

A02_2 AES67 INSIDE BADGE 2560

We’re going to assume it’s both, in which case you might want to manage all remote resources through one GUI and control all those audio connections through AES67 connectivity. If you’re a WheatNet IP shop, for example, managing codec properties through a WheatNet IP audio networked touchscreen (built with Screenbuilder tools) and using AES67 as the connectivity standard for all audio channels (available in our Blade 4 I/O unit) means you can easily manage multiple codecs for the same event.

A good example of this is a live sporting event, in which you might have a codec for the play-by-play, a codec for the nat sound, and a codec feeding the venue’s concourse plus the codec for affiliates. Or, as Brian Oliger, CBT, CBNE, explained in an interview for Radio World’s ebook Trends in Codecs 2024: “Having all these codecs visible in the same [Comrex] GUI allows the producer to switch easily among them to make or drop connections, monitor network conditions and audio levels and change codec profiles as needed.”

Oliger is the Technology Manager for Hubbard Radio’s news station WTOP in Washington, D.C., which is using Comrex’s Access Multirack codec units integrated into a busy WheatNet-IP audio networked news complex of 50 workstations.  

Combining codecs with AoIP routing, control, and AES67 connectivity, all managed through one GUI, can go a long way in managing a fleet of codecs.

As we embark on a new year here at Club Wheat, we hope you'll come along with us by clicking on the SUBSCRIBE button below to begin receiving Wheat News in your email inbox every month.