Neat Video & Neat Image community

We will update the history of changes in the coming days. Please wait.

Unfortunately no, the situation has not changed much in Edius 11. The traditional plug-in interface of Edius has not changed in Edius 11. The new OFX interface is not fully implemented, so some crucial features are still missing, making it impossible for Neat Video OFX to fully work. We hope that th...

Thank you for sharing your finding regarding Input LUT. It may indeed be a good option for such situation. We will test it from our side too as a possible general recommendation. I agree with you that this type of issues will become more common now with more people using these news color spaces offe...

Resolve uses the GPUs, its codecs may use the GPUs, Neat Video uses the GPUs and possibly other software in the system use the GPUs, so there is some overlap and competition for the same resources that can take place. So there is nothing unusual that they affect each other in somewhat unexpected way...

Please excuse the delay on our side. We have spent some time on studying this issue, which is on one hand looks somewhat new in 2023 and 2024 versions, but on the other hand it is still another manifestation of the same old problem of Premiere that I mentioned above: Premiere processes video differe...

Thank you for sending the test project. It will take us some time to update our machines for this new Premiere, and then we will run the tests using the test project. Premiere's incorrect behavior is triggered by adding a video effect, yes, that is correct. The effect doesn't even have to do anythin...

Please kindly create a fresh new test project with just one short clip and just one effect (Reduce Noise v5 (SR)) and verify that the problem is directly reproducible in the test project. Then please export the project as XML (FCP's menu File > Export as XML) and upload the XML file and source clip ...

Please kindly prepare a small test project with one short clip and Neat Video applied to it. Please verify that this test project allows to reproduce the problem on your machine and then please upload the test project and source clip to https://wetransfer.com/ for us (support [at] neatvideo.com). We...

This looks like that old design problem / bug of Premiere itself showing up in yet one more scenario. The problem is that Premiere processes video data differently when working using GPU vs using CPU alone. Lets demonstrate that directly. Please remove Neat Video from the clip, then go to Premiere's...

Possibly. It all depends on the noise in different scenes. If is more or less the same in strength, texture and color, then it should be fine. If it is very different, then going one by one would work better.

1. It is usually easier to manage noise profiles and filter settings of Neat Video when NV goes first, but this does not require to use NV first. It can be used second or last too. Just make sure you re-build the noise profile and possible readjust the filter settings after you change the order of e...

I do not see an attached clip, only a screenshot showing one frame. The flicker reduction controls are all in the Temporal Filter, so it is best to adjust those there. The Spatial Filter will not help much in this situation. Please re-watch the referenced tutorial on Youtube, it shows those controls...

Can you change the frame using the timeline selector of the main window of VD2 itself?

Vlad

Thank you. There is not much noise in the most of the image but the trees are mostly noise with little details under the noise. Taking that into account, your result is quite good. But it is possible to slightly improve it by disabling the spatial filter. Please see how that is done in the attached ...

Please create a fresh new test project with just one clip and just one effect (Reduce Noise v5 SR) applied to that clip. Please verify that the problem is reproducible in the test project and then upload the test project and source clip to https://wetransfer.com/ for us.

Thank you,
Vlad