- In FCP X 10.0.8: 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. We have informed Apple and
they currently work to fix this problem in FCP X.
- In FCP X 10.0.8: there is a known
problem in FCP X itself, 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 and Apple is currently busy trying to make
FCP X work correctly with Radeon HD 7950 in such situations.
- In FCP X 10.0.8: FCP X
10.0.8 has 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. Apple is currently looking into this FCP
- In FCP X 10.0.7 and 10.0.8: FCP X
10.0.7 and 10.0.8 (unlike 10.0.6 and earlier versions) have a bug, which
causes FCP X to provide a blank frame to Neat Video's Options 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).
- In 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
Solution: please upgrade FCP X to version 10.0.8. Version
10.0.8 does not have that bug. Upgrading Motion will help
to fix the problem in Motion as well.
- In 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 behaviour of FCP X may effectively disable Neat Video
and it will not produce expected noise reduction in FCP X preview or
- In FCP X: 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.
- In FCP X: 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.
- In FCP X: 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 or
temporarily disabling Neat Video (in the panel Inspector > Video > Effects
> Reduce Noise) when not adjusting Neat Video's settings.
- In 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 FCP7 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. The bug has been fixed by Apple
in OSX 10.7.2. If you need to use FCP7 with Neat Video plug-in,
please update OSX to version 10.7.2 or newer (or use
FCP7 in OSX 10.6 or 10.5).
- In Premiere CS6: applying both CS6's RGB Color Corrector
and Neat Video to the same clip may cause Premiere to fail a render with
the error message: "error compiling movie". This seems to be
caused by a bug in Premiere CS6's RGB Color Corrector itself and is reproducible
with other plug-ins (instead of Neat Video) as well.
1. (doesn't always work) disable GPU in Premiere's Mercury Engine;
apply and render RGB Color Corrector
and Neat Video separately;
3. use another version of Premiere (CS5.x,
CC are known to work correctly).
- Older Neat Video (v2.5 and older) for Sony Vegas could produce a short
stutter in the beginning of a filtered clip.
The effect is caused by the limitation of Vegas plug-in
architecture and can be resolved by using a newer version of the plug-in
(v2.6 and newer). The new versions of Neat Video for Vegas include a
Lag Mode" option
in temporal filter settings to compensate for that
functional limitation of Vegas. Using the option allows
to avoid the stutter and lag.