Choose a frame rate for the motion in your lesson

A static slide with occasional pointer movement asks for a different motion test from fast gameplay. List the hardest sequence: scrolling small text, dragging a window, drawing a curve or following a rapid animation. Include that sequence in every comparison.

Do not use a still title card as proof that a higher frame rate is unnecessary for the whole lesson. Equally, a game’s display refresh rate is not automatically the frame rate delivered by a recording file.

The inspected Reel Mac settings include 30, 60 and 120 choices, with platform qualifications. That is evidence of a selector, not a guarantee every capture, encoder, device or destination sustains those values. Do not advertise universal 120 fps recording on iPhone from a Mac-only preference.

If your recorder or upload destination limits the choice, work within that documented range. For example, a destination specification can cap frame rate even when a source recorder offers more. Check the final output, not only the setting selected before capture.

At 30 frames per second, the nominal interval is about 33.3 milliseconds; at 60 it is about 16.7 milliseconds. That describes sample spacing, not a promise that every frame is unique or that latency is reduced by exactly half.

A thirty-second file at a constant 30 fps has a nominal 900 frames; at 60 it has 1,800. Twice as many nominal frames does not imply precisely twice the file size, since encoding and scene content also matter.

Record a short safe sequence at two supported settings without changing resolution, framing or the action. Watch the files normally, then inspect the difficult movement. Ask whether the viewer can follow the pointer and read the result without distracting judder.

If the higher setting overloads the device and the saved result stutters, it may be less useful than a consistent lower setting. Follow the stutter-diagnosis workflow rather than raising every other quality control at the same time.

Send or upload the chosen sample and inspect the processed version. A platform or editor may transform the file; the source selector is not evidence of the final rendition. Preserve the original until the handoff passes.

For a static lesson, clear pauses and deliberate pointer movement may matter more than an ambitious rate. For motion-heavy content, evaluate smoothness alongside readable detail and manageable size. Record the selected compromise and repeat the test when the workload or destination changes.