Presets

Denoise, Export Ready, Remaster, Smooth 60 fps, and advanced Clean 8K. The intent door picks one from three answers about the footage.

Presets are named recipes. The usual way in is the queue rail’s list — the problems on their steps’ switches, Made for, and How far to take it — which picks a preset. The same list shows the steps that preset runs; change any of them there (size, motion, Remaster detail, file…), or switch the whole recipe with Start from, behind the Recipe header at the top of the list. A change you make is the clip’s, not the preset’s: the preset itself never changes, the Recipe header names what changed (Export Ready · no denoise), and Back to the preset beside it drops the clip’s changes with Undo. Start from follows Recipe for: with one clip selected it changes that clip, and the rest keep theirs.

Catalog

Retired alias: clean_4k still resolves as Export Ready so old queue rows keep a name.

Interlaced tape and camcorders

Most VHS, MiniDV, Hi8, and camcorder transfers are interlaced: each frame holds two fields recorded a fraction of a second apart, so NTSC tape carries 59.94 moments of motion a second (PAL tape, 50). FrameLathe deinterlaces a file like that at the full field rate by default, turning each field into its own frame. The recipe rail’s Motion step says so: 59.94 fps · from the fields.

• NTSC delivers at 59.94 fps with no frames interpolated. Smooth 60 is the same run. The motion is the motion the camera recorded.
• PAL delivers at 50 fps from its fields. Choosing 60 fps interpolates only the step from 50 to 60.
• Keep 29.97 fps (or 25) merges each pair of fields into one frame instead. It keeps half the captured motion and takes about half the time. Before you start offers it as a cheaper recipe on a very long job.
• Film transferred with 3:2 pulldown is checked when the job starts and keeps its frame rate, because splitting its fields would add judder rather than motion.
• With object removal in the recipe the frame rate is kept, because the selection names a frame of the source.

The upscale sees twice as many frames when the fields are kept, so these files take longer than a progressive clip of the same length. The estimate on the row already counts that.

Some files are interlaced but labelled progressive. HDMI and USB capture devices often record a 1080i camcorder that way, and some re-encodes drop the label. When a file at 1080 lines or fewer and 30 fps or less says progressive, FrameLathe checks a few seconds of its frames for interlaced fields. If it finds them, the file is treated as interlaced and the queue row says so.

Remaster detail

Inside Remaster, detail mode is Natural (default) or Crisp. That is not a separate preset.

Clean 8K

A 4K source renders 16K intermediate frames. On an RTX 4060 Ti that has been measured at roughly eight days per ten minutes of footage. Read the estimate on the row before you start one. The engine will still run it from the command line if you ask; the UI hides it behind More… under Start from and in the file formats so a misclick does not lock the GPU for a week. That gate is not a Settings-only toggle.

Also-fix extras

Beside the preset, the recipe rail can add denoise, stabilise, deinterlace, Even out flicker, motion, colour, Hold invented detail still, delivery format, face blur, and background removal when those features are on. More… can also reveal AV1 delivery, with a playback caveat versus HEVC.

Hold invented detail still blends high-frequency flicker after a per-frame upscale. It is for Export Ready–style jobs (upscale / denoise_then_upscale). Remaster already carries detail across frames, so the toggle is not offered there.

Even out flicker (under Also → Improve) steadies brightness that pulses from frame to frame, as on old film and worn tape. It runs before every other step and works with any preset. It corrects the whole frame’s brightness and contrast only: it does not touch colour flicker, a corner that flickers on its own, or a fade, which it keeps (the ends of a fade can come out slightly rounded). Cuts are respected, so the shots on either side of one are not blended.

The recipe rail Models block can swap the upscaler, denoise network, or matting network when that recipe actually runs those stages. Remaster keeps RealBasicVSR; Denoise-only does not run an upscaler. Colorize runs first-party and is not a bring-your-own slot. See Models.

Denoise is not guaranteed to be the neural denoise path on every machine. If the AI denoise backend is not ready, the engine may fall back to FFmpeg hqdn3d. The app reports what actually ran.