OBS encoding overloaded: test the encoder bottleneck first

What it may mean

The selected encoder, preset, resolution, frame rate, concurrent recording, filters or overall workload may exceed available encoder capacity.

What it does not prove

Encoding lag is different from network-dropped frames and rendering lag. Lowering bitrate alone may not reduce encoder workload.

Evidence to inspect

Run the problem scene briefly, stop output, and inspect the end-of-session skipped-frame counter plus the relevant OBS log block.

One conservative free test

Change one workload variable: use a faster supported preset or lower output resolution/frame rate. Repeat the same scene and compare skipped-frame deltas.

Rollback first

Export or screenshot the original output settings and restore them if the repeated test does not materially reduce skipped frames.