LensNode is one plugin, but each host exposes it a little differently. This page collects the minor UI and UX differences you’ll notice when running LensNode in Final Cut Pro compared to the OFX versions.

Lens Menu

The lens selection menu in Final Cut Pro is laid out differently. Here, a cascading menu is used to select your lens profile, instead of the three dynamic dropdowns in the OFX version. See Lens Selection in the full guide for the OFX layout.

Depth Maps & Depth Gain

Since Final Cut Pro is effect-based and has no node inputs, the depth-map workflow is a bit different. In order to supply LensNode with a depth input, scroll to the bottom of the plugin effect controls in the Video Inspector panel. There you will see Depth Input. Click the rectangle with the downward-pointing arrow in it, then select a clip to be your depth input. In Final Cut Pro, the Depth Gain parameter is always called Depth Gain, but it still functions the same way Bokeh Boost does when no input is connected to the Depth Input. See Bokeh Boost / Depth Gain in the full guide.

Save Defaults

Final Cut Pro has no Save Defaults button like the OFX version’s User Defaults. Instead, users can set their own defaults by editing the .moef preset file directly.

Preview Speed

You may notice Final Cut Pro can be quicker to preview LensNode with than on other platforms. This is because it has a very efficient adaptive resolution system, allowing you to scrub through and preview footage very quickly. Other host platforms like Resolve allow you to lower your playback resolution manually, but Final Cut Pro does this automatically.