Multiple Neat Video nodes killing performance

[DannyYoon]

@mattriley

…ke and see this kind of performance issue if you use multiple neat nodes in a script?I’ve seen a couple of topics with a similar issue but one was mentioning color shift issues with multiple neat nodes in a batch. I’m not seeing any problems with the output, it’s just extremely slow when the one Neat node depends on the results of another Neat node.-MattLinux, Flame 2022.1, 128 GB RAM, M6000 (12 GB)

Neat video defaults to 32bit float not 16bit float. What bit depth are your write nodes? If its 32bit then that would explain why everything is slow.

[andymilkis]

@mattriley

Does there exist a python script that would allow for rendering a write file node and then importing the rendered frames when it is done? I gotta think some clever person around here has made a script like that already. AE has a feature like this and it can be nice in certain situations.

I don’t remember if this is an option with Python and 2022. I remember writing/modifying a python script to do this, but it was deprecated when the feature was added to the write file node a couple of versions ago.

That being said, take a look in the Logik Portal. If there’s a re-import script that works with that version it will be in the Portal!

[Antonknee]

If you have old kit, I suggest getting Neat 6, but if not, adding a colour management node or changing the render node to 16bit before you export will save on file sizes. Obviously you need fast hard drives for when you use the neat file, otherwise its not worth the exporting, and will still be a bit slow, once the shot is done delete the Neat clip, and save the set-up!