Sound · practical guide
Audio for a hybrid event
Build explicit mixes for the room, stage, transmission and remote participants.
Destinations and responsibilities
- Room
- PA
- Stage
- Required returns
- Transmission
- Dedicated program mix
- Remote send
- N-1 / mix-minus
- Operator
- Assigned audio responsibility
List local microphones, playback and every remote return. A streaming feed and a conversational return serve different listeners.
Signal flow
Local sources feed the required destinations. Remote incoming audio may feed PA and program, but must be excluded from the send back to that same link. Multiple independent links may need distinct return mixes.
Choose by destination and rehearse the handover
Before choosing a console, list who hears each mix: room audience, stage, stream, each remote link and recording. Identify who must speak to each destination. A single program mix does not automatically satisfy every path.
For recording, specify the finished mix or separate sources and who receives the files. Identify computer, interface and application; the console name alone does not establish compatibility across the chain.
Agree what happens if the remote link fails: who mutes that input, how the moderator is informed and which local content continues. Rehearse with the remote participant and check that backup does not create duplicate audio.
For rental, purchase or a production solution, start with date, venue, local/remote participants and destinations. Approximate quantities and existing equipment are enough to begin without a model decision. Configuration and scope are confirmed in the proposal.
Preparation
- Draw source-to-destination assignments, including computer/interface loopback.
- Choose pre/post and mute behavior deliberately; check what follows a room-fader move.
- Rehearse with a real remote participant and monitor the actual transmission separately.
Common questions
Why does the remote guest hear themselves?
First separate an electronic loop from acoustic pickup.
- Listen to the remote-send bus with the guest speaking; their incoming signal must be absent.
- If routing is correct, test with headphones and check loudspeaker pickup, duplicate computer audio and the designed AEC path.
- If the guest is audible in their own send, correct that route first and verify it is absent while local speech remains. If echo disappears with the room speakers reduced or headphones used, investigate acoustic pickup/AEC with the system designer. Stop uncontrolled changes if multiple platforms or returns remain unidentified.
Can I send the PA main mix to the call?
Only if its contents meet the return requirement; commonly a separate bus is needed.
- Exclude the return from that same call in the send bus.
- Check local microphones and playback still reach the guest, with intentional pre/post behavior.
- Rehearse local speech, playback and guest speech separately. The guest must receive the intended local sources without their own return; verify fader and mute behavior on the actual platform. If one change affects an unintended destination, stop and review the bus/tap map with the audio lead.
Why does the stream differ from the room?
The remote audience does not hear the room’s natural sound.
- Listen at the actual destination for speech, playback and remote voices.
- Adjust the dedicated program mix and check timing; do not judge it only from the PA.
- If the console program meter moves but the remote destination lacks that source, trace interface, application selection and send mapping; if the source is missing in the program bus, correct that mix first. Verify from an independent receiving endpoint; unresolved delay or missing audio requires the platform/audio operator’s coordinated review.
Destination map
| Destination | Intended content | Verification |
|---|---|---|
| PA | Required local and remote sound | Room coverage and feedback |
| Stage return | What presenters need | Listening level and excluded sources |
| Transmission | Complete audience program | Actual receiver/recording |
| Remote send | Required program minus own return | Guest speech absent from send |
Operating conditions
- Mix-minus does not remove acoustic echo by itself; AEC needs the correct design and reference.
- Use controlled listening levels and avoid loud test signals on live destinations.
- Keep labeled buses and a tested backup; avoid changing platform processing during the show.
Sources
Sources consulted October 22, 2026. Confirm routing and available functions on the actual system.
- vMix — Mix Minus Basics and Troubleshooting — Official routing and echo troubleshooting principles; not a universal platform preset.
- Yamaha DM7 Reference Manual — Mix Minus — Model-specific implementation; verify feature/package and version.
Related help
Help us improve this guide
Is an explanation missing, did you find an error, or did you solve something differently? Tell us on WhatsApp.
WhatsApp opens with an editable draft. Review it and send it if you choose. Do not include passwords, keys or client information. Contributions are reviewed before being added to guides; they are not published automatically.