Neat Video & Neat Image community

The official support for Vegas 17 starts in Neat Video 5.1. The older versions might work in some cases but that is not officially supported. The last version of Vegas officially supported by Neat Video 4.x is the version 16.

Vlad

I would try to use a directly available mechanism of copy&pasting an instance of the filter from one clip to another. Here is how it would work in Vegas: - add the filter to a clip; - set up a noise profile in that instance of the filter, adjust the filter settings, apply; - copy (Ctrl+C) the event ...

We do not normally detail such minor updates. I believe there were some minor updates like some internal library or certificate update or so.

Vlad

We discussed the re-rendering behavior of FCPX with Apple some time ago and they general idea was that if it takes place, then that means FCPX thinks that is either necessary or may be necessary. The plug-in cannot change that from its side. That decision making is taking place on the side of FCPX i...

If you input TIFFs, then please save output files in TIFF format as well. This way you will preserve all details of the color profile and the image will look the same.

Please send a direct message to support [at] neatvideo.com, lets continue there.

Thank you,
Vlad

Thank you for checking. We will try to figure out what could be causing that.

Vlad

> I tried the bench, it succed

Thank you for testing NeatBench.

Please try to run it in 4k resolution too using this command:
NeatBench5 3840x2160

Thank you,
Vlad

Please try to run Neat Bench to check if it is able to complete its test or it shows similar errors.

Thank you,
Vlad

In Neat Video Preferences > Performance, you can control which of the available GPUs to use for Neat Video processing and how much of the GPU memory to let it use. I recommend to try limiting Neat Video to one of those GPUs (perhaps one of 2080ti) and then running the render for a test.

Vlad

We believe that problem was fixed in Premiere CC 2019 v13.1.3.

Vlad

The problem with Lumetri is that it has a bug that causes Premiere to re-render many frames several times. Hence a slowdown and higher memory usage. Try to render a short test clip with Lumetri (placed after Neat Video) and without Lumetri at all. It is possible that there is an appreciable differen...

1. Lumetri is a performance killer when Lumetri is applied before/above a temporal effect like Neat Video. Move Neat Video above Lumetri to avoid that. Better put Neat Video as the first effect. 2. 8GB of RAM may be somewhat low for modern video processing. Check the memory utilization during render...

Looks like the latest update of Premiere added a new problem. We will try to reproduce that. In the meantime please try to separately apply noise reduction and warp stabilizer to avoid that issue. You may also want to try placing warp stabilizer into a nested sequence (Clip > Nest) before adding Nea...

Do you receive any crash logs when that happens? Please send those to support [at] neatvideo.com for analysis.

Does Premiere crash if Warp is disabled?

Thank you,
Vlad