So, at my church, like practically every other church in the world, we have a sound system. (It seems that churches that meet in barns in third world countries somehow manage to afford at least a microphone and a speaker or two.) Our church currently uses a Behringer X32 along with a PowerPlay P16-D and a series of P16M’s for the band members’ personal monitoring.
I’m a big fan of personal monitoring
for a few simple reasons:
- I don’t like mixing monitors:
- Musicians know what they want, I can only guess (I guess fairly well though).
- Everyone seems to like different mixes each week.
- I can’t hear myself (you just woke up, you are quiet)
- Adjusting mixes when everyone is getting started wastes precious practice time before any given service.
- This is true not just at my current church, but also each of the 4 churches I have previously attended. (1 growing up, 3 during college)
- I don’t like extra stage noise.
- We already play our music “loud” through the mains, but any extra noise from the stage makes things unbearable.
- Room dynamics change between practice and the actual service.
- I may be blowing smoke here, but a room full of people sounds different.
- Musicians play differently when a congregation is present.
- They deny it, but it is true.
- If the lead guitar player is suddenly playing louder, the keyboard player will want to be able to quiet it in their mix.
- This NEVER happens in our church.
Back to the technical details
I mentioned that we use the Behringer system. The P16 is pretty neat because it is cheap ($250 / person) and quite easy to use. We had to buy a “distributor”, the P16-D ($100), which is basically an Ethernet switch that has PoE to power the P16-M’s. For what it does, I think the price is fair.
Of course, when you buy into something that is cheap and affordable, you quickly find out why… there are a maximum of 16 channels in the P16 system. For reference, the X32 is a 32 channel board. Musicians (the collective lot of them) can mix from 16 of those channels + busses that we choose at the board. Put another way, the drummer doesn’t get fine-tuned control of the drums because it would occupy half(ish) of the channel count for the rest of the band. To resolve this, we made a sub-mix of the drums, one for background vocals, one for speaking mic’s (we have maybe 3?), etc.
Why don’t I like this? I don’t like this because even though we have spent almost $2K on the personal monitor system, I still find myself managing too much of the monitoring.
Enter the X-Touch Mini
The X-Touch is a $99 midi controller that has, I swear, just as much control surface as the P16-M in a Midi controller. With what looks to be 2 layer selection buttons an 8 rotary knobs, it has the potential to control the same number of channels as the P16-M. My plan involves a more complicated setup than the Plug-And-Play nature of the P16 though. Midi controlling and routing would have to be individually setup for each controller to select what knobs on each layer control for each musician. That ain’t easy from what I can tell. Additionally, the midi controller route doesn’t provide any actual audio output for headphones. We’d need headphone amps and enough outputs for the band in addition to the Foyer speakers, L+R+C+S and the video send. I believe the system handles 16 outputs, leaving us at 10 for the band. Manageable, but barely.
However, I AM a software engineer who happens to have hardware design experience and I can solve problems like that. I’m imagining a bridge between either MIDI or USB(USB MIDI) to an IP network for each controller. These would all communicate (probably through a http RESTful API) to a controlling software that performs the mapping from the Controller to the X32 (basically, assigning a given control command from any X-Touch to the specific contorl command on the mixer.) The mapping would need to be easily configurable by the musicians, probably with a mobile webpage accessible from a phone. The remaining task would be to actually send the mapped control data to the X32.
This is where the real power comes into play. The X32 can now be replaced and the only piece that needs to change is the mapping. The control surfaces on the stage can stay the same. I don’t know of a single commercial system that can manage that. Especially for the price.
So, about the implementation, how is it done? Well, Intel has done most of the work for me at rather reasonable prices. Enter the Galileo ($60) and Edison ($50). Each are x86 machines that can talk USB and IP networking.
The Galileo is ready to use with USB Host and Client, as well as 100MB Ethernet. It is WifFi ready when a $15 mPCIE card is added. A few bucks more and you get Bluetooth with the WiFi.
The Edison is brand new as of this month and requires a bit more work. It is a module that can be added to larger boards for power delivery and interfacing. It has no Ethernet options, but has WiFi and Bluetooth built in. USB OnTheGo (host or client, not both) is similarly an add-on option.
With the multiple needed add-ons of the Edison, the Galileo becomes the more ideal choice for me. Here’s how it would be set up:
- X-Touch mini -> Galileo via USB.
- Stage Galileos -> central Galileo via IP
- Central Galileo -> X32 via USB
The Galileo would have code (C, python, Arduino sketch, whatever) to packet-ize the MIDI data and send to the central controller. Communication is either Ethernet or WiFi. Both have similar cost because cat5 isn’t free and neither are the necessary switches. I’d expect similar pricing to a WiFi card. It would be a close decision, but there is still power delivery for the board. The latest version of the Galileo has an option for PoE, which would be very convenient and probably worth any added cost, just to avoid the wall-warts all over the stage.
Now for the “central controller”. This would also be a Galileo board, acting as a computer to talk MIDI directly to the X32. it would be connected to the network via cat5 and powered with a wall-wart since the wiring in the booth is already a mess and always will be.
looking at the cost per musician (not including centralized costs), the
- P16-M $250.
- Custom design:
- $99 (X-Touch)
- $20 (enclosure, estimated)
- $15 (overpriced headphone cable)
- Total = $209.
My custom solution wins the per-musician cost breakdown.
Moving on to the centralized (one time) cost:
- $100 for the P-16D to distribute and power the P16-M’s on stage.
- Custom design:
- $60 for central Galileo
- $150 Behringer Powerplay Pro-8 HA8000
- Headphone amp for 8 musicians
- Network switch. One of:
- $100 8-port PoE capable switch
- $25 8-port (non-PoE) switch
- Total = $235 – $310
P16 wins this regardless of the WiFi / PoE decision
The real cost is found in the development of a software solution that I don’t think exists yet. To be honest, I already volunteer at church so much, I would hardly notice the additional effort.
I think I’ll start on this sometime soon. I already have 2 Galileo boards, so I’m looking at a $99 investment at this point.
Ideally, if the Galileo was audio capable and someone added a network driver to the Linux kernel that the X32 used, the Galileo would get a straight digital send from the X32 ,reducing the total cost by $150 and allow for > 10 musicians. But alas, I don’t expect such a nice setup anytime soon.