A village harvest supper streamed to families who could not travel

Margaret contacted us through the contact page a few weeks before a harvest supper that her village hall committee organises each year. She explained that many former residents now live overseas and had asked, more than once, whether they could watch the evening. The committee had never streamed anything and had a modest budget, so her first message was cautious and full of questions rather than requirements.

I read it twice before replying, because the questions told me more than a specification would have. She wanted to know whether the hall's broadband would cope, whether anyone had to be technical on the night, and whether a stream could be kept private to invited family. None of that was unusual. It is the ordinary starting point for a first streamed event, and it shapes the whole plan.

We agreed a short call, and I asked her to send a rough running order and a sketch of the hall layout. Those two things allowed us to decide camera positions and cable runs before anyone visited the building.

• A rough running order for the evening
• A simple sketch of the hall and stage area
• The name of the platform her relatives already use

Village halls bring their own constraints: a single power circuit shared with the kitchen, a low ceiling, and a stage that is really a raised platform at one end. Tom, our streaming engineer, visited a fortnight ahead with a notebook and a signal tester. He checked where a camera could sit without blocking the fire exit and whether the wall sockets could carry the load.

The broadband was the first concern. He ran upload tests at different times of day and found the connection steady but modest. Rather than trust it blindly, we planned the encoder settings to sit comfortably below the measured speed, leaving headroom for the moment when the kitchen's card machine and the committee's phones all wanted the network.

He also marked a spot for a second camera at the side, giving a closer view of the speeches without needing anyone to walk about during the meal.

• Upload speed measured at several times of day
• Power circuits mapped away from the kitchen
• Camera positions kept clear of exits and walkways

For a small private stream, we kept the chain deliberately plain: two cameras, a compact switcher, a hardware encoder and a single delivery to the chosen platform. Every extra piece of equipment is another thing that can fail in a draughty hall, so we only brought what the evening needed and nothing that merely looked impressive on a spec sheet.

We did add one safeguard. A second encoder, on a separate connection from a mobile hotspot, sat ready to take over if the hall's line dropped. Tom set it up so that switching to it took seconds and the viewers would see a short pause rather than an ended broadcast.

Graphics were minimal: a title card, the names of the speakers, and a small line thanking the village for joining. Margaret approved the wording by email the day before, which saved any last-minute typing on the night.

• Two cameras and a compact switcher
• Primary encoder plus a standby on a separate connection
• Titles approved in writing the day before

We arrived mid-afternoon to rig, test and leave time for the unexpected. The unexpected turned out to be a trestle table placed directly in front of the main camera. A quick word with the helpers and a gentle shuffle fixed it, but it was a reminder of why we always arrive early and never at the last minute.

Once guests settled, the stream opened with a calm title card while relatives joined. Tom watched the outgoing signal on a monitor and the platform's own preview, checking that what we sent matched what viewers received. Sound was the delicate part, because the room echoed. A small microphone near the lectern and a lower level on the room mic kept the speeches clear.

Margaret later said the most touching moment was a grandmother in another country raising a glass to the screen, which a relative in the hall noticed and answered.

Nothing went badly wrong, but we made notes the next morning, as we do after every job. The echo in the room meant we would place a microphone differently next time, and we would ask the committee to move the main table a few feet before we arrive rather than after.

We also noted that the backup encoder was never needed, though the hall's connection dipped briefly during the speeches. Because we had set the bitrate conservatively, viewers saw only a moment of softer picture and not a freeze. That small margin is the kind of decision nobody notices when it works.

Margaret asked for a copy of the recording to keep in the village archive. We supplied it as agreed, and she shared it with those who could not watch live, which turned a single evening into something the village could return to.

A stream does not have to be large to be done carefully. Margaret's supper had two cameras and a handful of guests, yet it needed the same attention to connection, sound and monitoring as a bigger event. The scale changes, but the checking does not, and the viewers abroad were relying on all of it.

If you are planning something similar, the useful things to bring are a running order, a view of the room and an honest idea of who is watching and from where. Everything else we can work out together, step by step, well before the day.

That is the part of the job I enjoy most: turning a hopeful question from someone like Margaret into a quiet, reliable evening on screen.