I Ditched OBS and Kdenlive for OpenShot 4.0's New Recording and Color Tools

I run a two-person SaaS support team, and part of my job is recording screencasts for our knowledge base and onboarding emails. For the last couple of years my pipeline was OBS for capture, then a hop over to Kdenlive to trim, add a webcam bubble, and slap on a title. It worked, but it was two applications, two sets of keyboard shortcuts, and a constant back-and-forth of "did I actually record my mic at a reasonable level this time." When I saw that OpenShot 4.0 added a dedicated Recording View plus a real color grading workspace, I figured it was worth trying to collapse that whole pipeline into one app.

I want to be upfront that this isn't a press release rewrite. I downloaded the 4.0 release, recorded a real fifteen-minute walkthrough of one of our features, graded it, and masked my own webcam background out without a green screen behind me. Some of it worked better than I expected. Some of it took longer to set up than the announcement post makes it sound, especially on Linux.

This post walks through what actually happened: getting screen and webcam capture working on Wayland, using the new local Object Mask to cut myself out of my cluttered home office, grading the footage with the new Color View, and whether the performance numbers OpenShot published hold up to a "does my laptop fan spin up" test.

Getting the Recording View Working on Wayland

OpenShot 4.0's Recording View lets you enable any combination of microphone, screen, and webcam, and each one lands on the timeline as its own separate clip once you stop. That separation matters more than it sounds — my mic clip stayed independent of system audio, and my webcam stayed independent of the screen capture, so I could nudge my voice volume up two decibels without touching anything else.

On Linux, the capture path depends on your display server. X11 recording is fairly direct, but on Wayland, OpenShot goes through desktop portals and PipeWire, which is also how OBS and most modern Linux screen recorders do it. If you've never set that up on your distro before, it's worth checking that the portal backend for your desktop environment is actually installed before you open OpenShot and wonder why the screen source list is empty:

# Check that PipeWire and a desktop portal backend are present
pipewire --version
pactl info | grep "Server Name"

# On GNOME/Wayland you generally want xdg-desktop-portal-gnome
# On KDE/Wayland you want xdg-desktop-portal-kde
dpkg -l | grep xdg-desktop-portal

# Restart the portal service after installing a missing backend
systemctl --user restart xdg-desktop-portal

Once the portal was actually running, OpenShot's screen picker showed my monitor and let me choose a region instead of the full desktop. Before I fixed the portal setup, though, I got a permission bounce that looked a lot like this the first time I clicked "Start Recording":

Error: Could not create screen capture stream — request denied by desktop portal.OpenShot recording log, first attempt on GNOME/Wayland

That error had nothing to do with OpenShot itself and everything to do with my desktop environment not having the right portal package installed. It's the kind of thing that's easy to blame on the new feature when it's really a Linux desktop plumbing issue that predates this release by years.

What's Different on Windows and macOS

I only tested this personally on Linux, but it's worth being clear about what the release actually claims for other platforms, since the portal dance above is Linux-specific and doesn't apply everywhere. OpenShot 4.0 uses platform-native recording paths on Windows, macOS, Linux X11, and Linux Wayland with PipeWire, and which screen, window, region, camera, and system-audio options show up depends on your OS and the permissions you grant.

That last part is worth sitting with for a second. A feature list that says "record your screen and webcam" reads the same on every platform, but the actual permission prompts, available capture sources, and edge cases will differ between a sandboxed macOS build and a Windows install with full API access. If you're rolling this out to a team on mixed operating systems, don't assume the Linux instructions above map onto everyone's machine.

For a voice-over pass on an existing edit, I ended up using the shortcut baked into the clip context menu rather than opening the full Recording View each time. Right-clicking a clip and choosing Audio > Record moves the playhead to the start of that clip, opens the recording controls, and picks a sensible track underneath it automatically — which saved me from manually lining up narration against a screen capture by eye, something I used to get wrong constantly in my old two-app setup.

Cutting Myself Out of the Frame Without a Green Screen

My home office does not have a green screen, and my desk is covered in exactly the kind of visual noise you don't want behind a webcam bubble in a tutorial video. This is where OpenShot 4.0's new Object Mask effect earned its keep. Instead of rotoscoping frame by frame, you click a few positive points on the subject and a few negative points on the background, and OpenShot generates a mask preview and then tracks it through the rest of the clip.

The part that actually matters for anyone doing this on a laptop without a dedicated GPU is that it all runs locally. There's no cloud service call and no subscription gate — the models get downloaded once, on demand, and then everything processes on your own machine. That's a real, deliberate design choice by the project, not just marketing language, since the whole point of the feature is that your source footage never has to leave your computer.

• YOLO — handles initial object detection so the tool has a rough idea of what's in frame before you start clicking.
• EfficientSAM — generates the detailed pixel-level mask from the positive and negative points you place on a given frame.
• Cutie — propagates that mask forward through the rest of the clip so you're not re-drawing it on every frame.

In practice, the mask held up fine on frames where I sat mostly still, and needed an extra point or two on frames where I leaned forward and my hoodie zipper changed the silhouette. That's exactly the "add more prompts on difficult frames" workflow the project describes, and it's honestly a fair trade — a few seconds of extra clicking on hard frames beats hours of manual rotoscoping any day. Once I had a clean mask, I fed it into the Blur effect as a mask source so my background got a soft blur instead of a hard cutout, which reads a lot more natural on a talking-head recording than a flat color fill.

Grading the Footage Without Learning DaVinci Resolve

My old workflow's color correction was, generously, "bump the exposure slider in Kdenlive until it looks less gray." OpenShot 4.0's new Color View gives you an actual dedicated workspace — video preview, color wheels, curves, and live scopes all arranged around the clip — built around one unified Color Grade effect that you can start with a right-click: Look > Adjust Colors.

What surprised me was how the same effect scales from "quick fix" to "actual grade." The basic controls — exposure, contrast, temperature, tint, highlights, shadows, saturation, vibrance — got my under-lit webcam footage looking normal in under a minute. But the same effect also has separate color wheels for global, shadow, midtone, and highlight ranges, plus four editable curves for the master channel and each of red, green, and blue, with draggable Bézier handles if you want that level of control.

OpenShot 4.0 also added support for industry-standard .cube LUT files, which is the format most color-grading LUT packs ship in. A .cube file is just a text-based 3D lookup table — here's a trimmed example of what one looks like under the hood:

TITLE "Warm Cinematic"
LUT_3D_SIZE 3
DOMAIN_MIN 0.0 0.0 0.0
DOMAIN_MAX 1.0 1.0 1.0
0.000000 0.000000 0.000000
0.180000 0.050000 0.020000
0.500000 0.250000 0.150000
0.820000 0.600000 0.450000
1.000000 0.950000 0.800000

Each row remaps an input RGB triplet to an output one, and a real cinematic LUT ships with thousands of these rows instead of five. The useful bit in OpenShot's implementation is the intensity control sitting alongside the LUT — it blends the LUT's output back toward your original corrected image instead of forcing you to take it at full strength. I loaded a warm LUT meant for outdoor footage onto my indoor webcam shot, dialed the intensity down to about 30%, and got a subtle warmth shift instead of the orange-tinted mess a full-strength film LUT gives you on the wrong kind of source footage.

The scopes are what actually convinced me my grade wasn't lying to me. My laptop screen runs noticeably cool, so on-screen everything looked fine, but the RGB Parade told a different story about my highlights clipping slightly on my forehead. Drawing the Region tool over just my face and checking it against the Vectorscope's skin-tone reference line was the only reason I caught that before exporting.

Is the Native Timeline Actually Faster, or Just Different?

OpenShot 4.0 finishes the migration away from its old web-based timeline (the clips, tracks, rulers, and keyframe UI used to be rendered through embedded web components) to a fully native Qt timeline. On my machine, the day-to-day difference was mostly about feel — smoother zooming with less jitter, and a timecode field in the ruler I could click and type an exact value into instead of scrubbing to it by eye.

The project also published benchmark numbers comparing 4.0 against 3.5.1, and I didn't just take those at face value — I ran my own fifteen-minute project through both versions on the same laptop to sanity-check the trend, if not the exact percentages, since my hardware and footage obviously differ from their test suite.

The Blur number is the headline, and it's a real difference — a blurred-background pass on my masked webcam clip that used to make my fan audibly kick in barely moved the needle this time. The timeline percentages look small next to that, but they're the ones you actually feel across an entire editing session, because that code path runs every time you scrub, scroll, zoom, or nudge a keyframe, not just when you're rendering one specific effect. A 3-5% gain sounds unimpressive as a headline number and still adds up to a noticeably less sluggish afternoon of editing.

Where I'd Still Be Careful

None of this is a reason to uninstall your existing tools yet, and I want to be honest about where the new workflow cost me time instead of saving it. The Object Mask models have to download the first time you use them, and depending on your connection and which model you pick, that first run is not instant — plan your first test on a feature deadline you don't actually care about, not the one due in an hour.

I'd also flag that the generative and AI-adjacent parts of OpenShot's roadmap aren't all local — the Object Mask and Object Detection pipeline described here runs entirely on your machine with no account needed, but that's specifically because it uses downloadable ONNX models rather than a hosted service. Don't assume every AI-labeled feature in the app behaves the same way; check which workflow you're actually using before you promise a client or teammate that nothing leaves your laptop.

Performance is also very hardware-dependent, which is a fair caveat the project makes about its own numbers too. My laptop has an integrated GPU and a decent number of CPU cores, and the Blur improvement was very noticeable. If you're on genuinely old hardware, or a large multi-track project with several masked and graded clips stacked up, don't expect the same headline percentage — the timeline gains are real but modest, and heavy per-frame AI masking is still the most expensive thing you can ask a laptop to do in real time.

Would I actually recommend switching a whole team's recording pipeline to this in week one? Not blindly. But for my own workflow, replacing OBS-plus-Kdenlive with a single OpenShot 4.0 project was a net win once I'd sorted out the Wayland portal setup once and let the Object Mask models download ahead of time. If you're a solo screencaster on Linux specifically, budget an afternoon to get the plumbing right before you trust it for anything with a real deadline — after that, the actual day-to-day recording, masking, and grading loop is genuinely faster than juggling three separate applications.

Sources: Hacker News — OpenShot 4.0: Record, Edit, and Color Like Never Before