Neat Video & Neat Image community

> Neat Video 5.2.3 plug-in for VirtualDub

Please try to run the latest available version 5.5.x.

Thank you.

FCPX 10.6.1 is very old. Please try to install the latest version 10.6.4.

No, we are not waiting anymore, because Apple has released 10.6.4 with a fix to that problem.

Please kindly email support [at] neatvideo.com

From our e-mail exchange we found out that the render become more stable when the output format is ProRes, instead of H.264. Apparently H.264 is more resource intensive, which causes MacOS to shoot off processes like plug-ins, leading to that "The plug-in is not responding." situation.

If you do not see the results from a specific CPU model, then it is most likely that we haven't received such results from anyone yet and we do not have it in our labs yet as well. If you have access to a specific new CPU model, please run the NeatBench test and send us the results. We will likely i...

Incorrect input data means that some of the input frames sent by After Effects to Neat Video for processing are not right in some way. For example in your screenshot you can see that the central frame has the zero width and height, which is clearly abnormal. That means something is done incorrectly ...

> Windows Task-Manager shows

That is a problem of Task Manager

Please change its indication mode from "3D" to "CUDA", "Compute_0" or "Compute_1". Some of those non-default modes will show the actual computing load on the GPU.

Vlad

Our tests confirm that as well. FCP 10.6.4 now works correctly with Neat Video as well as with FCP's built-in effects that earlier shown the same problem.

Vlad

Thank you for the suggestions. These are in the wish list now and your voice is also added.

Thank you,
Vlad

Thank you very much.

We have tried to reproduce the problem using our own tests on a Mac Pro with one Xeon but it worked without problems. So none of our Intel machines reproduced the issue. However it is still possible that dual Xeon may be the key to issue.

Vlad

I believe we received one report where a Xeon-based system was showing the same symptoms but we have not been able to reproduce that on any of our Intel-based machines. I will double-check with my colleagues tomorrow.

Vlad

Yes, it is a known bug of FCPX 10.6.2 and 10.6.3 described in this page. There are two known workarounds at this time. Apple is working on this issue now.

Vlad

If you install using all default settings, then the product is installed into /usr/local/Neat Video v5 OFX
but also a link is added into /usr/OFX/Plugins because that is the standard location for OFX plug-ins
where most OFX applications look for plug-ins.

Vlad

Thank you for the update. This seems to be a solution for the case of using flatpack.

Just a small comment on the directory to link to. Perhaps it would be simpler to link to /usr/OFX/Plugins
where Neat Video's plug-in is present and the path does not contain spaces already.

Thank you,
Vlad