Re: Midas Mixtender iPad App
Last weekend was time for me to "pay up" with the coke. I had suggested there was no way the Gen II software would be seen this side of July. I was wrong. Its now installed and running on both our XL8 consoles. So here is the evidence of the pay-out
.
Its a good thing Coke was on sale at the local supermarket that week!
I had a reasonable look at Gen II over the weekend, with two "shows" on Sunday. As noted above, the main drivers for us was the ability to use Mixtender iPad app. But of course it comes with other changes/enhancements from the original software version. Here are my initial thoughts:
Changes:
- Attenuation level displayed on the channel/VCA select button when the fader is touched - handy addition
- Some different effects. Have not had a chance to investigate all yet, but the delay sounded nice. Might be able to retire the outboard D2 now.
- Shutdown process is pretty - "DO NOT POWER OFF" -> "GOODBYE"
Losses:
- No longer able to Copy/Paste between individual channel - or at least we could not find it
Additions:
As the sole operator for the first event, being able to unmute channels and adjust foldback/monitor levels from on-stage was wonderful. Then once the musos were happy, I could wander back to the mix/op position and set the FOH mix. saved a lot of walking back and forth, resulting in one of the most efficient set-ups ever. With simple events with up to 8 monitor sends we generally fun monitors from FOH and just "pass-through" the Monitor desk without a separate monitor operator.
Second event we had two ops, but still used FOH console for monitors. I set Foldback/Monitor from on-stage, controlling the mix on the FOH desk while Scottie (on the left in pic above" set FOH and Jono (on the right in pic) drank Coke. Jono had "played" with Gen II and Mixtender on Friday so Sunday was our turn.
I found Mixtender very good for its intended purpose. Its not meant to provide full control over all aspects of the console. But it does allow simple max level control, channle mute/unmute, visual feedback of levels, and control over the patched graphic EQs. However, there are a few things that would be great to see in an updated version which would make it an even better app:
1. When in VCA view, selecting the VCA "button" at the top of the fader would be really nice if it took you to the equivalent of the VCA population group view of the channels in the VCA group. Eight channels at a time is ok and swipe to view more if there are more than eight channels in the group. I know the intention is not to "mix" FOH from Mixtender, but when common sources are in a FOH group (such as Drums/Kit, Vocals, Strings, Brass etc) and not necessarily in grouped or consecutive input channels, then finding them via the VCA selection can be a lot easier.
2. The ability to select an input channel and adjust Gain, EQ, Compression and Gate thresholds. This obviously add complexity to the app, but would be great functionality. I like the touch/drag EQ adjustments on the Yamaha StageMix app. Compression and Gate controls really only need the thresholds and not full configuration capability.
I have yet to set-up the Mixtender connection for the Monitor desk. I was originally thinking it would require its own separate SSID and IP Subnet (same AP and LAN switych using different VLANs for each console). Is there any "best practice" for this? Should we just run them both on the same IP subnet/SSID or keep them separate?
It would be nice to be able to provide iPad access to performers to adjust their own mix. However, I need to spend a little more time with the app to understand how best to "protect" FOH and other monitor mixes from performers self-mixing their own foldback. The "Lock Mix" and "Lock Navigation" under Settings are the obvious components to this protection. But I have yet to understand the function of the password and the "Allow Select" option. Is there any documentation available such as a User Guide for Mixtender?
Overall I am really happy with Mixtender and so far the Gen II code seems to be behaving itself - always a risk with new code. Keep up the enhancements.