Archive
Loss of Connection Errors?
Why do we always start of with “it’s been a busy week”? I would hope we are busy or else someone out there will find our presence superfluous. Always wanted to use that word in a blog. I will say an average week with an interesting find, and we are only half way through the week! As we all do more and more IP based infrastructure, we get to troubleshoot more and more IP based issues. We send audio all over the place via IP these days, so when a codec reports an unusual amount of errors, even though it is not a main, you look into it. As we progressed to a MPX over IP solution, my audio codecs are still online as backups, and I do check these on my remote control for any anomalies. I saw one which was troubling, an excessive amount of Loss of Connection(LOC) errors.
As I saw these errors on both codecs, I began my investigation at the studio end in the comfort of my not so comfortable chair. Software reboot of both codecs was first. Hardware restart of the studio end codec. As it was due for a firmware update, I even verified this was up to date which it was. One of the last things I did before exiting for the day was to connect this codec to the backup codec at the site and see if I was chasing the wrong end.
Good morning, and time to check what the double hockey stick is going on with that codec. Interesting find: LOC errors were gone and the usually expected dropped packets, especially on the Internet side. Looks like a visit to the site.
At the site I did the same routine as I did at the studio. Another software reboot, then a hardware reset, and just a good head scratch as the errors continued to climb. I did a quick check of the switch and verified all other equipment had no issues, and I did not find any. So, I decided to do the tried and true of troubleshooting, and I reworked, exercised, and cleaned the ethernet connections both into the switch and into the codec. I checked for proper operation and began to monitor the situation. No immediate count increase, so looking good. As it is a transmitter site visit I did some routine cleanup. After that time where I saw upwards of 50 or more LOC errors before, none were recorded! Connector cleaning it was.
I checked when I got back and all good. As of writing, a few hours later, still no LOC errors. I will do my periodic checks, but it all looks like life is once again in balance. When tracking down and troubleshooting don’t forget to include connectors and connections in general especially at transmitter sites. Think about how many years its been since you have touched a connection at a site. Usually if nothing is wrong you don’t touch it, but if you have an issue, clean things up and get back to a clean base.
Dante Certified! Level 3
Just wanted to give a quick update. I just completed and passed the level 3 test online for Dante Level 3! Yeah!
I will admit it was not as “easy” as I would have thought with the amount of work done in our facility. I am happy that I did it! Confirms that I maybe possibly really know something, though may not be an expert yet!
If you are out there working your way through any cert or achievement, keep at it. It is well worth it and quite satisfying.
Cheers!
Audio Over IP (AoIP)-Dante
To Audio Over IP or not to Audio Over IP. That should not be the question. The answer is a definitive yes. This should be a decision of adding another layer to the arsenal of audio options toolkit. We all still need analog and digital audio. Just add IP to that kit. Of the options available, from proprietary LiveWire and Wheatnet, to what may be considered standard, the choice is yours. Do not be fooled by AES67 claims. Think about what you want to do and why. I chose Audinate Dante. It compliments what I have and moves us into the future. And for my system it is integrated with Sierra Automated Systems (SAS) 32KD and Bravo. (It even supports AES67.) Choose wisely.
I know you have read about AoIP. I know you know about AoIP. I know you use AoIP. Any modern codec is using AoIP as we all use the Internet to feed audio remotely. The basics of creating an AoIP network is simple. You need a network. The main part of this network is your switch. Do not use a hub. Make it a good switch. Design your network for at least 1 GB. Depending what you decide on a platform, you may need a DHCP server, and possibly some high-end switches. Some will want to Subnet and use VLANs on existing networks. I am of the belief of making things simple, so I chose to create a completely independent and isolated network. I chose Dante.
What makes Dante “simple?” Many things, but the main is the fact it does not require any special hardware. No special switches. No special configurations. In addition to that it does not require DHCP. The IP addresses are automatically assigned by Dante just like the automatic addressing Windows does when a DHCP server is not available. I chose to manually, or statically, assign the IP addresses. To manage Dante, the machine that has the Dante Controller has two NICs (Network Interface Card), so one is assigned an IP address for the Dante network. As the audio in the broadcast facility is contained here alone, there is not need for a gateway. I have 59 devices, so the assignment and manually configuring of the Dante portion may take time, but once it is done, it is done.
You ask about automation and playback computers. Two NICs. Ask me how many times I have been off air with this configuration. I dare you. Zero. Keep that in mind. Each machine has 1GB NICs. All studios have CAT6 cable home runs to the switch. Avoid multiple switches if you can. This is in line with keeping things simple.
And that is the basic framework that I use. Keep it simple. Don’t try and do too much at once. Get used to what you are doing.
Next post will be the basics of Dante. I will cover the Dante Controller basics.
In the meantime, check some Audinate links while you plan your system:
So You’re Adding Dante to Your Network?
Broadcast: Radio
Cheers!
Why Dante by Audinate?
I have mentioned Audio over IP (AoIP) in posts and on my site. I have been using AoIP for years to do remote broadcasts, normally using Tieline codecs, but have used others. I was one of the early adopters. I also decided years ago to run our studio to transmitter audio over IP. Due to space constraints and other factors I decided on the Worldcast/APT codecs. All have worked very well. When the stations had to move I wanted my AoIP platform to be Dante. I am glad I did.
There are three notable choices for AoIP on the broadcast industry: Dante, LiveWire, and WheatNet. Two of these are proprietary and do not have to pointed out. Only one, Dante, is an industry standard most notably in the audio/video industry and live sound. It is used worldwide in major venues. The list goes on and on. Just visit the Audinate Project Gallery. If you need devices and interfaces, why there are a whole slew of choices. Any time you need to interface, just check out their Product Catalog where you can research what you want, but do not pass over Audinate’s own devices, the AVIO adapters. Though I have not needed one, I think next year I will pick up a couple to have for the rainy day emergency! How could I pass on choosing Dante for my platform of choice?
Overall, the installation was a breeze. In my next post I will detail our basic installation, but for now just an overview. Though Audinate is designed to run on your existing Ethernet network, I am a strong believer in keeping mission critical separate, so I installed a completely separate network just for Dante. This makes life super easy as all you need to install is a good core switch and home run all your connections. At this point, as Dante will automatically configure its own IP addresses you can just let it happen. I actually manually assigned all IP addresses. Once you have a couple devices installed, you will see them populate in the Device Manager software. Using the Device Manager, make your audio connections and you are off to the races.
I am a Sierra Automated Systems (SAS) plant. With the new KDL modules and Rio Bravos, interfacing Dante to the routing system is quite easy. Again, you need to make your routes in the Dante Controller first, but once you have them available, that audio is not available in the SAS routers just like any other audio. SAS is working with Audinate such that they can control Dante routing through their system from my understanding. Seems like a complex challenge, but if anyone can do it, SAS can.
Stay tuned from my next post about the details of installing Dante, the devices, and configuration. Being an industry standard makes for easy integration with many devices. Mackie comes to mind. As for up-time, I have not had any issues with our AoIP setup. It works, and that is what counts.
AoIP: Dante by Audinate
Love it. Simple. Just build your network properly.
We are what I would say is 3/4 the way through getting these facilities in a psuedo-complete state. The one thing that I think has been the most reliable is our audio network, Dante AoIP. Simple, efficient, and easy to maintain. I need to do a count, but I am sure I have over 50 devices on this network/system. I know I am not done.
The devices range for KDL modules in my SAS 32KD frame, to SAS Rio Bravos, and a multitude of Dante Virtual Sound Cards (DVS). Using the Dante Controller application makes it very easy to setup, configure, and maintain. After putting all this fun stuff together I decided to visit the Audinate site and check with their online information. I decided to go through the steps and check out the training. I did all this just this past weekend. The end result: I have a Dante Level 2 certification.
I hope to catch up and spend time on some details on why I chose Dante, and how I implemented it. For now, know that I am a pleased Audinate Dante customer.
NAB Show 2014 Recap
Coming up on a month out and I have not even done a recap of the NAB Show! Well, that’s because most of the wanderings I did had to do with actual business this year. Odd, but true. I really could have used a third day this year as I did not even make it to the South Hall!!! Nor did I visit my friends at GoPro or DJi. Now that is what I call busy.
What I did see was the cool stuff that you probably already know about through trades or hearsay. I like the new Nautel GV series transmitters. Harris is also looking good and stepping up a bit. This time I was actually talking STL equipment with them. The Alliance had their share of stuff, and all they need to do now is make transmitters since they seem to do everything else. As you can tell if you have read this far, nothing really jumped out at me at this point. I did have a nice demonstration of the Tieline offering: the Codec Lounge. A very good concept and we discussed possible ways of making it even better. Maybe I’ll get a demo/beta version to try out. I also heard about the SAS Virtual Console of which I will get to see shortly. I have some ideas for this.
Of course on the Radio side of life is talk of HD Radio. HD this, HD that. As we progress with this technology I see more and more use of it as a data transport more so than audio. Traffic, weather, album art, artist and title. Wonder what else we can squeeze into 96kb, or 128kB? Did I get to see any demos? No. I saw a couple of cars out front, though. The one thing that stood out to me is that different manufacturers are offering different radios that do different things. My new Mazda6 has HD, but it does not do album art; it does everything else. A hand full of aftermarket have displays for everything, but there are many that do not. Will there ever be a “standard?”
Along the lines of STL’s (that’s Studio to Transmitter Links for the acronym challenged) I’m seeing more in the IP transport arena. We are actually researching upgrading our aural STLs to an IP based system for two reasons, flexibility and flexibility. Audio over IP on a private network is just fine these days and for a backup to anything else it is great. With all the data we push around with IP based remote controls and addressable transmitter equipment, the added flexibility of IP makes life much more simple. For audio I was looking a the Tieline and Worldcast gear. As for a system we are looking into the licensed 8, 11, etc. Gig radios and broadband data. Let’s see how that pans out over the year.
As we move forward what did you see that excited you at the show? Overall, not too much jumped out at me. Yet, on the face-to-face time, it was a very good show. Maybe next year I can get an extra day to see the other world of cool stuff in the South Hall.
Tech Notes from the Field 