Hmm Toby not sure about the code release bit, someone writes an application, I install it and the desk crashes, not the fault of the factory, they are not responsible for it, chances of getting some recourse from an individual pretty slim I would have thought.
So my fault for installing it is the answer I guess, I could be left with a desk that thinks it is a toaster and a bill to get the factory to correct that if they will.
I know that is the dark side of it, just thinking aloud.
I would love to see an app that mainly focuses on Aux mixes for personal monitoring. An ipod touch is cheaper than an Aviom mixer, it would be wiereless control, and extra cabling to send audio from an on stage mixer to a wireless IEM or amp is not needed. This would also allow musicians to mix themselves, and the engineer can help/tweak their mixes if needed.
As this evolves, you could add administrative controls to the engineer, so he can assign mixes to people or restrict mixes from being changed from the app.
I could see this being an excellent value for churches or bands that have a low budget and can’t afford a monitor engineer.
API or control protocol documentation would be great. I would love to write my own app for this.
BTW I don’t think an API is a full code release, its just an interface for other programs to interact with. So in this case, we are talking about control protocol, which should not allow you to execute code on the device, just provide an interface to programmatically change settings, call snapshots, etc.
Yeah – I’m a software developer by trade. An api would let us make an iPod touch app (or any other app) that would let you sit stage side and tweak monitor mixes or something.
Lots of things to think about though – primarily the authentication model. It would be nice to allow plugins, though.
What about a single fader view with a tumbler to select the input/output/effects etc. channel you would like to work with and links to each processing section available for that particular channel (which opens a separate screen to view the particular processing eq, comp etc.). It will have to remember if the mix button has been pressed for any aux, matrix etc. so that assignments can be made by tumbling to the proper channel. The channels should automatically go to sends on faders(to save placing an encoder on the page) when an aux, matrix etc. is selected.The channel view should also have a button to turn on and off assignments. That should pretty much put the whole system aside from configuration on the iPhone, iPad or iPod touch.