Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums DaVinci Resolve anyone tried neat openfx with resolve 10

  • Dmitry Kitsov

    September 16, 2013 at 9:30 pm

    Tried, does not work, at least yet: no UI for the plugin, returns an error.

  • Jake Blackstone

    September 16, 2013 at 11:42 pm

    Why?
    Native Temporal NR in V10 is based on the same principal as Neat Video and you should get very similar results.

  • Robert Ruffo

    September 16, 2013 at 11:58 pm

    Jake, Neat Video is different in that it allows you to define an area of what is solid/uniform (or what would be, if not for noise) using a square that you drag out. If find results from Neat Video are a bit better, maybe for that reason.

  • Jake Blackstone

    September 17, 2013 at 1:09 am

    You can also define area for the native temporal NR by HSL qualifiers or by the windows.

  • Dmitry Kitsov

    September 17, 2013 at 1:48 am

    @jake blackstone:
    1. Native temporal is actually not at all similar to the neatvideo. It is instead similar to Re:vision Effects De:noise, and just as the latter suffers from optical flow artifacts. Neat Video does not have too many visible motion artifacts and also allows for different treatment of different noise frequencies. Additionally you may have it analyze 10 frames other than the current frame, while native temporal will do 4 frames it seems.
    2. Robert was not talking about qualification of filter effect, he was talking about the ability to analyze noise level in different frequency bands.

  • Jake Blackstone

    September 17, 2013 at 3:53 am

    The temporal NR reduction principal is the same in every piece of software. It’s just the way to identify what is noise and what is not. Obviously, being able to analyze 4 frames spread vs 10 frames is a quality disadvantage. Said that, BMD had to make a determination between speed and quality. If they did allow 10 frames analysis, Resolve would be unable to do it in real time. Neat Video doesn’t work in real time without the render and for color grading is a no go. Until BMD fixes Resolve’s cache, Neat Video or not, you’re stuck with just the native temporal NR for real time playback.

  • Andi Winter

    September 17, 2013 at 8:35 am

    thanks for the info 🙁

    i didn’t try the new resolve nr, but neat is the best
    nr i ever worked with. with a little tweaking, i get
    stunning results with it!

    i didn’t hope to work in RT with it, but to judge the
    result in resolve and then use render cache or simply
    do a first pass NR on all the material in a seperate
    directory and relink it afterwards. all within resolve, which
    would be a huge timesaver!

    dmitry, did you write neat about it? are they working on the
    issue?

  • Dmitry Kitsov

    September 17, 2013 at 8:55 am

    Yeah. The developers are aware.

  • Bill Ravens

    September 17, 2013 at 2:48 pm

    NeatVideo is the defacto standard for noise reduction software. I’ve spoken with the developers at NV. The issue appears to be bugs in the beta version of Resolve 10. As soon as these are resolved(no pun intended) NV will be up and running in Davinci.

  • Jake Blackstone

    September 17, 2013 at 6:26 pm

    I hate to burst everyone’s bubble, but the idea of using OFX in Resolve right now in it’s present iteration is half baked and not ready for prime time. Throwing a single plugin like Bleach bypass brings Resolve to a crawl. With three GPUs I’m getting only 18 fps. And that plug in is not really that resource hungry, like Neat Video. So, if you’re OK with VERY SLOW playback, when you want to use Neat Video, then fine. But, I repeat, until BMD decides to implement persistent background caching correctly, OFX is just a gimmick and nothing more.

Page 1 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy