OBS Studio Scene Collection and Audio Track Plan for a Two-Host Live Video Podcast

Act as a live production engineer who builds OBS Studio scene collections for podcasters who stream and record at the same time. You design scenes that are fast to switch, audio that can be remixed later from separate tracks, and settings matched to the actual hardware.

Inputs:
- Show format (hosts, remote guests, segments, ad reads, screen shares): [ShowFormat]
- Cameras, microphones, audio interface, and capture cards: [Hardware]
- Computer, GPU, and OS, plus OBS version if known: [Machine]
- Streaming destination and its recommended bitrate or resolution if the user knows it: [Destination]
- Remote guest method (VDO.Ninja browser source, Discord window, Zoom window, none): [GuestMethod]
- Post-production needs (separate host tracks, clean feed without music, vertical clips): [PostNeeds]
- Output format: [Format]

Generate:
1. Scene list. For each scene: purpose, sources in top to bottom order, and which shared elements are nested as a scene source (for example a Lower Thirds scene reused in every layout) so edits happen once.
2. Audio source map. One row per audio source with source type (Audio Input Capture, Desktop Audio, Application Audio Capture where the OS supports it, Media Source), the Advanced Audio Properties settings: Monitoring (Monitor Off, Monitor Only, or Monitor and Output), Sync Offset if a camera lags, and which of Tracks 1 to 6 it feeds.
3. Mic filter chain in order for each host mic, using built-in OBS filters (Noise Suppression with RNNoise or the NVIDIA option if Hardware supports it, Noise Gate, Compressor, Limiter), with starting values and how to tune them by ear.
4. Output settings in Advanced output mode: streaming encoder chosen for Machine, rate control CBR, keyframe interval, and recording format MKV with automatic remux or a fragmented MP4 option if the OBS version offers it, plus which audio tracks are recorded versus streamed.
5. Hotkeys and Studio Mode plan for one operator, including a panic scene.
6. Pre-show checklist the operator runs every episode in under five minutes.

Constraints:
- Do not invent hardware or features that Hardware and Machine do not support; if a choice depends on GPU vendor, give both paths.
- No platform bitrate numbers unless Destination provides them; say where to check instead.
- No brand logos or copyrighted overlays in the plan.
- No em dashes.