Lighting a bar without a lighting tech

Venue lighting fails in a predictable way, and it is almost never the lights. Someone capable sets the rig up, learns where everything lives, runs it beautifully for eight months, and then takes a job somewhere else. The week after they leave, the room settles into whatever look happened to be on screen when they last closed the laptop, and it stays there for two years. Nothing broke. The knowledge left the building.

So the useful question for a bar, club or small venue is not "what is the best look I can build?" It is "what can the person on shift next Tuesday do with this, having been shown it once, at the end of a busy night, by someone who has already mentally resigned?"

Who are you actually designing this rig for?

Design the rig for the least confident person who will ever touch it. In a venue that is usually a bartender halfway through a shift, with one hand free, no lighting background, and no interest in acquiring one. Every choice you make in the software should be judged against that person, not against what you personally can do with an hour and full attention.

This is a genuinely different design brief from the one a touring operator works to. A touring operator wants depth: more scenes, more control, more nuance. A venue wants shallowness on purpose. The best possible outcome is that nobody ever has to think about the lighting again, and the second best is that thinking about it takes four seconds.

The practical test is simple. Sit someone from the floor staff in front of the laptop, say nothing, and ask them to make the room look right for 9pm. If they hesitate, hunt, or open the wrong thing, the problem is your layout rather than their competence. Fix the layout.

How many looks does a bar actually need?

Most venues need between four and eight looks, named after the parts of the night rather than after what they do technically. A staff member can hold six names in their head. They cannot hold sixty, and a scene list with sixty entries is functionally the same as a scene list with none, because the search cost is higher than the perceived reward.

Name them the way the staff already talk. "Doors", "Early", "Peak", "Band", "Last orders", "Clean". Nobody has to be told what those mean. Names like "Scene 4" or "Blue chase 120bpm" require the reader to already know the answer, which defeats the point.

What happens when the owner asks for everything to be more blue?

Use palettes, so that a colour change is one edit rather than twenty. A palette is a named colour or position that scenes refer to instead of storing their own copy. Edit the palette once and every scene using it updates. Without palettes, "can we make the whole room a bit warmer?" means opening every scene and changing the same value by hand, which is how a venue ends up with three shades of nearly-the-same-red.

This matters more in a venue than anywhere else, because the request will come. A new manager arrives, a brand refresh happens, a beer sponsor turns up with a green. If that request costs you an evening every time, the rig will drift out of date and eventually get left on one static look — which is the failure mode this whole article is about.

What do you hand over: the software, or a console?

Hand over a console, not the software. HitLight's virtual console is a grid of buttons, faders and XY pads that you arrange yourself and then hand to someone who has never used the app. The person on shift sees six labelled buttons and a master fader. They never see the scene editor, the patch, or anything else they could break by clicking on it.

Build it in edit mode, lay out one button per named look, one fader for overall brightness, and a Blackout that is obvious and reachable. Then leave it in operator mode. The rest of the app still exists for whoever programmes the rig; it simply is not the surface the venue interacts with day to day.

If a laptop on the bar is a bad idea — and in a wet, busy venue it often is — bind the same actions to a physical controller. MIDI learn works by pressing the control you want to use, so a cheap pad controller or a footswitch becomes the console instead. A row of labelled pads under the till is about as low as the training cost gets.

Can more than one person run the lights?

Yes. A show owner can invite collaborators, and browser or iOS remotes forward control to the elected Mac hardware master — the machine physically connected to the rig. There are no paid Team plans during the beta. In practice that means the venue Mac sits in the booth driving DMX while a duty manager fires looks from a phone on the floor.

This is worth setting up before you need it, for two reasons. The first is that a second account means a second person who can fix something at 10pm on a Saturday. The second is that the iOS remote can issue Stop or Blackout, so the person who is actually standing in the room when something looks wrong is also the person who can stop it.

The constraint to plan around: the Mac is the only client that outputs DMX. If it is asleep, signed out or unplugged from the interface, the remotes have nothing to remote-control. Treat that machine as part of the installation rather than as someone's laptop.

What goes on the laminated card next to the laptop?

One side of A5, laminated, physically attached to the booth. It exists because the handover conversation will be forgotten and the card will not. Keep it to things a person can do while holding a drinks order in their head.

• The six look names, in the order of the night. Doors, Early, Peak, Band, Last orders, Clean — matching the button labels exactly, character for character.
• Where Blackout is, and what it does. One line: it takes the rig dark immediately. This is the only control everybody must know.
• What to do if the lights are stuck. Usually: press the look you want again, then Blackout, then the look. If that fails, the next line tells them who to ring.
• What to do if the screen is asleep. The Mac drives the rig, so a sleeping or signed-out Mac means no output at all. Say so explicitly, because it is not obvious.
• What not to touch. Name the one or two things that will cause real work to undo — usually the patch and the fixture addresses.
• A name and a phone number. Whoever programmed it. Cards without a contact get ignored the first time reality departs from the script.

None of this is about lighting design. It is about designing the operating instructions, and then making the software match them. A rig that four people can run badly is worth more to a venue than a rig one person can run brilliantly, because only one of those two survives a staff rota.

For a fuller picture of how this fits together, see lighting control for bars and venues, or the plain-English DMX glossary if some of the vocabulary above was new.