Re: Apple Airport Express + DSP
What if there's an issue and it surfaces during the next show?
Hmm - the luxury of not paying attention to a few details with an auto-configuration service and some eventual random hard to troubleshoot failure vs. the certainty that the equipment will work the same way every time, and if there is an issue it will be discovered the first time the equipment is used.
I know which one I prefer, and for mission critical stuff auto-configuration protocols have no place!
Sure, you probably have gotten by for years, and you may continue to do so. Still doesn't mean it's smart. I've had friends and even I myself didn't pay much attention to backups on my computer - until I had a disk go bad and I lost stuff.
It's the same reason you carry insurance. Not because you think it's going to happen, but just in case it does.
As for being a sound guy and not a network guy - there's a recipe for disaster. If you are going to rely on a technology, you need to at least take ownership of the most basic fundamentals for it. Were not talking mastering BGP over multi-homed redundant ISP connections here! It's friggin TCP/IP 101 - IP address, Subnetmask, gateway. Three pieces of information. How about introducing some standards. Standard networks - eliminates the subnet and gateway issue. Label your equipment. Eliminates the IP address issue.
Wow - that was hard. Yup, it may add a minute or two to your device setup - I'm sorry, I thought some of you were professionals? I may be amateur and part timer but I certainly understand the value of eliminating variables to further total system stability. Especially for something so trivial as to be completely laughable. As alluded to earlier, this is more a failing of process control on your part. The best way to experience predictable results is to have well defined processes - this simply becomes one more item in your process.
Good luck - I doubt you will change; you've already indicated as much. I just hope for your clients sake when one of those variables does pop up it and bite you in the ass that it does so during a sound check or some other non-critical time. And yes, I realize that there isn't infinite resources and an incremental cost to each step; I'm not being totally glib even if that's how I may appear to you. But trust me, DHCP issues are NO fun to track down when you have a couple hundred users staring at you, a wired network and a protocol analyzer. If your a sound guy in front of thousands of people with wifi and other crap in the mix too - like I said, I'll gladly shoulder the "burden" of "managing" static IP's for the overall stability. Think about your chief complaint for a moment - an issue with system setup. If there IS going to be a problem, quite frankly that's exactly when I would want to deal with it.
What if there's an issue and it surfaces during the next show?
Hmm - the luxury of not paying attention to a few details with an auto-configuration service and some eventual random hard to troubleshoot failure vs. the certainty that the equipment will work the same way every time, and if there is an issue it will be discovered the first time the equipment is used.
I know which one I prefer, and for mission critical stuff auto-configuration protocols have no place!
Sure, you probably have gotten by for years, and you may continue to do so. Still doesn't mean it's smart. I've had friends and even I myself didn't pay much attention to backups on my computer - until I had a disk go bad and I lost stuff.
It's the same reason you carry insurance. Not because you think it's going to happen, but just in case it does.
As for being a sound guy and not a network guy - there's a recipe for disaster. If you are going to rely on a technology, you need to at least take ownership of the most basic fundamentals for it. Were not talking mastering BGP over multi-homed redundant ISP connections here! It's friggin TCP/IP 101 - IP address, Subnetmask, gateway. Three pieces of information. How about introducing some standards. Standard networks - eliminates the subnet and gateway issue. Label your equipment. Eliminates the IP address issue.
Wow - that was hard. Yup, it may add a minute or two to your device setup - I'm sorry, I thought some of you were professionals? I may be amateur and part timer but I certainly understand the value of eliminating variables to further total system stability. Especially for something so trivial as to be completely laughable. As alluded to earlier, this is more a failing of process control on your part. The best way to experience predictable results is to have well defined processes - this simply becomes one more item in your process.
Good luck - I doubt you will change; you've already indicated as much. I just hope for your clients sake when one of those variables does pop up it and bite you in the ass that it does so during a sound check or some other non-critical time. And yes, I realize that there isn't infinite resources and an incremental cost to each step; I'm not being totally glib even if that's how I may appear to you. But trust me, DHCP issues are NO fun to track down when you have a couple hundred users staring at you, a wired network and a protocol analyzer. If your a sound guy in front of thousands of people with wifi and other crap in the mix too - like I said, I'll gladly shoulder the "burden" of "managing" static IP's for the overall stability. Think about your chief complaint for a moment - an issue with system setup. If there IS going to be a problem, quite frankly that's exactly when I would want to deal with it.