jlaudon wrote:I will be the band leader for a big concert (2 nights in the Coliseum) here in HK (Canto-pop) in April. We will be doing about 40 songs (!), and for a number of them, I plan on running DP along with the band (I'll be using my G4 laptop and DP 5.13, mainly running one stereo mix of extra synth/string parts and a click track for the drummer - using my 828mk3). I also plan to bring my G5 Quad to use (either Mainstage or Jambalaya) my VIs.
Does anyone have any thoughts about how this should all work (will it work, stable, etc)? How should I set up DP (each song as a chunk, click track only to the drummer or the whole band, etc?)?
Thanks for any input.
Simplify as much as possible. If there is anything that causes trouble, remove it. Don't try to do effects in the box; save them for your soundman. Some exceptions may qualify there: Trim is often useful, and rarely causes delay or problems. Minimal MOTU EQ (not masterworks, but the regular kind) tends to be easy on the CPU and little delay.
Do entire show in one file, or at least entire sets. If you have a break for more than 15 minutes, you can load a different file. Have one short sequence output to headset for testing, just to see if everything is working. Then stop.
Use Chunk Chaining to cue the next chunk. Have it cue and stop. Then you trigger start with whatever way is convenient for you. Click track goes to conductor, but 2nd pair can go to drummer. Do a preparation click (3-4 beats) for each tempo change, fermatas. etc. Do that by creating 4 beats in the first measure of the new tempo, then shift backward with "preserve realtime performance" checked in the Shift dialog. This may take some trial and error.
If your lighting guys are up for it, you can do the light cues from DP. It's a lot of work, but it makes everything precise. Chances are your lighting guys won't like that idea, anyway, not to mention the hours of input time it will take to get it set up. Their instruments set up the cues. You just send out "go" commands for their cues. Each lighting instrument documents their MIDI cues in the manual.
I always ran a 2nd machine for redundancy. Never had to switch over, but it was there and ready for it in case one machine failed. We rehearsed banter for the audience while the MIDI director is frantically changing over to the other machine. Madonna's MIDI guy came up with a method of live switching so that she would vamp with the audience for a beat or two, and he'd call video and tell them to restart their timecode at xx:xx:xx:xx, and then they'd go on his cue. It was an elaborate setup with some proprietary boxes he had made for that, if I'm not mistaken. Anyway, his setup and methods were quite different. I just started each song on cue, and I never had a failure of any kind. But that's why I recommend keeping things simple.
Rehearse. I've done this blind with artists who didn't want to rehearse. It'll give you religion. Say no to guys who want to skip the rehearsal. Rehearse until you're comfortable.
Check cables before each set. You never know when someone has stepped on one, kicked something, yanked something, or powered off something. Check those cables. MIDI Time Code or SMPTE may or may not be necessary, depending on what you are doing and what machines must be synced to you. If you need it, study the sections in the manual on time code, and in the MTP-AV manual especially. Code is easy to do, but you've got to know what you're doing. the guys who will be receiving your sync will MOST LIKELY have zero idea of what you're doing or how it works. You may have to show them how to slave their machines to SMPTE, which usually isn't hard, but requires a few practical guesses. Once you've got speed, it's easy.
Anyway, it's easy to get carried away with the possibilities, but live and studio are two different things. Live has to work first-time; every time. You will not get the chance to "try it out" when the audience comes in. You've got to have faith in your system. Simple is good. I've changed things 3 minutes before showtime, because I knew my system and knew what I could do. If you do lights, and you re-order your chunks, you may find your lighting cues all screwed up for the next song. Just think everything through a dozen times and you'll be fine. Make that a dozen and one.
When there are stage events that must coincide with timing, insist that you're the guy who calls them. You've got the time right in front of you; they don't. I've had ego clashes with stage managers over that before, in which I always gave in rather than start a fight. The results spoke for themselves, and management would then step in and demand that I call the shots. If you can manage to get that control without a clash, it's always best for the guy with absolute accuracy to call the shots. MIDI time is absolute.
I often closed all windows except the Chunk window. Less chance of screwing something up. My chunk window was all that was on the screen, so I made it a full-screen window. The COMMENTS section beside each chunk gave me a place to write in dialog cues, or other cues, so I'd know exactly when to hit "play." Sometimes I needed to follow a part so that I could tell in advance where the tempo changes were going to occur. You should rehearse this to the point that you don't need to look.
Test your latency. Hitting play doesn't always mean the song starts right then, but hitting "pause" first, then play, then "unpause" will give a precise start when needed. If the band has to start on 1, then give yourself a blank measure for a clicktrack countoff. On several tours for which I was music director, there was a Yamaha Disklavier on stage. The soloist wanted something subtle to guide him at times. I came up with the idea of Controller 67, which invokes the shift pedal -- the unacorda. It shifts the keyboard, and he can see it, while nobody else notices anything. Plus his foot on the pedal gave him more confidence. Anything to help! Maybe there are MIDI lights that could flash with the click; I always wanted some, but nobody had thought of it yet, so we had to use other methods.
Just remember: practice for performance, and you'll be ok.
Shooshie