Right now the way users work in OneMix is you log in to the DLive as an admin user, configure OneMix for a particular mix, then log out and log in as a standard user which locks out OneMix from affecting other mixes. This is marginally acceptable if a set of IPads are owned by the sound company (or church in our case) where you can pass out the “bass” ipad to the bass player, the “keys” ipad to the keys player, etc. This breaks down when users bringing their own ipads, as they may not always end up on the same mix. For example, if a user is sometimes vocal 1 and other times guitar 1, their prior OneMix setup will point to the wrong mix and you need to delete the whole thing and start over with the correct mix, which requires logging in as admin, deleting the mix, adding a different mix, logging out, and in the process losing any custom fader setups.
The better solution for this is for the MixRack to store the OneMix configuration so that you can define users on the mix rack and give them permissions to the appropriate mix. For example, the DLive has users for bass, vocal 1, vocal 2, etc. which grant permission to a matching mix bus. When a user logs in to OneMix as the “bass” DLive user, OneMix automatically loads the correct mix.
Right now we can’t really use OneMix, and we have multiple copies of MixPad running, which is a bit risky. We aren’t worried about malicious changes, however accidental pressing of buttons could happen.
