Cookies are disabled. This site requires cookies turned on to run properly. Please enable cookies and reload this page.

Best noise reduction
for digital video
Logo

Known Issues for Final Cut Pro

Current Issues

The most compatible and stable version of FCP X is version 10.4.x (Motion 5.4.x). We recommend to use these versions.

  • Slow response if skimming and background render are enabled in FCP X (all versions)
    FCP X with enabled skimming and background rendering may be slower to respond to user actions when a computationally-intensive filter (such as Neat Video) is added to the project. Please consider disabling skimming and/or background rendering in FCP X Preferences. Alternatively, temporarily disable Neat Video itself (in FCP X’s panel Inspector > Video > Effects > Reduce Noise) when not adjusting Neat Video's settings.
     
  • Unnecessary re-rendering of clips (all versions)
    FCP X may decide (sometimes without an obvious reason) to re-render a clip where a video effect is applied. When that happens with a clip where Neat Video is used, re-rendering may take a considerable time (because Neat Video is very computation intensive). FCP X may trigger re-rendering when a transition is added to a clip, when another effect is added to the clip, when the clip is cut, etc. In many cases, such re-rendering is unnecessary but it cannot be avoided because of the design of FCP X itself. To avoid wasting time on re-rendering, we recommend to disable background render and to trigger render manually when it is needed.

Older Issues

  • Adding Neat Video may cause preview to go black (FCP X 10.2)
    Adding Neat Video to a clip may cause the preview to go black in some cases (this may involve using transitions, presence of several clips, multicam clips). This issue seems to be caused by an unexpected behavior of FCP X 10.2.

    We have implemented a workaround to let Neat Video avoid that problem. To use it please download and install the latest available version of Neat Video plug-in for FCP and/or update FCP X itself to a newer version.
     
  • Visual artifacts in large frames (FCP X versions prior to 10.2)
    FCP X 10.0.8, 10.0.9 and 10.1: FCP X may produce visual artifacts: mirrored right part of the frame (or corruption in all parts of the frame when running on older GPUs) when processing large frames such as 5k clips (5120 x 2160) using certain type of plug-ins (plug-ins doing temporal processing; Neat Video is one of those). The artifacts are produced by FCP X itself.
    Update: This problem seems to be fully fixed in FCP X 10.2.
     
  • Blank frame in Neat Video window (FCP X versions prior to 10.2)
    FCP X 10.0.7, 10.0.8, 10.0.9 and 10.1 (to some extent): These versions of FCP X (unlike 10.0.6 and earlier versions) have a bug, which causes FCP X to provide a blank frame to Neat Video's window when Neat Video is not the first effect added to the clip. To avoid that please manually move Neat Video's Reduce Noise effect to the top of the filter stack in FCP X (above all other effects in that clip).
    Update: This problem seems to be fully fixed in FCP X 10.2.
     
  • Missync between video and audio channels (FCPX 10.0.8 and 10.0.9)
    FCP X 10.0.8 and 10.0.9 have a bug, which causes FCP X to introduce a missync between video and audio channels if a filter plug-in of certain type (filter doing temporal processing) is added to a clip with a preceding transition. Removing the transition resolves the missync problem.
    Update: this problem seems to be fully fixed in FCP X 10.1.
     
  • Visual artifacts with Radeon HD 7950 (FCP X 10.0.8)
    There is a known problem in FCP X 10.0.8, which may cause FCP X to produce visual artifacts (vertical lines) when running on AMD Radeon HD 7950 while plug-ins of certain type (Neat Video is one of them) are used. The artifacts are produced by FCP X itself.
    Update: this problem seems to be fully fixed in FCP X 10.1.
     
  • Corrupted frames: incorrect colors, inverted, mirrored, etc. (FCP X 10.0.6 and 10.0.7)
    FCP X 10.0.6 and 10.0.7 (unlike 10.0.5) and Motion 5.0.5 and 5.0.6 have a bug, which produces corrupted frames (incorrect colors, inverted, mirrored, etc.) when certain types of effect plug-ins are used. Not only Neat Video, other effect plug-ins too, including even some of the effects developed by Apple. Please update to a newer version of FCP X to avoid that bug.
     
  • No filtration when applied to clip with pixel aspect ratio other than 1.0 (FCP X 10.0.6)
    FCP X 10.0.6: This version of FCP X may not work correctly if the clip's pixel aspect ratio is different than 1.0. That incorrect behavior of FCP X may effectively disable Neat Video and it will not produce expected noise reduction in FCP X preview or render. Please update to a newer version of FCP X to avoid that bug.
     
  • No filtration if clip is located in non-main timeline (FCP X 10.0.4 and 10.0.5)
    FCP X 10.0.4 and 10.0.5: if the clip where Neat Video is applied is located in non-main timeline, the filter may not work. The problem is caused by a bug in FCP X (10.0.4, 10.0.5): FCP X does not provide all frames requires to conduct temporal processing. Please update to a newer version of FCP X to avoid that bug.
     
  • Neat Video plug-in may indicate a lack of free GPU memory (some old versions)
    On systems with CUDA-enabled video cards, Neat Video plug-in may try to use CUDA to speed up processing and in some cases during the first start of FCP X, the plug-in may give an error indicating a lack of free GPU memory. Please restart FCP X in such a situation, this may help to resolve the problem. Alternatively, disable use of GPU in Neat Video's Preferences: open the main window of the plug-in using the Options window popup menu, go to menu Tools > Preferences > Performance and select to use CPU only.
     
  • Cannot use Neat Video in older versions of FCP X (FCP X 10.0.3 and older)
    The versions 10.0.3 and older are not technically capable of running Neat Video.
    Please update FCPX to a newer version.
  • Error message about a memory block (FCP 7 and 6)
    FCP 7 and FCP 6: these 32-bit versions of FCP often experience memory-related problems caused by the general limitation of the 32-bit architecture. If you receive an error message where Neat Video complains about not being able to receive a memory block from the host application or from OSX, please try the following workaround. Restart FCP and go to its menu Preferences >System Settings >Memory & Cache >Application. By default, the amount of memory there is set to 100%. Try reducing the amount to 60-70% and even further to 30-50%. Then restart FCP and try to use Neat Video again.
     
  • FCP 7 losing the Neat Video filter settings (FCP 7 on OSX 10.7.0/10.7.1)
    FCP 7 and OSX 10.7.0/10.7.1: There is a bug in the Mac OSX Lion 10.7.0 and 10.7.1 that shows up in FCP 7 running the Neat Video plug-in. This bug in Lion causes FCP 7 to not save (and therefore lose) the filter settings (profile and preset). The bug affects any FCP plug-in that uses custom parameters, it is not specific to Neat Video.

    Update: The bug has been fixed by Apple in OSX 10.7.2. If you need to use FCP 7 with Neat Video plug-in, please update OSX to version 10.7.2 or newer (or use FCP 7 in OSX 10.6 or 10.5).
     
  • Options button may disappear (FCP 7 and 6)
    FCP 7 and FCP 6: these versions of FCP have the following bug. When you use two monitors and move the FCP window to the secondary monitor, the Options button in Neat Video settings displayed by FCP may initially change its position on the screen and then may disappear completely. The position of the button is controlled by FCP and there is a bug in FCP code.

    To restore the Options button please move the FCP windows back to the main monitor.
  • FCP 6 supplies adjacent frames with reduced quality on FullHD clips (FCP 6)
    FCP 6: this version of FCP has the following bug. When you apply Neat Video plug-in to FullHD clips, FCP supplies to the plug-in adjacent frames with reduced quality, which leads to lowered quality of the rendered output. This does not happen with lower resolution videos.

    The only currently known solution is to upgrade to a newer version of FCP.