Neat Video & Neat Image community

Greetings community,

NeatVideo OFX 5.4.0 appears to not respect clip speed/retming settings in Resolve v17.1.

Temporal filtering introduces incorrect frames in shots that have been slowed down, sped up, or reversed at 100%. Of course this could be a bug on Resolve's side and how it supplies adjacent retimed frames...

I've tried altering, with no change:

- Noise profile generic vs. custom.
- Temporal NR quality, radius.
- Render settings (CPU vs. GPU vs. both).
- Node and clip-level caching.
- New project vs. existing project.

Disabling temporal NR fixes the issue.

Anything else you can recommend, or a bug fix?

Thanks!
Stephen

PS > I've seen the Resolve known issues, but the clips showing problems are not standard, not nested/compound, and are progressive @ 24 fps.

PPS > System details: Mac Pro 5,1 / AMD RX580 / MacOS Catalina 10.15.7 / Resolve 17.1 build 24 / NeatVideo 5.4.0

Please create a minimum test project with (ideally) just one short clip and one effect (Neat Video) applied to it besides any necessary time adjustments. Please verify that the problem is reproducible in the test project and then send the test project with the source clip to us (support at neatvideo.com) for analysis. Once we reproduce the problem on our machines, we can identify the root cause of the issue and possibly find a solution or workaround.

Thank you,
Vlad

Hi Vlad,

Thanks for the quick reply. Sure, here is a .dra, zipped on Frame.io.

More comments:

- I've also investigated different kinds of source media: the problem exists with both long-GOP and intra-frame.
- Error present in 24 and 25 fps source/project.
- I've re-checked project-wide scaling and retiming settings, no change to the error.
- Lastly, one interesting thing I noticed: when node/output caching is disabled, the paused/frame-advance preview is correct. But when playing back, the error is present.

Thanks,
Stephen

Hi Stephen,

Thank you for preparing a test project. I hope it includes the clip as well.

Could you please upload it to www.wetransfer.com (which doesn't require registering unlike frame.io)?

Thank you,
Vlad

Sure. Yes, the media is included.

This is a public Frame.io link; any details may be filled into the download page, they are not vetted at all. But here it is uploaded to Wetransfer.

Thank you very much. We could reproduce the problem and it is more or less clear where it comes from but it is not yet clear how to avoid that in the best possible way. We will try to discuss that with the developers of the host application to see what could be done.

Vlad

Hi again,

Ok, thanks.

One solution: as was suggested on BMD's forum, rendering a video 'mixdown', baking in the speed effects solves this problem by hiding the retiming from Neat Video. Resolve 17's new render in place feature is probably the easiest way to deploy this. Requires intermediate files which is pretty inelegant, but this will work in a pinch...

Stephen

Yes, it is a common workaround in such situations.

Vlad

Hi again,

Resolve 17.1.1 came out today, doesn't appear to fix this problem.
Any update from your side?

Thanks,
Stephen

Unfortunately we haven't received a reply from Resolve regarding our bug report yet.
It is likely that they haven't considered it yet.

Vlad

NVTeam wrote: ↑Wed Mar 31, 2021 4:52 pm Unfortunately we haven't received a reply from Resolve regarding our bug report yet.
It is likely that they haven't considered it yet.

The current version of Resolve is now 17.4.2, and still this problem persists. Vlad, did you ever get a response from BND at all about this bug?

Thanks.

--
Oyvind

Yes, but it was not quite substantial, unfortunately. I am going to try again.

Vlad

NVTeam wrote: ↑Thu Dec 09, 2021 11:04 pm Yes, but it was not quite substantial, unfortunately. I am going to try again.

Thanks, I appreciate it.

Right now the only workaround I have is just exporting the clip without re-timing, apply the NR and then re-import the clip. It works, but It's a lot more work.

--
Oyvind

The "Render in Place" function may be another option. See in known issues.

Vlad

I'm having the same (similar) issue in Resolve 17.4.5 and NV 5.5.1 Pro on OSX.

I got sent a project with a lot of footage shot in 50 FPS and the editor placed that in a 25 FPS timeline.
For the most part there are no fancy speedramps/reverse playback or any of that – just plain 50 FPS clips in a 25 FPS timeline.
I assume that counts as "retiming" too?

Whenever I apply NeatVideo with the Temporal Filter enabled things go haywire.

Rendering hundreds of shots in place is not an option – it's just too time consuming.
This problem makes NV pretty much unusable for me (at least on this project - don't get me wrong, I love NV )

Is there any other way? A fix on the horizon?

Cheers!