Latest Project
by
on 11-17-2009 at 04:46 PM (990 Views)
With the group I'm currently working with, we have a unique problem that I haven't run into before. The cast of 5 players have "alternates" who will replace the main cast members from time to time, from just one player to all players. The combinations and permutations of cast members is a lot.
Some use wedges, some are on IEMs, although they are all currently "on their way" to using IEMS.
So, we had to come up with a way to have everyone's IEM and wedge mixes accomodated, no matter what combination of players are playing. It's extremely tricky, as not only do you need to change the mixes for the person playing, but you also need to change the other players' mixes depending on who they're playing with.
Add to that the need to make sure everyone has their latest settings. If one alternate hasn't played with the group in a month, it doesn't do any good to load the last setup that that player had since all the other players have had changes since then.
A way needed to be devised to pull in JUST the latest information for each player, based on who they are playing with. I needed to write a program that figures out what information to pull from previous setup files, based on what combination of players would be performing.
Turns out it's quite complex. Getting my head around "how it should work" took just as long as writing the program! Turns out you need to identify 2 things for each player: What channels do they "play" and what mixes do they "listen to".
For example, the bass player plays the bass DI & MIC channel and his vocal and the acoustic guitar. The drummer plays all the drum kit mics and the click. The bass player listens to his IEM mixes, and his wedge. (If he's an IEM user, the wedge mix is muted).
So you end up with this matrix of players, channels and mixes. I used a DataGridView to show it, with colour coding based on the player.
Add to that the complexity of 40+ scenes in the show and the fact that players move around on stage, singing into other mics than their own, playing multiple instruments. The "who's channel/who's mix" matrix had to store information for each scene separately as they can change.
So, the program is simple enough to use, but Very complicated to get the right information into it at setup time. Picking the correct "Who's" is quite tricky. Also, setup files have to have all matching scenes to work.
Anyway, it's custom made for our group, and I can't imagine trying to get it to become generic enough to release, let alone support, since the setup is so difficult to get right.
Good news is that it works perfectly if you do get it set up right, and I learned quite a bit more about Yamaha session (scene) files and some additional programming.
Here's a demo of how the program works:
http://checkcheckonetwo.com/files/FlexiCast_Demo.html
(Firefox users: http://checkcheckonetwo.com/files/flexicast.SWF)



Email Blog Entry