Appendix E: NLE Translation Guide

This is the book's Rosetta Stone. Every editing, color, audio, and delivery chapter (roughly Chapters 26–37) teaches a concept first and then names the button — and the button it names lives in DaVinci Resolve, the free, professional suite this book anchors its hands-on steps to (see Chapter 27). But you may be sitting in front of Premiere, Final Cut, CapCut, or Kdenlive, and the labels on your screen will not match the labels in the text. That mismatch is cosmetic. This appendix exists so that a control the book names is never a control you cannot find.

Here is the whole idea, and it is worth carrying as a working belief: a bin in Resolve, a Project panel in Premiere, an Event in Final Cut, and a Project Bin in Kdenlive are the same idea wearing different name-tags. A blade is a razor is a split. A cross-dissolve is a cross-dissolve is a "Dissolve" transition. A node and an adjustment layer are two ways of stacking the same color operation. When a lab in this book names a control you cannot find in your software, the answer is almost never "my app can't do that." It is "my app calls it something else, and it lives in a slightly different room." This guide tells you the something-else and the room. Editing concepts are universal; only the software names differ. Learn the concept once and you can sit down in front of any of these five tools — and any tool released after this book — and be productive by dinner.

How to read this guide

The tables below map one Concept across five editors. A cell gives the feature's name in that app and, where useful, the area it lives in — a panel, a page, a browser. Two conventions:

—    no direct, one-to-one equivalent (do the job another way, noted in the surrounding text)
≈    present but simplified, partial, or handled differently than the desktop tools

A standing caveat, applied to every cell: software changes. Menu names move, panels get renamed, features arrive and get reorganized between versions. This guide names features and where they generally live, not exact click-paths, and it deliberately avoids version numbers. If a name here does not match your screen exactly, it has almost certainly just moved — look for the same idea under a nearby label, and use your app's built-in search (most have one) to find it by name. The point of this appendix is never the precise menu path; it is the confidence that the feature is in there.

The five editors at a glance

Resolve, Kdenlive, and CapCut are all free to use, so cost is never the reason a reader of this book cannot finish a project. Everything the book teaches can be done for nothing. The differences below are about shape — how each app arranges the same craft.

One structural fact to absorb before the tables: Resolve is organized into pages — Media, Cut, Edit, Fusion, Color, Fairlight, Deliver — that you switch between like rooms in a house. Most other editors put those functions in panels and workspaces inside a single window. So when the book says "go to the Color page," the Premiere equivalent is "open the Lumetri Color panel," and the Final Cut equivalent is "open the Color Inspector." Same job, different architecture. Keep that in mind and half the translations below become obvious.

1. Media and project

The first hour of any edit is the same in every app: get the footage in, organize it, make it play smoothly, and save the project. This is the material of Chapter 27.

Where it genuinely differs. Final Cut's organizing unit is the Library — a single bundle that contains your Events (which hold clips) and your Projects (which are timelines). Where other apps sort clips into bins, Final Cut leans on Keywords: you tag clips and let Keyword Collections and Smart Collections gather them automatically. Resolve is unusual in the other direction: it keeps projects in a database, not as loose files you double-click, so "back up the project" means exporting a .drp or backing up the database (Chapter 37), not just copying one file. Premiere and Kdenlive are the conventional case — one project file that points at your media sitting in folders on disk. CapCut mostly hides all of this: your work lives as a draft inside the app, which is convenient on a phone and a real limitation when you want a portable, archivable project.

On proxies: a proxy is a lightweight stand-in copy of heavy footage so editing stays smooth, swapped back for the full-quality original at export (Chapter 27). Every desktop tool here can do it; only the menu name changes. CapCut abstracts it away — fine for phone-sized clips, less so for a folder of 4K.

2. Timeline and editing

This is the heart of Chapters 26 and 28 — the moves you make hundreds of times a day. The vocabulary is remarkably stable across apps; the one real outlier is Final Cut's timeline model, flagged below.

Where it genuinely differs. Final Cut Pro's Magnetic Timeline is the big conceptual jump. There are no lockable V1/V2/A1/A2 tracks to lay clips onto. Instead there is a primary storyline with connected clips (B-roll, titles, sound) attached above or below, and the timeline "magnetically" closes gaps as you edit so clips do not collide. To organize audio and video the way tracks would, Final Cut uses Roles (label a clip "Dialogue," "Music," "Titles," and mix or export by role). If you come from a track-based tool and go looking for "tracks" in Final Cut, you will not find them — search for Roles instead. Everything the book says about J-cuts, L-cuts, ripple, and coverage still applies; it is simply arranged around clips and roles rather than a grid of tracks.

The split edit is universal. The J-cut and L-cut (Chapter 28) — where sound leads or lags the picture — are not a special feature in any of these apps. They are just what happens when you trim the audio and the video of a clip to different points. Every app lets you break the link between a clip's picture and its sound (or trim them separately) so you can do it. The label on the "unlink" or "expand" command is the only thing that changes.

CapCut, in one line: it does the common edits — split, trim, reorder, overlay — quickly and by touch, and quietly automates the fussier ones (gaps close on their own; there are no named slip/slide tools). That is a feature for a fast social cut and a ceiling when you need frame-exact control.

3. Transitions

A hard cut — the default, and the cut you will use ninety-plus percent of the time (Chapter 28) — requires no tool at all in any app: you simply place two clips next to each other. A transition (a dissolve, a wipe, a fade) is an effect you add at the join. So the only things to translate are the default dissolve and where the transition library lives.

Where it genuinely differs. Kdenlive splits a concept the others merge. A Mix is a dissolve within a single track (trim two neighboring clips so they overlap and cross-fade); a Composition is a blend between two stacked tracks (the upper track dissolving over the lower). If you are looking for a plain cross-dissolve in Kdenlive and only find "compositions," reach for Mix on the cut between two same-track clips. CapCut applies a transition by tapping the little seam icon between two clips and picking from a menu that leans heavily toward flashy, motion-driven transitions — the restraint the book preaches (a cut is a thought, not a decoration) is on you, not the app.

4. Color

Chapters 31 and 32 draw a hard line between correction (neutralize each shot, match shot to shot — the boring, essential pass) and the grade (the look you build on top of a corrected image). Every app can do both. The one deep structural difference is how corrections stack: Resolve builds them as a node tree; everyone else stacks them as a list of effects or layers.

Where it genuinely differs. Two things trip people up here. First, "Power Windows" is Resolve's brand name for a shape mask — an oval or rectangle (or hand-drawn shape) that limits a correction to part of the frame (darken a bright sky, brighten a face). Every app has this; it is just called a mask almost everywhere else. When Chapter 32 says "add a Power Window," the Premiere translation is "add a mask inside Lumetri," and the Final Cut translation is "add a color mask." Second, and more fundamental: Resolve organizes color as a node graph — little connected boxes, each doing one operation, that you wire in series or in parallel. Premiere, Final Cut, and Kdenlive organize the same operations as a stack of effects or layers (a top-down list). CapCut flattens it further into per-clip sliders and preset filters. These are different mental models for the identical underlying math. The book teaches nodes because it anchors on Resolve and because nodes make the correction-then-grade order (Chapter 32) visually obvious — but if your app stacks layers instead, read "add a node" as "add another effect/adjustment on top," and every instruction still lands.

CapCut color, honestly: the Adjust panel plus Filters will get a social clip looking good, and that is often all a vertical cut needs (Chapter 23). But without real scopes it is hard to correct precisely (Chapter 31) — you are trusting your eye on an uncalibrated phone screen. For anything destined for a controlled color pass, this is the point to move to Resolve.

5. Audio

"Sound is half the picture" is a load-bearing theme of this book (Chapters 14, 15, 33). The good news: the audio vocabulary — levels, EQ, noise reduction, keyframed volume, loudness — is nearly identical everywhere. The main structural note is where the mixer lives.

Where it genuinely differs. Resolve's audio lives on its own page, Fairlight, which is effectively a full digital audio workstation bolted onto the editor — the most capable audio environment of the five, and the reason the book can teach a real mix (Chapter 33) without leaving the app. Final Cut has no separate mixer page; you adjust audio in the inspector and organize the mix through Roles, metering as you go. The one place to be careful is loudness metering — hitting a target like -14 LUFS for streaming (Chapter 33). Resolve and Premiere have solid built-in loudness tools; Final Cut, CapCut, and Kdenlive's loudness metering is more limited or varies by version. If your app cannot show you LUFS reliably, you have two honest options: check the level on a dedicated loudness meter (a free plugin or a separate tool), or master to sensible dialogue levels by ear and meter, and let the destination platform's normalization do the final leveling — but never skip a levels check just because the fancy meter is missing.

Keyframing volume is the same gesture everywhere: it is how you duck music under a line of narration or fade a clip out by hand (Chapter 33). Look for the thin volume line running through the audio clip and add points to it. Resolve, Premiere, Final Cut, CapCut, and Kdenlive all have it; only the word for the little points ("keyframes") is universal.

6. Titles and graphics

Titles, lower thirds, and simple animation are Chapter 34's territory. Every app can set text on screen and move it; they differ mostly in how much motion-graphics muscle sits behind the text.

Where it genuinely differs. The desktop suites each pair with a deeper motion-graphics environment for anything beyond a moving title: Resolve has Fusion (a node-based compositor built into the app — Chapter 35), Final Cut has the companion app Motion, and Premiere hands off to After Effects. Kdenlive and CapCut keep animation at the per-clip keyframe level — position, scale, rotation, opacity — which is genuinely enough for titles, lower thirds, and simple moves, and not the place to build a complex animated sequence. For the book's motion-graphics work, Resolve's built-in Fusion means you never have to buy or leave for a second app.

Captions are a special case. Auto-captioning (transcribe speech to on-screen text, then correct it — Chapter 36's accessibility work) is a strength of CapCut and is built into recent versions of the desktop tools too. Wherever you generate them, the rule from Chapter 36 holds in every app: read and fix auto-captions before you deliver. The generator is a first draft, never the final word.

7. Export and delivery

The last step (Chapter 36) — get a finished file out at full quality, matched to where it is going. The settings are the same everywhere (container, codec, resolution, frame rate, bitrate); only the name of the command and the shape of the preset list change.

Where it genuinely differs. True to form, Resolve makes export a whole page (Deliver) with a render queue, so you can line up several outputs and render them in a batch — handy when you owe a master, a YouTube file, and a 9:16 social cut from the same timeline (Chapters 23, 36). Premiere splits the job between its own Export view and Adobe Media Encoder (a separate queuing app). Final Cut calls it Share and pushes heavier or fussier encodes to the companion app Compressor. Kdenlive calls it Render. CapCut boils it down to one Export button and a short list of quality choices, then offers to post straight to social platforms.

Notice how similar the codec columns are: the desktop apps all wrap the same industry standards (H.264/H.265, Apple ProRes, and friends — Chapter 3), because a codec is a published standard, not a proprietary feature. That is the whole thesis of this appendix in miniature: the thing that matters (which codec, at what bitrate, for which destination) is identical across apps and is taught once, in Chapter 36; the thing that differs (whether you click a page, a menu, or a button) does not matter at all.

Structural differences worth keeping in your head

Most of this guide is one-to-one translation. But five differences are architectural — they change how you think, not just what you click. Keep these five in mind and the rest of the translations fall out naturally:

1. Resolve is organized into pages (Media, Cut, Edit, Fusion, Color, Fairlight, Deliver). You change rooms, not panels. In the other editors the same jobs are panels and workspaces inside one window. "Go to the Color page" ≈ "open the color panel/inspector."
2. Final Cut's Magnetic Timeline has no lockable tracks. A primary storyline with connected clips replaces V1/V2/A1/A2, and Roles replace tracks for organizing and mixing. Search for "Roles," not "tracks."
3. Color is a node graph in Resolve and a layer/effect stack everywhere else. Same operations, different mental model. Read "add a node" as "add another effect/adjustment on top." "Power Window" ≈ "mask."
4. Where the project lives varies. Resolve keeps projects in a database; Final Cut wraps everything in a Library bundle; Premiere and Kdenlive use a conventional project file pointing at media on disk; CapCut keeps an in-app draft. This changes how you back up and archive (Chapter 37) — know which case you are in.
5. CapCut is deliberately simplified and mobile-first. It hides proxies, scopes, and the mixer; it auto-does ripple; it leads with templates and auto-captions. It can carry a social or vertical piece end-to-end (Chapter 23) and tops out exactly where controlled color and audio finishing begin (Chapters 31–33).

The bottom line: the concept matters, the button doesn't

If you take one thing from this appendix, take this: you are not learning software; you are learning a craft that software happens to host. The skills this book builds — reading a scope, cutting on the right frame, balancing a shot to neutral before you grade it, ducking music under a voice, matching a codec to a destination — are the same in every application, and they will outlast every application. Software gets renamed, reorganized, discontinued, and replaced. The concepts do not. An editor who understands why a J-cut works can find the J-cut in any tool in about ninety seconds. An editor who only memorized where the button was in one app is lost the moment the button moves.

So when a lab in this book names a control you cannot find, do not conclude your app is missing it. Come back to the relevant table, find the concept, read across the row, and it will be there under another name in a slightly different room. That habit — translating the concept, not hunting for the exact button — is what lets you walk into any edit suite, on any machine, and go to work.

And you can build this entire book's three-project portfolio without spending a dollar:

• DaVinci Resolve does everything the book needs in one free application — edit, color, audio (Fairlight), motion graphics and compositing (Fusion), and delivery. It is the reference for every hands-on step precisely because a free tool with no missing pieces means no reader is left behind. If you install one thing, install this.
• Kdenlive (and its close cousin Shotcut) are free, open-source, conventional track-based editors — an excellent path if you prefer the familiar tracks-and-timeline model, are on Linux, or want a lighter install than Resolve. They cover editing, basic color, audio, titles, and export.
• CapCut is the fast lane for mobile and social work (Chapter 23): shoot on the phone, cut on the phone, auto-caption, and post — no computer required. Use it for what it is superb at, and step up to Resolve when a project calls for real scopes, a real mixer, and a controlled finish.

The gear was never the variable, and neither is the software. Pick a tool you can afford — which, thanks to Resolve, Kdenlive, Shotcut, and CapCut, can be nothing — learn the concepts once, and let this table handle the translation.