← Back
Category 13: YouTube Live Streaming, Super Chats & Broadcast Operations

Recording and streaming use separate encoders but together exceed available hardware encoder capacity.

Problem

Recording and streaming use separate encoders but together exceed available hardware encoder capacity.

Solution

Root Cause / Diagnostic:
Assigning separate hardware encoding profiles with disparate resolutions, presets, or codecs (e.g., HEVC for 4K local recording and H.264 for 1080p streaming) instantiates multiple discrete encoder hardware pipelines. When combined throughput exceeds the dedicated video engine clock speeds or concurrent NVENC session bandwidth, the hardware encoder throttles. Both the broadcast output and local master recording suffer catastrophic stutter, macroblocking, and dropped frames.

Actionable Fix:
1. In OBS Output Settings (Recording tab), change the Recording Encoder setting to '(Use stream encoder)' to eliminate the secondary hardware encoding pass.
2. If distinct recording quality is mandatory, lock recording resolution to match the stream resolution and utilize NVENC with 'P4: Medium' or 'P5: Slow' preset across both outputs.
3. Monitor the 'Skipped frames due to encoding lag' counter in OBS Stats to verify that hardware encoder load remains under 80% during intense on-screen action.

Pro Tip:
For multi-track 4K master recording while live streaming, utilize a dedicated secondary PCIe capture card or external ProRes recorder (e.g., Atomos Ninja V) to isolate recording load entirely.