Get AI summaries of any video or article — Sign up free
How I Make Notion Tutorials: Apps, Tools, and Process! thumbnail

How I Make Notion Tutorials: Apps, Tools, and Process!

Thomas Frank Explains·
5 min read

Based on Thomas Frank Explains's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Record voiceover in Adobe Audition to get standalone WAV files that are easier to sync and recover if OBS audio has issues.

Briefing

High-quality software tutorials come from treating audio, screen capture, and face-cam footage as separate, editable assets—then assembling them in post with a disciplined workflow. The process centers on recording voiceover in Adobe Audition for cleaner, standalone WAV files, while screen activity is captured in OBS Studio at 4K. That split matters because it protects the final edit from common failure modes (like audio issues in OBS) and gives maximum flexibility when syncing, cutting, and rebalancing in Premiere Pro.

On the screen-capture side, OBS is configured to record only the exact Notion area that should appear to viewers. Instead of relying on heavy “punch in” editing later, the Notion window is positioned to fit the OBS frame, and the Notion interface is zoomed using Control + Plus until the UI is readable at typical YouTube or phone viewing sizes. The sidebar is collapsed for this specific tutorial, and the zoom level is chosen by mentally simulating how a viewer sees the smaller player window. To make interaction cues unmistakable, two helper tools are used: Mouse Highlight, which visually tracks the cursor and also mitigates an OBS cursor invisibility bug in text-selection mode, and Carnac, which overlays keyboard shortcuts (like Control + C) at a consistent on-screen location.

The face-cam approach also prioritizes edit control. Rather than recording face footage with Loom, the workflow uses a Canon C70 camera with a 20 millimeter lens positioned above the monitor. This produces higher-quality video and—crucially—lets the face-cam be moved, resized, masked, or even temporarily hidden so it doesn’t block UI elements. The assembled edit can therefore show the face cam larger when narration needs it, or cut to face-only when the UI isn’t the focus.

Lighting and audio gear are built around reliability and sound quality. Aputure 300D Mark 2 lighting with the Light Dome and grid provides soft diffusion and directional control, while a Shure SM7B handles the main voiceover through a Focusrite Scarlett 18i8 audio interface (with a Cloudlifter used to boost gain for the SM7B). A Schoeps CMC641 (Hyper Cardiod) shotgun-style mic sits as a high-end backup and can be used when the main mic shouldn’t appear in frame. The lighting stack includes a reflective bounce card for facial fill, a Godox light with a Furnale modifier for hair light, and Nanlite Pavotubes for colored background ambiance.

After recording, footage is organized using a centralized server folder structure tied to Notion. A numbering system links Notion “completed projects” to the correct server assets, enabling quick retrieval of B-roll from other projects. Editing begins from a pre-built Premiere Pro template (Creator’s companion-style defaults), which already includes intro stings, titles, and common elements suited to TF explains’ more formulaic structure.

Because Premiere Pro can be slow with high-resolution media, the workflow uses proxies: ProRes-quality 4K screen and 4K face-cam files are edited via lower-resolution proxy versions, then swapped back to full quality at the end. Audio previews and WAV forms are generated to sync multiple audio tracks, and the face-cam is masked and positioned using copied clip attributes. The result is a tutorial timeline that’s ready for final cutting, with the template and asset structure reducing repetitive setup work.

Cornell Notes

The workflow for TF explains tutorials separates voiceover, screen recording, and camera footage so each element can be edited, synced, and repositioned independently. Voiceover is recorded in Adobe Audition as standalone WAV files, while OBS Studio captures a 4K screen region sized and zoomed so the Notion UI remains readable at typical viewer sizes. Helper tools—Mouse Highlight and Carnac—make cursor movement and keystrokes visible, addressing OBS cursor quirks. Face-cam is recorded with a Canon C70 camera, enabling flexible face-cam placement and masking in post. In Premiere Pro, a default template plus proxy editing (for large ProRes files) speeds up timeline work, then WAV forms and audio track mixer settings help sync and finalize the edit.

Why record voiceover in Adobe Audition instead of relying on OBS audio?

Voiceover is captured in Adobe Audition to produce a standalone WAV file that’s easier to reuse and edit in post. OBS audio can work, but the workflow favors Audition because it typically yields better audio quality and preserves flexibility if OBS audio fails—an issue that has happened before. The standalone WAV also simplifies syncing and waveform-based alignment in Premiere Pro.

How does the workflow ensure the Notion UI is readable without heavy post “punch-ins”?

OBS is set to capture a 4K window that matches the exact Notion area being shown. The Notion interface is zoomed using Control + Plus (about three times, targeting ~125%), and the sidebar is collapsed when it isn’t needed. The creator checks readability by imagining the viewer watching the smaller YouTube player or phone screen, then positions the Notion window inside OBS so the viewer sees the intended layout immediately.

What roles do Mouse Highlight and Carnac play during screen recordings?

Mouse Highlight (Windows utility) draws attention to cursor movement, making interactions easier to follow. It also compensates for an OBS cursor bug where the text-selection cursor can become invisible in Notion. Carnac overlays keyboard shortcuts on screen (e.g., Control + C), with the overlay positioned consistently so it doesn’t shift between takes.

Why record face-cam with a dedicated camera instead of Loom?

Face-cam is recorded with a Canon C70 camera (20 millimeter lens) for higher-quality footage and—more importantly—post-production flexibility. The face-cam can be moved, resized, masked, or temporarily hidden so it doesn’t cover UI elements. That avoids Loom’s typical workaround of keeping the face-cam small and supports scenarios where the face needs to be larger or the UI needs full visibility.

How does the workflow keep Premiere Pro editing manageable with large ProRes files?

It uses proxies. High-quality 4K ProRes screen and face-cam files are imported, but editing is done with lower-resolution proxy files toggled in Premiere Pro. This makes scrubbing and cutting smoother, especially when OBS screen footage adds performance load. At the end, the timeline can switch back to full-resolution media.

How does the workflow use Notion to organize and retrieve assets during editing?

Notion acts as a single source of truth via a numbering system that matches projects to server folders. In Notion’s creators companion board, each completed project has a corresponding number, letting the editor quickly locate the right server assets for that project. This also supports pulling B-roll from other videos by identifying which project number contains the needed footage.

Review Questions

  1. What specific problems does the workflow try to prevent by recording voiceover as standalone WAV files and using Audition instead of OBS audio?
  2. How do zoom level, window positioning, and sidebar visibility work together to keep the Notion UI readable for viewers on smaller screens?
  3. Describe how proxies and WAV-form generation support syncing and editing speed in Premiere Pro for large ProRes media.

Key Points

  1. 1

    Record voiceover in Adobe Audition to get standalone WAV files that are easier to sync and recover if OBS audio has issues.

  2. 2

    Capture only the intended Notion region in OBS and zoom the UI (via Control + Plus) so the interface remains readable at typical YouTube or phone sizes.

  3. 3

    Use Mouse Highlight to make cursor movement visible and to work around OBS cursor invisibility in Notion text-selection mode.

  4. 4

    Overlay keystrokes with Carnac so viewers can follow shortcuts like Control + C without guessing.

  5. 5

    Record face-cam with a dedicated camera (Canon C70) to enable post-production repositioning, masking, and face-only cuts without blocking UI.

  6. 6

    Organize assets using a Notion-to-server numbering system so B-roll and project files can be found quickly and consistently.

  7. 7

    Speed up Premiere Pro editing by working with proxy files while syncing audio using generated waveform previews.

Highlights

Splitting voiceover (Adobe Audition WAV) from screen capture (OBS 4K) reduces risk and increases post-edit flexibility, especially when audio in OBS goes wrong.
OBS is configured to avoid later “punch-in” work by positioning and zooming the Notion UI so it’s readable in the smaller YouTube/phone player.
Face-cam flexibility comes from recording with a Canon C70 camera, allowing the face layer to be moved, resized, or masked in Premiere Pro.
Proxy editing is treated as essential for Premiere Pro when working with huge ProRes files, keeping scrubbing and cutting responsive.
Notion’s project numbering links directly to server folders, turning asset retrieval (including B-roll sourcing) into a fast, repeatable lookup.

Topics

  • Tutorial Recording Workflow
  • OBS Screen Capture
  • Voiceover Audio
  • Face-Cam Production
  • Premiere Pro Editing
  • Proxy Workflow
  • Notion Asset Management

Mentioned

  • Adobe Audition
  • OBS Studio
  • Canon C70
  • Aputure 300D Mark 2
  • Light Dome
  • Shure SM7B
  • Focusrite Scarlett 18i8
  • Cloudlifter
  • Schoeps CMC641
  • Godox
  • Furnale
  • Nanlite Pavotubes
  • Premier Pro
  • Mouse Highlight
  • Carnac
  • Thomas Frank
  • OBS
  • 4K
  • VO
  • B-Roll
  • A-Roll
  • UI
  • XLR
  • SM7B
  • WAV
  • ProRes
  • H264