reel-screen-recorder-docs

Reel: Screen Recorder Face Cam — operating procedures

Use these procedures as task-oriented reference. They describe public capabilities and verification steps, not private implementation. UI labels can vary by version.

Procedure 1: Commission a new microphone or headset

Before you begin

Use the intended headset, recording app and playback source. Avoid changing the audio route midway through the first test.

Steps

  1. Connect the headset before configuring recording. Check the input/output route shown by the device.

  2. Set app-audio and microphone levels, then record speech alone for a few seconds.

  3. Play source audio, speak over it, then leave a brief section with source audio only.

  4. Stop and play the saved MP4. Compare speech clarity, source level and echo.

  5. If the route changes during a real take, stop and repeat this test before continuing.

Expected result

Both sources are audible at a usable balance in the exported file; the voice is not doubled or masked.

If the result differs

If speech is absent, check microphone permission/mute and the active input. If the app source is absent, check its level and capture restrictions. Do not infer separate exported tracks from separate level controls.

Procedure 2: Prepare a multi-screen walkthrough

Before you begin

Use sample data and plan a route through the app that can be repeated.

Steps

  1. List the three or four screens the demonstration will visit.

  2. Choose portrait or landscape before recording and inspect each screen in that orientation.

  3. Place the camera overlay away from controls that will be used later, not only the opening screen.

  4. Record the entire route once without final narration; replay to inspect hidden buttons and app switching.

  5. Record the narrated take, then verify the first action, most crowded screen and final result.

Expected result

Every required control and result is visible in the saved video, with no unintended rotation or private notification.

If the result differs

If the overlay covers an action, reposition it or simplify the route. If a source screen cannot be captured, document the limitation rather than promising capture of every app.

Report a repeatable problem

Record app/version, device/OS, selected mode, input conditions and the smallest failing step. Distinguish expected behavior from the observed result. Use synthetic examples and omit credentials or private records.

Documentation index · Capabilities and limits · Support and sources