It sounds like the passwords are not to protect the software, but the use of the software. The place I worked last had quite a few DSPs, and we changed settings on them all the time. We didnt mess with the software itself, but with the settings that the software allows us to make. If that functionality is password protected, then do you really own your box? It sounds to me like you would have then bought the contractor an expensive piece of gear that they leave in your space.
What
DSP? Some of this depends greatly upon the device. With something like a DriveRack PA there is no real programming, it is mainly making adjustments to the fairly fixed internal programming provided by the manufacturer as an integral part of the device. However, with a MediaMatrix Nion, BSS London Architect BLU,
Biamp Audia, Symetrix SymNet,
etc. there is no inherent operating program provided with the device, when you buy the box itself you get a box and some software to create and manage programming but the programming is custom created for each application and not part of the box. Thus with some
DSP devices the program itself is not a part of the equipment
purchase, it is a unique creation and thus protected Intellectual Property.
However, even with something as simple as a DRPA, there is still the issue of the impact of any programming on the
system. For example, if you allow someone to access limiters you have lost the ability to control what happens with the related protection for any devices downstream. Just the eventuality of changes that could negatively impact the
system represent a risk for someone having to warranty the related components or
system.
Perhaps we can look at this another way. Sorry for the long diatribe, but this is an important issue. The argument is that buying a
DSP box buys you full access to the software/programming. However, buying a box really buys nothing other than what comes in the box and the manufacturer's standard warranty. No special support, no integration with other components, no setup, no related
system documentation, no training, no
system warranty,
etc., just the box and the default programming. However, chances are that what was purchased was an
operating system. In that case you have to look at the 'thing' purchased as being the
system and not the individual components. That usually includes integration with other devices,
system warranty,
etc. And that usually includes the setup of the
DSP as necessary to meet the project requirements.
An analogy might be a car. A modern car contains multiple programmable processors. What you get when you
purchase a car is those devices as integrated into the
vehicle with the user access defined by the party supporting those devices as far as service and warranty. Try asking Honda or Toyota or Ford or whomever for full access to all the processing devices installed in your car and the programming for them because you 'bought' that when you bought the car. You may be able to overwrite the initial programming, but typically with the
express condition that this voids all warranties. A sound
system is not that much different, you buy the component devices as integrated parts of a larger 'thing' and not as individual, unrelated parts.
And that is where the dilemma lies, the Contractor is responsible for providing a
system that meets all the project requirements and typically for warrantying that
system for some period. They also have their reputation tied to the
system. You can't hold the Contractor responsible for changes made by others and the only reason you would need access to a
DSP is to make changes. Thus the difficulty becomes how to balance access to
DSP devices with the Contractor's responsibility for the
system.
So the concept that you should be able to freely access the programming because you bought the
DSP device is false in two potential manners; the programming may not be part of the device and the device is not operating in a vacuum but instead is a component of the
system purchased with specific requirements and responsibility placed on the Contractor for that
system. I agree that the Owner (which is different than the end user, e.g. the school district probably owns it) should have access to anything necessary to support the
system in the future but you also have to somehow balance that with the Contractor's responsibility for the initial
system and warranty.