Technical Multicamera Streaming Checklist for Launches and Activations in São Paulo

Start with the broadcast brief, not the equipment list. Define the audience, platform, expected duration, language, privacy level, number of remote contributors, recording requirement, and whether the stream will be public, private, or embedded into an internal event experience.

The running order should identify every live source and transition. For example, a 45-minute product launch might include a holding slide, host introduction, executive keynote, product close-up, pre-recorded film, audience questions, remote guest, and closing call to action. Each item should have a source, an audio owner, a camera instruction, and a backup option.

Request a venue technical pack at least several weeks before the event. The pack should include the room layout, electrical information, internet handoff details, available sound equipment, loading instructions, access windows, restrictions on rigging, noise considerations, and the contact details of the venue representative on event day.

For Scheeeins House, the production company should confirm which spaces will be used and whether the stream will move between the main room, covered outdoor auditorium, speakeasy, meeting room, or external areas. A visual route through the venue can be effective, but it increases the need for wireless communication, cable management, exposure control, and reliable camera-to-control-room connectivity.

Do not treat venue Wi-Fi as a vague promise of internet access. Ask whether the connection is dedicated to the event, how the production network will be separated from guest traffic, where the handoff will occur, whether wired access is available, and who can authorize a network change. A written answer is more useful than a verbal assumption made during a site tour.

The number of cameras does not directly determine upload bandwidth. The encoder usually combines the selected camera views into one program feed, so the required upload rate depends mainly on the output resolution, frame rate, codec, platform, and number of simultaneous destinations.

As a planning rule, a single 1080p program feed commonly requires several megabits per second of sustained upload, plus operational headroom. A production team should not size the connection at the exact bitrate. For a primary feed around 6 to 8 Mbps, planning roughly 12 to 16 Mbps of stable dedicated upload gives room for protocol overhead and short fluctuations. The final target must follow the platform specification and the encoder configuration.

If the team sends separate feeds to Zoom, Microsoft Teams, Instagram Live, and another destination, the bandwidth calculation changes. One encoder may create multiple outbound streams, or a cloud distribution service may receive one contribution feed and distribute it onward. Ask the streaming provider which architecture will be used before approving the internet requirement.

For corporate meetings, Zoom publishes separate recommended bandwidth figures by meeting quality and device role in its official bandwidth requirements. Microsoft also provides quality guidance for Teams through its official network planning documentation, which is useful when the broadcast includes remote presenters or an internal audience.

A robust plan separates the primary contribution from guest internet access. The production network should use a wired handoff whenever possible, while attendee Wi-Fi remains available through its own access method. At Scheeeins House, confirm the dedicated Wi-Fi arrangement, the physical handoff point, the expected upload performance, and the person responsible for technical escalation.

Redundancy should be designed as an operating procedure, not merely as a second modem in a box. Define what happens if the primary connection drops for 10 seconds, 60 seconds, or several minutes. A cellular router, second fixed connection, bonded encoder, pre-recorded version of the keynote, or local recording can each solve a different failure scenario.

One frequent mistake is choosing camera positions after the room has been dressed. Scenic elements, branding, catering, furniture, and guest circulation can block an otherwise workable angle. Mark camera footprints during the venue survey and include them in the floor plan before the setup is finalized.

Another mistake is assuming that a high download speed proves good streaming performance. The production depends on stable upload capacity, latency, packet loss, and the behavior of the connection under load. Test at the planned handoff point and repeat the test during a period that resembles the event schedule.

Teams also underestimate presentation files. Fonts, embedded videos, aspect ratios, animations, clickers, and presenter notes can behave differently between computers. Use a playback machine controlled by the technical director, collect final files before rehearsal, and keep a PDF or still-image version available as a safety option.

A third error is separating the stage rehearsal from the technical rehearsal. Speakers may practice their words while the crew misses camera transitions, slide cues, microphone changes, remote returns, or the moment when the product is revealed. Rehearse the show as it will actually run, including pauses and handoffs.

The day-of checklist should be signed off in this order: power and cable safety, network handoff, encoder output, platform privacy, local recording, audio paths, camera shots, graphics, playback, remote contributors, fallback assets, contact chain, and doors-open timing. Keep one version at the control desk and one with the event lead.

At a premium venue, technical reliability must coexist with guest experience. Cable paths should not compromise the reception, valet flow, catering service, or access to the pool and external areas. At Scheeeins House, coordinate production load-in and camera placement with the venue team early enough to protect both the broadcast and the atmosphere of the activation.