10.2- Neat Video doesn't work

Just attempted Neat Video on a clip and the clip went black. Deselected and the clip reappeared. Seems to be a glitch.

truelife2 wrote: Just attempted Neat Video on a clip and the clip went black. Deselected and the clip reappeared. Seems to be a glitch.

Works for me, do you have the latest version of Neat?

So odd- I'm using footage from FS7 (XAVC-I) and A7S (MP4). Seems pretty straightforward. Both clips go to black with no other effects used.

I just tried it on my end and it works fine. FCP X 10.2 and the latest Yosemite

truelife2 wrote: So odd- I'm using footage from FS7 (XAVC-I) and A7S (MP4). Seems pretty straightforward. Both clips go to black with no other effects used.

Maybe trash prefs?

Yes, try trash preferences. Worst case scenario: Neat doesn't with those particular files? However, did they work with Neat before 10.2?

Either way, it might be time for Neat to come out with another upgrade since the latest came out in October.

Good Luck

Yeah I've trashed prefs a bunch in recent days and it hasn't made a difference. It definitely worked on 10.1.4.

In that case, Neat will need to upgrade. I will email their support to see if they can help. I just used it on a H.264 file and it still good.

User error!

For some reason, my project had begun as a 23.98 project but using 29.97 footage, so I’m sure that was the issue.

Started a new 29.97 project and copied all footage and Neat worked.

Cool. Congrats

Interestingly, I had a similar issue with two clips in a project - the first clip the Neat Video Plug-in worked fine, the second clip it went to black...

I ended up changing out the shot.

Will keep an eye on it... I was Editing 25p footage.

Read this page: www.neatvideo.com/bugs.html

Neat tells me it's an Apple bug that effects footage that is not matching the timeline's framerate. Even if you use "automatic speed", the 2nd and following clips will always fail. You have to make a timeline in the matching framerate, or make a temporary project where you conform to the delivery frame rate, export that to ProRes, and import into your main project. Kind of a pain, but it'll work for now.

I have not yet seen the issue with 3rd party transitions on secondary timelines yet, but stacked 3rd party non-transitions on secondary timelines seem to work ok. The solution there is to make the secondary timeline a compound clip (what a pain...)

Neat Video says these bugs were introduced by Apple and they are aware and need to fix them.

Hi, this error happens when there are different frame rates, to fix just select the clip on the timeline and select open in timeline option, apply Neat Video NR on the file alone, should work properly.

Choose open in timeline and apply Neat Video NR on the file alone, should work properly.