Neat Video & Neat Image community

I noticed FCP 10.6.4 was just released. There is a single listed fix: "Fixes an issue where video frames may be out of order during playback or export". Anyone experiencing this problem should get this version and test it.

I confirm it also happens if sending the timeline to Compressor for export. Update on 3rd-party plugins affected by this (besides Neat Video)

- CoreMelt Lock & Load stabilizer 4.0.2
- Digital Anarchy Beauty Box 5.0.4

It also happens with the built-in FCP chroma keyer.

This can also happen if using CoreMelt's Lock & Load stabilizer or the FCP built-in chroma keyer. To reproduce that I used four stacked 1080p/29.97 ProRes 422 clips, each scaled to 50% so they all appear on the viewer, and retimed the clip to 25% speed. So it's clearly not unique to Neat Video; ...

In further testing today I have seen this on these built-in FCP effects: Film Grain, Raster, Stencil and Subway Shadow. On those it seems to happen less frequently than the "Trails" effect and it might require a retimed clip to manifest but I'm not sure. It is consistent with the original ...

Another user just completed a series of tests on a 2019 Mac Pro, config: 12-core, 96 GB RAM, Afterburner, 2 x AMD Radeon Pro W5700X, macOS 12.4, FCP 10.6.3. He also tried NeatVideo SR 5.5.2 combined with variations of the above-mentioned scenario. He never saw it.

Here is a DropBox link to a simple problem replication, along with a .txt file describing how to run it. The package is very small, only about 62 megabytes. It includes an FCP project XML file which recreates the needed timeline. Initial setup is very simple: just load the XML, then relink to the si...

I list below the most reliable simple scenario which reproduces the problem. This works using only a short retimed 1080p ProRes 422 clip and the built-in FCP "Trail" effect (thanks to Neat Video for that tip). It works for 23.98 in a 23.98 timeline, 29.97 in a 29.97 timeline and 59.94 in a...

Vlad/Team: what is the latest confidence this can be reproduced on Intel? I have a semi-reliable small replication that works on M1 Ultra and M1 Max MacBook Pro 16 but I cannot reproduce it on a top-spec 2019 i9 MacBook Pro 16. All are running FCP 10.6.3 and Monterey 12.4. All have the same 4k/23.98...

Thanks for the comment about compound clips, I will test that. If breaking those apart works for you, OK but in my testing the problem is not isolated to Neat Video (compound clips or not), therefore it's not caused by a bug in Neat Video. It can happen when using other multi-frame effects such as t...

M1 Ultra has two H264/HEVC decode engines, four H264/HEVC encode engines and four ProRes encode/decode engines. M1 Max has half of those. On current versions of MacOS, hardware acceleration is enabled by default for apps. It can be disabled programmatically by apps using the Video Toolbox framework ...

I am investigating this issue for my video team. Is there any updated info? Here is what I've observed so far, with most testing done on a Mac Studio M1 Ultra, MacOS 12.4, FCP 10.6.3 and Neat Video 5.5.2 (SR): - It is not restricted to Neat Video, but can happen on retimed clips, especially if invol...