Command line access/API access

suggest a way to improve Neat Video
Post Reply
tk421storm
Posts: 1
Joined: Wed Feb 19, 2020 5:39 pm

Command line access/API access

Post by tk421storm »

We're looking at streamlining our usage of Reduce Noise in our studio - we think the "automatic" button gives passable results in almost all occasions, so we wanted to automate a process that would provide an "Automatic" output without user intervention.

However I haven't found a command line/api function to deal with doing basic degrains headlessly. We realize that there are a lot of options which require a users' intervention; however in our business case sometimes volume is more important than accuracy.
NVTeam
Posts: 2745
Joined: Thu Sep 01, 2005 4:12 pm
Contact:

Re: Command line access/API access

Post by NVTeam »

There is no command line interface or API in the current versions of Neat Video, so doing that is not really possible yet.

We will consider adding more tools to enable automatic processing in the future versions.

Thank you,
Vlad
dirkjanmi
Posts: 3
Joined: Fri May 13, 2022 9:04 am

Re: Command line access/API access

Post by dirkjanmi »

Hello everyone,

is this feature something that has been implemented in more recent versions?
We also want to streamline our Denoise automization and be able to run an auto-profile on the OFX plugin without the user having to enter the GUI - just something that we can trigger from outside via Python.
Ideally we would get some sort of signal back if the auto-profiling succeeded or failed (e.g. when the detected sample area was too small).
Would this be possible to implement for the "auto-profile current frame" as well as "auto-profile noisiest frame"?
Best,

Dirk Jansen-Michels
NVTeam
Posts: 2745
Joined: Thu Sep 01, 2005 4:12 pm
Contact:

Re: Command line access/API access

Post by NVTeam »

This has not been implemented yet. This idea is in the wish list for future versions.

Thank you.
dirkjanmi
Posts: 3
Joined: Fri May 13, 2022 9:04 am

Re: Command line access/API access

Post by dirkjanmi »

Is it easier to implement to just have another button available for the OFX plugin like "quick auto-profile" with which we don't have to enter the GUI? This would already help a lot.
NVTeam
Posts: 2745
Joined: Thu Sep 01, 2005 4:12 pm
Contact:

Re: Command line access/API access

Post by NVTeam »

It may be easier in terms of implementation but this general idea is a complicated architectural question that requires more systematic approach.
muaqat
Posts: 2
Joined: Mon Jan 23, 2023 11:00 pm

Re: Command line access/API access

Post by muaqat »

Hello,

We are interested in using the command line to speed up our pipeline, do you have any idea when such an option will be implemented?

Thank you
NVTeam
Posts: 2745
Joined: Thu Sep 01, 2005 4:12 pm
Contact:

Re: Command line access/API access

Post by NVTeam »

Unfortunately no, we do not currently have it in the development plans.
You may want to explore using the command line interface to start the host application that will in turn use the plug-in. That is directly possible with AE and Nuke as far as I know. Other host applications may offer a command line version as well.
muaqat
Posts: 2
Joined: Mon Jan 23, 2023 11:00 pm

Re: Command line access/API access

Post by muaqat »

By using the CLI of Nuke it'll still need to interact with the ui of neat for building the profil ?
NVTeam
Posts: 2745
Joined: Thu Sep 01, 2005 4:12 pm
Contact:

Re: Command line access/API access

Post by NVTeam »

Yes, you would need to create a project/composition and set up all filters in GUI first, and only then you would be able to render the project using the CLI of Nuke.
dirkjanmi
Posts: 3
Joined: Fri May 13, 2022 9:04 am

Re: Command line access/API access

Post by dirkjanmi »

Hello,
any chance this topic has been put on the agenda?
We are working a fully automated Denoise workflow and would really need a way to trigger the auto profile via API.
NVTeam
Posts: 2745
Joined: Thu Sep 01, 2005 4:12 pm
Contact:

Re: Command line access/API access

Post by NVTeam »

This idea is already in the wish list and it will be considered for implementation in one of the future versions.
Post Reply