Live production buying guide
Choose cameras, switchers and streaming software from the required output backwards
Start with what must leave the production: resolution, frame rate, audio, graphics, destinations, recording and recovery. Then choose the switcher and connections that can preserve that result. Buying a 4K camera, a 2 M/E switcher or an SDI converter before mapping the signal often creates an expensive feature that never reaches the audience.
The moving link marks illustrate the program moving through the planned chain; they are not live measurements and remain still for reduced-motion users.
HD or 4K?
Choose the production standard from the deliverable. UHD can preserve detail for a large display, crop or archive, but every compatible camera, cable, switcher input, keyer, recorder, encoder, monitor and storage path must carry the chosen format. If the audience output and edit are HD, a reliable HD production can be the stronger investment.
Choose HD when
Distribution is HD, bandwidth and storage are constrained, camera count matters more than crop latitude, or the team needs the simplest reliable field package.
Choose UHD when
The deliverable, projection, archive or post-production crop genuinely needs it and the complete signal path has been tested at the intended frame rate.
SDI or HDMI?
HDMI is common on computers, small cameras and presentation devices. SDI is normally easier to lock, distribute and run over longer professional production paths, with model- and standard-specific distance limits. The right answer is often mixed I/O at the switcher rather than converting every source to the same connector.
Count connector type, signal standard, cable length, embedded audio, copy protection, locking, converters and spares. A connector fitting physically does not guarantee that the source format is accepted. Roland’s V-80HD, for example, combines HDMI and 3G-SDI inputs, while Blackmagic’s ATEM Television Studio family demonstrates a more SDI-centered production design.
1 M/E or 2 M/E?
An M/E is not simply another camera input. It is an additional mix-effects production layer. One M/E can cover many straightforward programs. A second M/E becomes useful when the show needs a clean feed, an independent stage screen, picture-in-picture composition, a second language or version, or another program bus that must be built at the same time.
One M/E
Choose when one program/preview operation, a modest graphics stack and simple auxiliary outputs cover the rundown.
Two M/E
Choose when the rundown names two simultaneous compositions or outputs and the operators can actually control them.
Write the two outputs on paper. If the team cannot describe what the second M/E produces, do not buy it for the label.
Hardware or software switching?
A hardware switcher provides deterministic I/O and a dedicated control surface. Software such as vMix can combine switching, remote guests, replay, graphics and IP sources with exceptional flexibility, but the workstation, capture devices, GPU, audio and updates become part of the production risk.
Hybrid designs are common: hardware owns local cameras and a dependable program output; software owns remote sources, graphics or specialized production; Callaba receives the contribution, shows the remote operator state, records and routes the finished or intermediate feeds.
Build the shopping list from a requirements matrix
| Requirement | Question to answer | Evidence before purchase |
|---|---|---|
| Inputs | How many simultaneous cameras, computers, remote feeds and playback sources? | A connector and format table for every source, including spares. |
| Outputs | Program, clean feed, stage display, confidence monitor, ISO record, stream? | A named destination for every physical and IP output. |
| Audio | Embedded, analog, digital, mix-minus, language, talkback? | A channel map heard at the final program and return paths. |
| Control | One operator, volunteers, remote crew, automation, PTZ? | A rehearsal with the actual control surface and handoff roles. |
| Recovery | Which source, switcher, encoder, network and destination may fail? | A tested bypass or backup for the failures the event cannot tolerate. |
A rehearsal reveals the missing equipment faster than a feature table
- Connect every intended source and force the switcher into the chosen video standard.
- Build the busiest scene, key, replay or picture-in-picture in the rundown.
- Send program and every required aux/clean output to their real destinations.
- Listen to program, return and recording audio; check lip sync after contribution.
- Run the encoder and recording together for a representative duration.
- Disconnect one non-critical source or route and execute the documented recovery.
Let Callaba own the live path after the switcher
Use SRT or RTMP contribution from the venue, observe sources in browser Multiview, keep primary and backup paths explicit, route destinations, and record the event in cloud or self-hosted infrastructure.
