Los Angeles Performance Practice

Getting Your House in Order Before the First Rehearsal

Most people walk into a Los Angeles Performance Practice setup assuming the tech will just work. It won't. The first time I ran a full dress rehearsal for a multi-scene production at a warehouse space in Sun Valley, the ground loop hum was so bad you could hear it through the monitors even when everything was technically muted. Took me three hours to trace it to a dimmer rack sharing a neutral with the HVAC panel. That kind of thing happens constantly here because a lot of these venues were converted industrial spaces, not purpose-built theaters. The core workflow breaks down into a few phases that everyone glosses over until something breaks on tech week. You start with a strike and load-in schedule that actually accounts for LA traffic. A crew arriving at 6 AM from the Valley or Orange County needs different timing than one coming from West LA. I learned this the hard way when a lighting programmer missed his first cue-to-cue because he underestimated the 101 merge at Sunset. We pushed the session two hours and lost an entire day of rehearsal blocking time because of it. The second phase is tech prep, and this is where most groups fail. You need a detailed patch list before you ever plug in a fixture. I keep a master spreadsheet that tracks every DMX address, fixture type, channel count, and patch location. When a dimmer blows mid-show at a venue like The Echo or the ArcLight Hollywood (before it closed), you can swap the patch in under ten minutes instead of spending an hour pulling cables and guessing. Without that documentation, you're just winging it, and winging it in LA's short-notice rental market means you're lucky to get gear back the next day.

Third comes the integration phase. Sound, light, automation, and video need to talk to each other. SMPTE timecode is the standard, but not every piece of gear in a converted warehouse can handle it cleanly. I had a case where a Nino motion control rig wouldn't lock to timecode because the venue's power had 4% harmonic distortion on the return. The fix was a dedicated isolation transformer and a clock sync box on its own circuit. That's not in any beginner guide. It's just something you learn by showing up at enough problem venues.

Common Pitfalls That Wreck Productions

Permitting is the silent killer in Los Angeles. If you're doing anything involving street closures, outdoor performances, or structural rigging in a residential zone, you need clearance from the city and often the fire department. I've seen two productions shut down mid-rehearsal because someone didn't file a temporary use permit for a space in Downtown LA. The fines alone can exceed the entire sound budget. Budget six to eight weeks minimum for permit applications, and factor in a contingency buffer because the city of Los Angeles does not rush these things. Another issue is crew availability. The pool of qualified stage technicians in this market is smaller than you'd think. Good people get pulled into commercial film work that pays significantly more per day. When I was running a four-week resident engagement at a venue in Hollywood, I lost two of my three stagehands to a Netflix set within the first ten days. I had to promote from my electrician pool and spend three days retraining them on the show's specific cues. That's a real cost, both in time and in lowered quality during the transition period. Weather is a factor most people don't plan for. Outdoor performances in Santa Monica or Venice require wind monitoring systems for any overhead rigging. The first time I worked a show where wind speeds exceeded the rated limit for a flown scissor lift, we had twenty thousand dollars in gear that needed to be brought down immediately. Having a written weather protocol and a designated safety officer with authority to call hold is non-negotiable. I write this because I've seen it happen, and the aftermath involves insurance adjusters, not apologies.

What Actually Works in the Field

The workflow that survives repeated breakdowns is straightforward and boring. You build a show file in the same software version across all departments before load-in begins. If lighting is using Capture, sound is using Qlab, and video is using Resolume, those files need to be locked and shared on a common network drive by the time the crew arrives. I've cut my tech setup time from roughly four hours to about ninety minutes on standard club-sized venues by enforcing this discipline. The tradeoff is that someone has to own the coordination upfront, usually the stage manager or production manager, and that person needs decision-making authority from day one. For remote monitoring during strikes, I use a system built around Raspberry Pi units with camera feeds routed to a local tablet. This lets the production designer review set conditions without being physically present. It sounds like overkill until you're trying to manage a set change in a space with poor line-of-sight and limited crew. The setup costs around three hundred dollars in hardware and takes about two hours to configure per venue. It's cheap relative to the alternative of having someone physically run back and forth between locations twenty times during a scene change. When dealing with acoustically difficult venues, which is nearly every converted space in this city, I rely on measurement microphones and real-time analyzer software rather than gut feel. A REW (Room EQ Wizard) session takes about twenty minutes and will tell you exactly where your modal resonances are. Most engineers skip this and just adjust equalization by ear, which works fine in well-designed rooms but not in concrete-box venues with irregular geometry. The difference in clarity between the two approaches is noticeable within the first twenty minutes of audience seating.

When This Approach Doesn't Fit

There are scenarios where this level of procedural rigor actually slows you down. Small improv venues, pop-up performances, and experimental works that change daily don't benefit from the same documentation standards. Spending three hours on patch lists for a one-night showcase in a basement venue in Boyle Heights is counterproductive. In those cases, a simplified checklist approach works better, and the key is knowing which category your production falls into before you commit resources. There's no universal rule here, just experience telling you when to invest and when to conserve energy. Another limitation is the assumption that you have access to reliable vendors. In some parts of the city, particularly areas outside the central corridor, equipment rental turnaround can stretch to two or three days for specialty items. If you're working in Pasadena or Glendale and need a last-minute replacement component, you may not get it until the next business day. Building vendor relationships with companies in multiple corridors helps mitigate this, but it requires upfront time that many productions don't budget for. The model also assumes a certain baseline of technical literacy among crew members. If you're working with student productions or volunteer-run organizations, the gap between what the documentation assumes and what people can actually execute can be significant. I've adapted by creating visual cheat sheets and conducting fifteen-minute walkthroughs before each session rather than distributing lengthy procedural documents. It's slower per individual but faster overall because people actually understand what they're doing instead of guessing through written instructions.