FAQ

Yes—especially if your goal is “teach with video” rather than “become a professional colorist.” The timeline is approachable, templates accelerate first projects, and you can grow into advanced audio and animation over time. Beginners get the fastest wins by learning a simple recording setup (mic gain, consistent resolution) and a repeatable export preset.

The usual suspects are mismatched frame rates, variable frame rate (VFR) screen capture, or a project setting that doesn’t match your media. Stabilize by recording constant frame rate when possible, align project settings to your primary footage, and avoid unnecessary reinterpretation of clips. If drift appears only after export, verify your export FPS and audio sample rate.

Start with resolution: don’t export 4K if your delivery target is 1080p. Then tune bitrate relative to motion—screen recordings with lots of scrolling need more bitrate than static slides. Use modern codecs where supported, keep audio bitrate reasonable for speech, and avoid “double encoding” (re-exporting a heavily compressed source unless you have a reason).

OBS excels at live streaming and highly customizable capture graphs. Camtasia excels at editing, annotations, and producing polished training videos quickly. Many teams use OBS (or OS-level capture) for acquisition and Camtasia for post—what matters is a stable capture format and a consistent pipeline.

Use the publisher or a reseller you already trust for installers and updates. Third-party mirrors can bundle unwanted software or lag behind security patches. If a download page looks unfamiliar, stop and confirm the source before installing.

Stabilize narration level, noise, and pacing first. Captions should follow natural pauses; if you paint callouts before dialog is final, you will rework motion every time a line changes. Treat captions as part of the edit, not a bolt-on at the deadline. Feature notes on captions →

Keep every asset under one project folder, prefer relative paths, and write down project frame rate, sample rate, and any unusual codecs. Zip the whole folder instead of sending loose .tscproj files with missing media. A 30-second reference export plus a short README prevents “works on my machine” loops.

A quiet room and a mic with consistent gain beat almost any GPU upgrade for intelligibility. Fast CPUs and SSDs help long timelines, but clipped audio, variable frame rate chaos, and “mystery export” presets waste more hours than modest hardware spend. Fix acquisition discipline first, then profile disk and CPU if exports still crawl.

Name presets after the host so humans pick the right file under stress. Match resolution and bitrate to what the player actually streams—many LMS players recompress aggressively. Verify captions if your org requires them, export sidecars when the host expects them, and listen on laptop speakers before you publish. Archive the project folder before you delete intermediate stems. Large-project export patterns →

Zip the entire project folder—including media and any sidecar captions—before you flatten stems or run aggressive disk cleanup. Keep a dated archive before major version upgrades. If you rely on cloud sync, pause it during active edits: conflicted copies are a common source of “missing media” panic. A README with FPS, sample rate, and unusual codecs saves the next editor an hour.

VFR capture changes how many frames arrive per second: still slides look “cheaper” on disk, motion spikes when you scroll. If the project assumes constant frame rate, you can see drift, odd duration math, or exports that look fine locally but slip on strict players. For teaching video, CFR acquisition is usually worth the disk cost. Practical drift fixes → · Concepts primer →

Burned-in (open) captions survive every player but force a full re-export when legal tweaks a word. Sidecars (SRT/VTT) enable translation swaps and some accessibility pipelines—but only if your host ingests them and your learners know how to turn them on. When policy allows both, ship sidecars for the LMS and keep a burned-in emergency copy for executives who open files in random desktop players. Review & delivery section →

One document per review round, every comment tied to MM:SS, and a bright line between “blocks launch” and “nice to have.” Share a watermarked MP4 for narrative approval; reserve project files for people who actually edit. When rounds stack, close the previous doc—otherwise you will implement feedback that contradicts last Tuesday’s email. Stakeholder review habits →

Treat the desktop like a live broadcast: DND on, chat apps closed or on a safe account, browser on a profile without bookmarks to internal tools. Zoom the capture region so stray widgets do not appear. If customer data flashes, stop the publish pipeline, patch or re-capture, and ship a new file with a bumped version in the name so support can tell clean from dirty. Screen hygiene checklist →

Duplicate when two audiences need different legal text, when localization forks the script, or when a cohort must stay frozen while another moves forward. Stay in one project for typo-level fixes if you already zip backups before risky experiments. Either way, write a one-line README: what changed, who approved it, which export preset shipped. Versioning & rights section →

Every animated callout, zoom, and layered track asks the encoder to composite more pixels per frame. That is expected. What is not normal is a sudden cliff from full disk, thermal limits, or a background sync tool hammering the same volume as your render cache. Close chat and backup apps, keep tens of GB free on the scratch disk, and on huge courses consider proxies or segmented exports. Machine habits & QA section →

Skim the first and last ten seconds, read on-screen text aloud, listen on laptop speakers, verify captions if policy requires them, and confirm the filename matches the ticket’s approved version. If your LMS has a staging preview, use it—desktop players lie about what a recompressed host will do. Five-minute QA list →