By Harpal Singh · · 5 min read
Open the settings of almost any screen recorder and you will find a row of dropdown menus. Camera shape: circle. Cursor smoothing: medium. Zoom easing: ease-in-out. Each one is a word standing in for a picture, and the only way to find out what the word means is to record something, export it, watch it, and come back.
Some apps improve on this with a preview. Usually it is a small animation drawn by the settings screen itself — a canvas element, a CSS transition, a looping GIF someone recorded once. It gives you a feel for the option. It is not the option. The renderer that drew it and the renderer that will produce your video are two different pieces of code that happen to have been written to agree, and the day they stop agreeing is the day you export a file that does not look like the thing you chose.
The problem with a preview that is only a resemblance
A preview built separately from the export pipeline drifts in three predictable ways.
It drifts in timing. An easing curve implemented twice — once for the animation in the settings window, once in the compositor — is two interpretations of the same curve. They look similar at a glance and diverge over a two-second zoom.
It drifts in geometry. Corner radius, border width, shadow spread and padding are all numbers that have to be scaled from a preview a few hundred pixels wide to a canvas that might be 3840 across. A preview that scales them slightly differently is showing you a shadow you will not get.
It drifts in colour. A click effect tinted in the settings window with one colour space and composited into the video in another produces two different greens.
None of these are dramatic bugs. They are the reason a setting feels approximately right and the exported file feels subtly wrong, and they are very hard to notice until you have already published something.
One compositor, drawn twice
ReScreen does not have a second renderer. The preview beside each group of settings is a short scripted recording drawn by the export compositor itself — the same code that will render your finished video, given the same settings object.
That means there is nothing to keep in sync, because there is no second implementation to drift from. The easing you see is the easing that will be applied, because it is literally the same function call. The shadow is the same shadow. The framing logic that keeps a zoom inside the bounds of the source and away from your camera bubble is the same logic, running on a scripted clip instead of your footage.
The content is different — the preview plays a short constructed scene rather than your recording — but the treatment is identical. That distinction is the whole point: you are not being shown a picture of what the setting does, you are being shown the setting doing it.
What changes when the preview is real
The practical effect is that settings become learnable by fiddling, which is how people actually learn settings.
It redraws while you are still dragging. Not on mouse-up, not after a debounce — while the slider is moving. A cursor-smoothing value is a feel, not a number, and you find it by sliding until it feels right. That is only possible if the picture is keeping up with your hand.
Choices are pictures, not words. Camera shapes, shadow presets, the real curve of each easing mode, canvas ratios, framing options and backgrounds are all picture tiles rather than entries in a pop-up menu. You pick the one that looks right instead of translating "ease-out-quart" into an expectation and hoping.
Timings are shown to scale. The Smart Zoom preview carries a timing bar drawn to the real proportions of the in, hold and out phases, and it lights up whichever phase is playing. A long hold looks long. If you want the full tour of those controls, every Smart Zoom setting is explained here, and the Smart Zoom feature page covers what the automatic pass does before you touch anything.
Options that cannot apply are hidden rather than greyed. A control that does nothing in your current configuration is not shown at all, so the panel never invites you to change something that will have no effect.
The cursor preview is magnified. Cursor size, smoothing, idle fade and click effects are shown as a labelled 2× close-up, because the differences between them are a few pixels at normal scale and invisible in a thumbnail. The guide to cursor smoothing and click effects walks through what each control changes.
Where the preview deliberately stops
A live preview that never stops is a power drain and an accessibility problem, so two things switch it off.
It stops when the window is inactive. An animation looping in a window nobody is looking at is spending battery to show a picture to an empty room.
It stops under Reduce Motion. If macOS has been told that motion is unwelcome, a settings panel full of looping animation is exactly the thing that setting exists to prevent. The tiles are still there and still show the chosen treatment; they simply hold still.
Both are deliberate, and both are the kind of behaviour that is easy to leave out and noticeable when it is missing.
The same tiles appear in the editor
The preview is not a feature of the settings window. The same tiles appear in the editor's inspector, so adjusting a canvas or a camera treatment on a real take uses the same controls, showing the same pictures, backed by the same compositor. There is one mental model, not one for setup and another for editing. Backgrounds, padding and canvas presets covers that side of it, and the canvas and backgrounds feature page lists what is available.
What this does not claim
It is worth being precise about the limits.
The preview shows a scripted clip, not your recording. It is an accurate demonstration of the treatment, not a render of your specific footage — for that, the editor's player shows your real take, and it uses the same compositor too.
It does not make exporting instant. Rendering a finished 4K video is still work, and the app still has to do it.
And it does not remove the value of watching the result. A preview tells you what a setting does; only the finished video tells you whether the recording was any good. If your workflow is the part that hurts rather than your settings, editing screen recordings faster is the more useful read.
What it does remove is the loop where you guess at a menu, export, discover the shadow is too heavy, and start again. The picture beside the slider is the picture you are going to get, because the same code drew both. If that is the part of screen recording you have been fighting, download ReScreen for macOS and drag a slider.
Filed under