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 Premiere Pro (Standard plug-in)

Current Issues

  • Wrong frames served if Trim/Razor is applied to clip (Premiere CS6 – 2019, partial workaround implemented in Neat Video)
    When a video effect plug-in doing temporal processing (for example, Neat Video) is applied to a clip that was cut or trimmed (using the Razor tool or any other method available in Premiere), Premiere may serve incorrect input frames to the plug-in (you usually can see that in preview), which may result in lower quality filtration (with effective temporal radius=0) due to lack of adjacent frames. This is caused by a known bug in Premiere, which has been confirmed by the developers of Premiere.

    Neat Video v4.0.3 (and newer versions) includes an automated workaround, which allows Neat Video to compensate that Premiere bug in most cases. Please update from 4.0 to 4.0.3 (or newer) to be able to use it. It should work automatically in most cases except one: if you cut the clip or change the trim points already AFTER adding Neat Video to that clip, then please simply re-open the window of the plug-in and click Apply again.

    Another known workaround is to use the following steps when you need to apply Neat Video to a clip that has been cut in one way or another:
    1. Use Premiere's menu Clip > Nest on the clip where you have a cut; this creates a new Nested Sequence inside the main timeline.
    2. Add Neat Video to that new Nested Sequence in the main timeline (do not explicitly open the Nested Sequence to add Neat Video inside the Nested Sequence).
    3. Keep working with that new Nested Sequence as you would normally do with the original clip.
    If you still cannot resolve the problem using the above workarounds, please consider using the Second Revision plug-in, which avoids that Premiere bug by using a different Premiere API.
     
  • Lumetri above Neat Video slows down render (Premiere CC 2015 – 2019)
    If Lumetri Color is applied before/above Neat Video (or another temporal effect), then the overall render speed of Premiere will decrease by a factor of 5 or more (in Premiere 2019, by a factor of 2).
    As a workaround, place/move Neat Video's Reduce Noise v5 above Lumetri (and re-build the noise profile there).
     
  • Warp Stabilizer above Neat Video hangs (Premiere CC 2015 – 2019)
    If Warp Stabilizer effect is placed above Neat Video, then Warp Stabilizer sometimes hangs during tuning (this seems to be caused by a bug in Premiere). As a workaround, place/move Neat Video above Warp Stabilizer (and re-build the noise profile there).
     
  • Time Remapping produces stuttering with temporal effects (Premiere CS6 – 2019)
    If you apply Time Remapping (for example 25%) or Speed/Duration to a clip, then Premiere may send incorrect input frames from that clip to Neat Video (or built-in temporal effects of Premiere itself), usually in the second half of the clip. That can cause the output video to stutter. Time Remapping also causes similar problems when some of Premiere's built-in effects are used instead of Neat Video. Because of that, it is generally best to avoid using time/speed manipulations (such as Time Remapping) together with temporal effects (such as Neat Video).

    A possible workaround is to use nesting for the clip with Time Remapping:
    1. Use Premiere's menu Clip > Nest on the clip where you have Time Remapping applied. This creates a new Nested Sequence inside the main timeline.
    2. Add Neat Video to that new Nested Sequence in the main timeline (do not explicitly open the Nested Sequence, do not add Neat Video inside the Nested Sequence).
    3. Keep working with that new Nested Sequence as you would normally do with the original clip.
  • Immersive Video: "This effect requires GPU acceleration" (Premiere CC 2018 – 2019)
    An Immersive Video effect cannot work if Neat Video is added below/after it. The red text "This effect requires GPU acceleration" is shown by the corresponding Immersive Video effect in such cases. The same happens with many of Premiere's built-in effects.
    As a workaround, place/move Neat Video above the Immersive Video effect (and re-built the noise profile there).

Older Issues

  • Black highlights in frames served to Neat Video (Premiere 2019 until v13.1.3)
    When working with certain types of clips (for example, 10-bit ones), Premiere servers frames with black highlights to Neat Video (and other temporal effects). This is caused by a bug in Premiere's component reading the input clip.
    A possible workaround is to transcode the clip to another format that uses a different video codec that has no such problem in Premiere.
    This problem is fixed in Premiere 2019 v13.1.3.
     
  • Reduced contrast in frames served to Neat Video (Premiere 2019 until v13.1.3)
    When working with certain types of clips (for example, 10-bit ones), Premiere servers frames with changed contrast to Neat Video (and other temporal effects). This is caused by a bug in Premiere's component reading the input clip.
    A possible workaround is to transcode the clip to another format that uses a different video codec that has no such problem in Premiere.
    This problem is fixed in Premiere 2019 v13.1.3.
     
  • MXF clips: corrupted frames served to Neat Video (Premiere CC 2014 and possibly other versions)
    When working with an 8K MXF clip (from Sony FS7 and possibly from other models), Premiere may fail to return all requested input frames to Neat Video. Which shows up in Neat Video window as missing frames: some of the thumbnails (at random, not all of them) are displayed as N/A. This issue affects only previewing in Neat Video and Premiere; the final render done by Premiere usually doesn't show any issues. The problem seems to be caused by a possible bug in Premiere. It has been reported to Adobe.
    A possible workaround is to transcode the source MXF clip to another format before using the new clip in Premiere.
     
  • Adjustment Layer: wrong frames served to Neat Video (Premiere CS6 and CC)
    Incorrect operation of Premiere's temporal API in adjustment layers causes Premiere to send wrong frames to Neat Video (when Neat Video is applied to an adjustment layer) in cases when the adjustment layer begins to the right of the start of the clip underneath (not in the same point). This problem is fixed in newer versions of Premiere.
     
  • RGB Color Corrector: “error compiling movie” (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.

    Possible workarounds:
    1. Disable GPU in Premiere's Mercury Engine (this workaround doesn't always work).
    2. Apply and render RGB Color Corrector and Neat Video separately.
    3. Use another version of Premiere (CS5.x, CC are known to work correctly).
  • Cannot open Neat Video window once effect is copied (Premiere CC 2017 – 2018)
    If Reduce Noise effect is copied from one clip to another, or the whole clip with the effect is copied, then it may be not possible to open the window of Neat Video in the original clip anymore. This seems to be caused by a bug in Premiere.
    This problem is fixed in Premiere 2019.