Neat Video & Neat Image community

Please try to update to the latest version available in your account.

Thank you for reporting this issue. We could also reproduce it on our test machines and are working on a solution.

Kind regards,
Vlad

1. Which version of the plug-in worked better for you, before you updated to 5.5.5? Was that still with 2 RTX 3090 at that time? Or with 3 RTX 3090 already? It could be that adding one more GPU made it all unstable. I would try to remove it for a test. It is also possible to return to the earlier ve...

The plug-in does not interact the codec nor clip directly at all. So if there is a bug in the codec and that bug shows up for example when Premiere has to get several input frames from the clip for a temporal effect (like Neat Video or another temporal effect), then you will see this problem only wh...

The codec used by Premiere is written by Adobe itself, I believe. It is not something that we can fix from our side. I guess the best way would be to report this problem to Adobe. As a user of Premiere you can send them a report. If you also send us a test project (with the source clip) that allows ...

Yes, the general idea is the same as in our scenario above, except using an external tool to edit the metadata. Our scenario achieves the same by using only built-in tools of FCPX, which may be preferable if you cannot use ffmpeg for some reason.

It may still be possible to achieve that in FCP alone. The idea is the following: 1. Create a new project with say 30 fps frame rate; 2. Add the source 16 fps clip to that project. 3. Do not change the frame rate of the clip. 4. Increase the speed (click the icon 'Choose clip retiming options' and s...

> The ideal fix would be to process the 16 fps original clip with Neat Video to clean up the noise, dust, scratches, etc and then import the cleaned up clip to FCPX for resampling to 30 fps. Yes, that would be the optimal and most correct solution. As far as I know, FCPX is not able to work with 16 ...

This may indicate a problem with the input codec used by Premiere to read/decode that MXF file. Please try to convert that MXF file to something else, for example, to ProRes, and then import that new ProRes clip into your main project instead of that MXF file. Then apply the filter to that ProRes cl...

No, that doesn't seem to be normal.

Please check if you perhaps do something like this in the project. Also, please see this article for some more ideas on how to avoid any unnecessary slowdown in Premiere.

Thank you,
Vlad

At this time no, unfortunately.

Neat Video v5.5.5 Neat Video v5 plug-ins have been updated to version 5.5.5 This update adds support to both newest hardware and versions of host applications. The Neat team has added support to a big number of updated versions of host applications. Adobe Premiere Pro and After Effects 2023, DaVinc...

Could be many things, like disabled effects on the side of FCPX or just simply old version of the plug-in that needs to be updated. Please check the version first and update if necessary.

Thank you,
Vlad

The method below may help in some cases. Please try it: 1. Switch to Advanced mode: use the menu Tools > Advanced mode 2. Go to Temporal Filter > Jitter of Details and set the Threshold to -100% Another or additional option is the following: 1. Set the noise reduction amount to 100% in Spatial Filte...

Thank you for reporting this. We will try to reproduce and also analyze the file to see what happened.

Kind regards,
Vlad