Challenge 3: Why the Two Kinds of Dropped Frames Need Different Fixes — Solution Walkthrough

Why they're genuinely different problems:

Per this chapter's own material, network-related dropped frames occur
because the already-encoded video can't be sent out fast enough —
essentially a bandwidth problem, tied to Chapter 4's own bitrate
material. Rendering/encoding-related dropped frames occur because the
computer itself can't encode the video fast enough in the first
place, tied to Chapter 4's own encoder-choice material. One is a
problem with getting already-finished data out to the network; the
other is a problem with producing that data at all.

Why the fixes don't overlap:

Fixing a network-related problem means adjusting bitrate to match
actual upload bandwidth — a setting entirely about data leaving the
computer. Fixing a rendering/encoding problem instead means reducing
the actual computational load (switching encoders, lowering
resolution/framerate, freeing up CPU/GPU resources) — entirely about
what happens before any data is even ready to send. Applying the
network fix to an encoding problem, or vice versa, addresses a
resource that isn't actually the bottleneck.

Why this is easy to miss without deeper investigation:

Per this chapter's own material, both problems show up identically as
"dropped frames" in a casual glance at the Stats Dock — only checking
which specific category of dropped frame is occurring (network vs.
rendering) reveals which of the two entirely different underlying
problems is actually happening.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the network-vs-rendering distinction is
understood as a genuine difference in root cause and fix, not just
two labels for the same underlying symptom.