Known Issues for Premiere Pro (Second Revision plug-in)

Current Issues

• Lumetri above Neat Video slows down render (Premiere CC 2015–2023)
  If Lumetri Color is applied before/above Neat Video (or another temporal effect) or is applied to the master clip, then the overall render speed of Premiere will decrease by a factor of 5 or more (in Premiere 2019 or newer, by a factor of 2).

  As a workaround, place/move Neat Video's Reduce Noise v5 SR above Lumetri (and re-build the noise profile there). Do not apply Lumetri to the master clip if Neat Video is applied to the clip.

• Complex frame rate transformations produce stuttering with Neat Video and other temporal effects (Premiere CS6–2023)
  For example if you put 100 fps video into 25 fps sequence and apply Speed duration or Time Remapping = 25% to a clip, then Premiere may send incorrect input frames from that clip to Neat Video. That can cause the output video to stutter. Frame rate transformations also cause similar problems when some of Premiere's built-in effects are used instead of Neat Video.

  A possible workaround is to use nesting for the clip with frame rate transformations:

  1. Use Premiere's menu Clip > Nest on the clip where you have frame rate transformations 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.

• Warp Stabilizer above Neat Video hangs (Premiere 2019–2023 and possibly other versions)
  If Warp Stabilizer effect is applied before/above Neat Video, then Premiere sometimes hangs during Warp Stabilizer's Analysis process and simultaneous tuning of Neat Video. 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), or use clip nesting before applying Neat Video.

• Slowdown with Warp Stabilizer (Premiere 2019, 2023 and possibly other versions)
  Using Warp Stabilizer with Neat Video can cause a significant (1.5x–15x) slowdown that can be avoided in different ways depending on the mode of Warp Stabilizer.

  1. With "Stabilize, Crop, Auto scale" mode, it is best to use nesting:

     1. Add Neat Video to the clip;
     2. Use Premiere's menu Clip > Nest on that clip;
     3. Add Warp Stabilizer to that new Nested Sequence in the main timeline (do not explicitly open the Nested Sequence, do not add Warp Stabilizer inside the Nested Sequence).

  2. With "Stabilize, Synthesize Edges" mode, it is best to apply Neat Video and Warp Stabilizer completely separately, for example:

     1. Add Neat Video to the clip;
     2. Render out to produce an intermediate clip with noise reduced;
     3. Use the intermediate clip as input in your project where you want to apply Warp Stabilizer to that video.

• VR Projection above Neat Video slows down processing (Premiere 2019–2023 and possibly other versions)
  If VR Projection is applied before/above Neat Video (or above another temporal effect), then the overall speed of Premiere processing will significantly decrease. In some cases, Premiere may even crash.

  As a workaround, place/move Neat Video's Reduce Noise v5 SR above VR Projection (and re-build the noise profile there). This however will make the "Stretch To Fill Frame" option of VR Projection not working correctly, so if you need to use that option, then it is necessary to apply VR Projection and Neat Video separately, for example in two separate projects.

• MXF clips: corrupted frames served to Neat Video (Premiere 2018–2020, 2023–2024 Mac ARM)
  When working with a Sony encoded MXF file, Premiere 2018 may fail to return all requested input frames to Neat Video 5 SR. This may show up as an error message: "Premiere failed to check out source frames for Neat Video. The source video could not be correctly decoded by Premiere." This may also lead to black frames in the final render. (In version 2019 and newer, Premiere itself reports that as "Error retrieving frame N at time N from the file: X, substituting frame.") The same problem may also cause issues when using other temporal video effects including some of Premiere's built-in video effects.

  The problem seems to be caused by a bug in Premiere's MXF codec. It has been reported to Adobe.

  One possible workaround is to transcode the source MXF clip to another format before using the new clip in Premiere.

  Sometimes it is possible to use the Standard plug-in instead of SR plug-in to work with such an MXF clip in Premiere. The old interface of Premiere does not show that specific bug for some MXF files, so the Standard plug-in can avoid it.

• 'Set to Frame Size' option produces frames with gray borders for Neat Video (Premiere, All versions)
  If a sequence's frame size is greater than the clip's frame size and "Set to Frame Size" is applied to the clip, then you will see frames with gray borders in Neat Video plug-in window. This may lead to lower quality of filtration. That happens because "Set to Frame Size" is applied after all other effects have been applied (as it changes Motion->Scale parameter in Effect control window). It is better to use "Scale to Frame Size" which is applied before other effects.

• Frames from trimmed parts of clip are still accessible to Neat Video (Premiere, All versions)
  If the clip is trimmed, then the frames outside the remaining part are still sent by Premiere to Neat Video and are used in Neat Video temporal filter. This is the way Premiere API handles trims. If you need to exclude those extra frames completely, please use Clip->Nest.

• When Speed/Duration greater than 100% is applied, Neat Video cannot get frames from the end of the clip (Premiere 2017–2023)
  If you apply Speed/Duration greater than 100% to a clip, then it may be not possible to receive frames from the end of the clip to open Neat Video window. It may receive frames from the beginning of the clip instead.

  This seems to be caused by a bug in Premiere.

• Master Clip serves low resolution frames to Neat Video (Premiere, All versions)
  If Neat Video is applied to Master Clip, then Premiere sometimes sends lower resolution frames to Neat Video regardless of Program Monitor quality settings. In this case, please find the Source monitor window in Premiere and set the recommended quality settings in it: set the Playback/Paused resolution to Full and enable the "High Quality Playback" option. If this does not help, please try several times to get (using the Prepare button) full resolution frames to build a profile. Verify the resolution using the indicator in the bottom of Neat Video window.

• Immersive Video: "This effect requires GPU acceleration" (Premiere 2018–2023)
  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).

• If Adjustment layer's resolution is different from sequence's resolution, Neat Video shows a warning (Premiere 2019–2023)
  If Neat Video is applied to an adjustment layer having the size larger than the size of the sequence, then Neat Video shows a warning about reduced resolution of the frame and suggests to enable the full resolution preview in Premiere. The warning is harmless and can be ignored. To remove the warning, make sure the size of the adjustment layer is the same as the size of the sequence.

• Exporting a large-frame sequence without Maximum Render Quality option in lower resolution reduces render quality (Premiere CC 2014–2023)
  When exporting a project that has the frame size of 3 megapixels (or larger) into a lower resolution output clip (like fullHD) with the "Use Maximum Render Quality" option disabled in the Export dialog, Premiere sends to Neat Video frames in reduced resolution (as compared with the full resolution used to build the noise profile for the clip), leading to less accurate noise reduction.

  A possible workaround is to enable the "Use Maximum Render Quality" option in the Export dialog or to reduce the project resolution to the final lower resolution and then apply "Scale to frame size" to clips.

• Reduced contrast, color distortion in frames served by Premiere to Neat Video (Premiere 2019–2023)
  When working with certain types of source clips (for example, ProRes Raw, RED, etc.), Premiere may serve Neat Video (and other temporal effects) with frames showing reduced contrast and/or color distortion. This is caused by a bug in Premiere's components (codecs) reading and decoding the specific types of source clips.

  A possible workaround is to transcode the source clip to another format that uses a different video codec that has no such problem in Premiere.

  For ProRes Raw this problem was fixed in Premiere 2019 v13.1.3 but re-appeared in v14.0.1.

Older Issues

• Non-standard FPS project with Neat Video renders with stuttering (Premiere CC–CC 2018; automatic workaround added in Neat Video v5.1)
  If you create a new Sequence by adding a new clip into an empty project and the clip has a non-standard frame rate (a frame rate that doesn't match any of the frame rates offered by Premiere in Sequence Settings), then Premiere behaves incorrectly:

  • it automatically sets Sequence Settings -> Timebase to 10 fps,
  • it reports that 10 fps frame rate to Neat Video, but actually works based on the frame rate of the clip.

  That causes the following problems:

  • if you render/export the project, then the output video will be stuttering;
  • rendering may be significantly slower than usual.

  To avoid those problems please verify the Timebase in Sequence Settings and make sure it is set to the right value.

• 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 serves 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.

• Copy-pasting Neat Video effect creates memory leak (Premiere CS6, CC)
  Premiere leaks memory when copying the effect using the Copy and Paste commands due to a bug in Premiere (restarting it restores the memory resources).