Recording Settings Reference

Use the recording settings before a real take to confirm what Fraime.it will capture and which sidecar data will be available later in the editor.

Capture

The Capture tab controls the screen source and capture quality.

• Source can be a full display, a single window, or a selected area.
• Area capture is useful when the important content is smaller than the full display or when you want cleaner Shorts framing later.
• Frame rate is commonly 30 fps for tutorials and 60 fps for smoother scrolling or UI motion.
• Retina capture preserves sharper UI detail when the destination needs it, but can increase recording and export workload.

If a source is missing or black, check macOS Screen Recording permission and restart Fraime.it after granting access.

Window and Area Capture

Use a window source when the whole video stays in one app. Use a display source when the walkthrough moves between apps. Use area capture when only a region matters.

For area capture, select an area on screen and verify the live preview before recording. The selection defines the raw screen content saved into the project, so include enough room for menus, popovers, or terminal output that may appear during the take.

Window resize presets can help make app demos more consistent. If resize controls are unavailable, grant Accessibility permission so Fraime.it can manage compatible windows.

Audio

Fraime.it can record system audio, microphone audio, both, or neither.

• Use microphone audio for narration.
• Add system audio only when app sound matters to the viewer.
• Pick the intended microphone before recording a long take.
• Do a short test if you changed audio devices, aggregate devices, or headset settings.

After recording, use the Audio inspector to apply voice presets, cleanup, loudness, and background music.

Webcam

The Webcam tab controls whether a camera track is recorded and how it appears during capture preview.

• Enable webcam when face cam helps the explanation.
• Use Visible when you want the camera shown in the recording preview.
• Use Full Frame when you want the full camera feed saved for later layout decisions.
• Choose camera shape, position, size, opacity, and corner radius for the initial picture-in-picture look.

Webcam placement can still be changed later in the editor. Background removal, blur, and green-screen keying are timeline edits, not decisions you must finalize before recording.

Editor

The Editor tab shows the local IDE bridge and Agent API setup controls.

• Install the VS Code-family extension when recording coding sessions.
• Confirm the connected editor status before starting a take that depends on IDE context.
• Use Copy MCP Config and Copy Helper Path when setting up local agents to work with open projects.

The IDE bridge sends structured editor metadata such as file path, language, cursor position, visible range, and function scope. It does not send document contents or selected text.

Performance

Performance Mode balances quality, power use, and preview/export cost.

• Automatic is the safest default.
• High Quality favors fidelity for important captures.
• Balanced is a good general-purpose setting.
• Low Power is useful when recording on battery or under heavy system load.

If preview or export feels slow, check this setting before lowering the final export quality.

Advanced

Advanced settings are mostly for diagnostics and integration setup.

• Show Context Debug Overlay helps verify incoming IDE, cursor, scroll, or keyboard metadata.
• IDE bridge status helps confirm that local editor context is arriving.
• Extension install messages can help troubleshoot a manual VSIX install or removal.

Leave debug overlays off for normal recording so they do not distract from the source content.

Preflight Checklist

Before a long recording, confirm:

• The selected source is the app, display, window, or area you intended.
• Screen Recording, Microphone, Camera, Accessibility, and Input Monitoring permissions are granted when needed.
• The microphone and system audio choices match the video.
• Webcam is enabled only when it adds value.
• IDE context is connected for code-heavy videos.
• Frame rate, Retina, and Performance Mode match the destination.