Production Guide
Automatic multicam switching for podcasts
If you are searching for automatic multicam switching, autoswitching, or a 100% automated multicam podcast studio, this is the workflow. Automatic camera switching turns a multi-camera podcast from a manual directing job into a repeatable production system.
How to make podcast cameras follow the speaker
A podcast switching system needs three pieces of context: which microphone is active, which camera belongs to that speaker, and which switcher input should be placed on program. PodSwitcher handles the decision layer so the production machine can listen for speaker changes and send the correct commands to your ATEM or Companion setup.
The practical difference from regular audio-follow-video is intent. AFV makes the selected video source bring its audio with it. Automatic camera switching works in the other direction: speaker activity drives the camera choice. For podcasts, that is usually the more useful model because the conversation decides the edit.
Common ways people describe this problem
- I want my podcast camera to follow the person talking.
- How do I switch podcast cameras automatically?
- How to automate a multicam podcast?
- Is there autoswitching software for a podcast studio?
- Can an ATEM switch cameras based on microphone audio?
- How do I record a multi-camera podcast without a camera operator?
How to switch podcast cameras automatically
- Assign one clean audio source per speaker.Lavalier, dynamic, or interface channels work best when each person has a predictable input. Avoid combining all microphones before the switching logic if you want reliable speaker detection.
- Map each speaker to a camera.A host can map to camera 1, guest one to camera 2, guest two to camera 3, and a wide shot to camera 4. Keep the labels consistent between PodSwitcher, ATEM Software Control, and Companion.
- Confirm switcher control.Bitfocus lists ATEM actions such as setting program input, setting preview input, running macros, controlling media players, and audio input control. That gives a podcast workflow room to switch cameras and trigger production cues from one rule.
- Test thresholds before recording.Room noise, table bumps, cross-talk, and headphone bleed can all confuse a switching system. Run a short mock segment and adjust the hold time so the edit feels intentional instead of jumpy.
Rules that make automatic switching feel professional
The best automated edits are slightly conservative. A good podcast rule set should wait long enough to confirm a real speaker change, avoid cutting on every backchannel response, and return to a wide shot when multiple people talk over each other. This is where automation can outperform a tired operator: once the rules are dialed in, the system applies them the same way for a two-hour recording.
Recommended starting rule set
- Use a short hold before switching to a new speaker.
- Keep a minimum shot duration so cuts do not flicker.
- Use the wide shot during laughter, interruptions, or overlap.
- Let Companion trigger overlays or lights only on deliberate state changes.
- Someone watches every speaker change
- Camera cuts happen late when attention slips
- Editing time moves to post-production
- Speaker detection drives live camera switching
- ATEM and Companion actions fire automatically
- The host stays focused on the conversation
Where audio follows video fits
Blackmagic documentation describes AFV as audio that is sent to program only when the related video input is on air. For some inputs, that is perfect: a media player, remote guest feed, or camera with embedded HDMI audio should often follow its picture. For a podcast table with separate microphones, it is usually better to keep the final spoken-word mix stable and let speaker detection decide camera movement.
Read the companion explainer on audio follows video for when to use AFV, when to leave a mic permanently on, and how delay affects sync.