No. In Vegas 17, there were some internal changes made that broke compatibility with some plugins that required the dev to update the plugin for them to work correctly. Neat video actually put this update out a while back (they sent it to me a couple weeks sooner when I mentioned my Radeon 7 wasn't working at all with NV4, giving me NV5 free in the process, how nice of them!), but all other versions of NV work in all other versions of Vegas. The change made under the hood does break compatibility with Vegas 17 when using older versions of NV. Magix was proactive and reached out to all devs of VP plugins before releasing 17 to inform them of this change so they could get their plugins up to speed, but some took longer to respond/release updates than others. As such, Magix can't be blamed for this incompatibility, they did what they should have to make sure the change transitioned smoothly.

However, if you buy NV5, it will work just fine in all versions of VP. The incompatibility only affects older versions being used on VP17, at least until the NV devs update those older versions (chances are they'll just direct folks to NV5).

or they could stick to STANDARDS like everyone else has done for the last decade or more :D :D

All STANDARDS have to be occasionally updated. Their OFX standard still... stands. All OFX plugins still work, but the OFX standard doesn't "standardize" everything, there's still things that can be done in the app (that may be necessary for updating said app's features) that would require updates from plugin developers. I know you're in the midst of a temper tantrum right now about Vegas, but you can't pretend that other NLEs never have to make changes that require updates to their plugins, case in point below, where a Resolve user was suffering from the EXACT SAME kind of issue, supposedly standardized plugins requiring a new version to work right.

or they could stick to STANDARDS like everyone else has done for the last decade or more :D :D

Yes, this continues to baffle me. From what I understand Neat Video is a Video noise reduction tool. From what I gathered the standard plugin API for video plugins is OFX. Yet instead of making an OFX version plugin, Neat Video is going down the path of individual NLE support instead?

Being an audio guy, I find this perplexing trying to draw an analogy. There are certainly different audio noise reduction plugins but I an unaware of any of them which have chosen to go down a path of supporting individual DAWs. Instead they chose to support the standard plugin APIs be it VST, DX, AAX, TDM, RTAS with the most widely adopted by the majority of plugins and DAWs is currently VST.

What am I missing other than video software developers seem to be insistent on going down a path of non standard least compatibility?

All STANDARDS have to be occasionally updated. Their OFX standard still... stands. All OFX plugins still work, but the OFX standard doesn't "standardize" everything, there's still things that can be done in the app (that may be necessary for updating said app's features) that would require updates from plugin developers. I know you're in the midst of a temper tantrum right now about Vegas, but you can't pretend that other NLEs never have to make changes that require updates to their plugins, case in point below, where a Resolve user was suffering from the EXACT SAME kind of issue, supposedly standardized plugins requiring a new version to work right.

They seemed to have figured out the standardization's on the audio side. There's essentially 3 pieces to the puzzle.

1. The API specification (In the video case OFX)

2. The Plugin (ie Neat Video)

3. The Host (Vegas Pro)

If the plugin vendors want to introduce new features not currently supported by the API, they make their proposals to the API developer, thus the reason there are multiple versions of the VST plugin specification. If there's a problem with a particular plugin not working properly in a particular host, then the Host developers and Plugin developers 1st ensure they're each functioning according to the defined API and then work together in resolving the issue.

I don't think anyone's saying that they don't expect problems but creating a plugin which is specific to an particular host and even worse a particular version of that host, just seems like a tool I rather avoid.

It just seems to me that if the Plugin developers and host developers are continuing to work around the standard OFX API, then that tells me the owner of the OFX API are likely not living up to their end of their piece of the puzzle.

I visited the Neat Video website. I see they have an OFX host supported version. What would be the reasons to go with the version supported specifically for Vegas over going with the OFX version which should also be supported in Vegas?

I visited the Neat Video website. .... What would be the reasons to go with the version supported specifically for Vegas over going with the OFX version which should also be supported in Vegas?

@Rednroll - I hadn’t realised that before now. Good question RnR!

I visited the Neat Video website. .... What would be the reasons to go with the version supported specifically for Vegas over going with the OFX version which should also be supported in Vegas?

@Rednroll - I hadn’t realised that before now. Good question RnR!

 

Another thing I'm uncertain about is that since they have the multiple versions, OFX, Vegas, AE, etc, if you purchase Neat Video v5.1.4 do you only get one of those versions or all? Since it seems they have separate installer downloads for each of those, I'm currently assuming you are only purchasing the one and that's the reason I had asked if there are any differences between the Vegas and OFX version. My thought was that if the OFX version could be used in multiple hosts as long as the host supports OFX, then that would seem to be the better version to get since it would be more versatile.

My experience with audio plugins has been that they have a single installer and during the installation process you select the multiple versions you would like to get installed on your system at the time of installation but that doesn't seem to be the case with the Neat Video plugin.

One difference I just noticed looking at their feature comparisons. The OFX Pro version is $250. The Vegas specific Pro version is $130 as well as they offer a Home Vegas specific version which is $75 and the difference between the Pro and Home version seems to be Pro supports 4K+ video and home supports up to 1080p. So you're having to pay almost double if you want the flexibility of the OFX version.

There's also no specific mention of Vegas being a supported host of the OFX version.

Listed OFX Supported Host applications

Foundry Nuke 11 / 10 / 9 / 8 / 7 / 6 / 5.1+
(commercial version only)

Blackmagic Fusion Studio 16 / 9 / 8 / 7.7+

Eyeon Fusion 7 / 6 / 5.3+

Assimilate Scratch 9 / 8 / 7 / 6.1+

FXHOME HitFilm Pro
12 / 11 / 10 / 9 / 8 / 7 / 6 / 2017 / 4

SGO Mistika Boutique 8.8+

SGO Mistika 8.2+ / Mamba 2

Quantel Rio 4 / Pablo Rio 2.1.4+

Natron 2.0.5+

HS-ART DIAMANT-Film Restoration & DustBuster+
11 / 10 / 9 / 8 / 7 / 6 / 5 / 4.5+

IDT Vision Motion Studio 2.12+

Note: only 64-bit versions of host applications are supported.

I'm unsure if they could make this plugin any more confusing and with such a steep incremental price increase in regards to which one to purchase if they tried.

OFX Vegas is not supported, otherwise it would be on the list.

Pricing:

I don't see any confusion about the pricing.

There is no OFX for Vegas.

If you need to clean higher than full HD, get the Pro version, otherwise get the Home version.

Want to try it? Download the trial version.

This is the best there is for Video Noise Cleaning. Nothing else comes even close, in most circumstances.

That answers both questions, neat video was never OFX, therefore never standardized. Why the OFX version doesn't work with OFX compatible Vegas is a good question, perhaps they get better performance by avoiding that route.

OFX Vegas is not supported, otherwise it would be on the list.

Pricing:

"Note: only 64-bit versions of host applications are supported."

Is Vegas not a 64-bit OFX host application?

I believe if Vegas is a 64bit OFX host application, then it is therefore on the list as being supported..

Pricing:

I don't see any confusion about the pricing.

I never said I was confused about the pricing. The pricing is clear, it's ridiculously silly pricing buts its clear. I said I was confused whether to get the OFX or the Vegas specific version for Vegas. The OFX Pro version costs twice as much as the Vegas Pro versions for the same features which is what makes the pricing ridiculously silly but definitely no "confusion".

That answers both questions, neat video was never OFX, therefore never standardized. Why the OFX version doesn't work with OFX compatible Vegas is a good question, perhaps they get better performance by avoiding that route.

I looked back, v4.1.1 of Neat Video Pro also had an OFX version. I don't think its been determined if the OFX version works or doesn't work with Vegas. However, once I seen their pricing structure it no longer matters to me if it works with Vegas or not, it's too expensive, where if their business model is to charge separately for an OFX version and a Vegas specific supported version of the same plugin, then I no longer want anything to do with that business model since it misses the entire point of the intent of a plugin.

I have a multitude of audio plugins. The same plugin works in Vegas, Acid, Sound Forge, Ableton Live, Cubase and Reaper for me. I've never had to purchase an audio plugin which was made specifically for each host application, so I've decided I'm not going to start now for a single video application plugin with a ridiculous business model and pricing structure.

Ok, I installed the demos of the OFX and then the Vegas version. It looks like the OFX version does not show up in Vegas. The Vegas version shows up under the Third Party plugin folder and the OFX plugin folder within Vegas...go figure.

Another interesting thing during installation of the Vegas version, here is the default install folder location.

C:\\Program files\Neat Video v5 for Sony Vegas

That was fun, and that helped make up my mind in deciding to get it or not. That answer would be no, I've experienced too many times where you purchase a plugin, you decide to update to the next version of the host and that plugin no longer works. If the OFX version worked at least there would be some additional certainty hope that it would work in a future version release of Vegas.

My experience with using NeatVideo in Vegas is very positive.

Results are excellent. User interface is good. Support is perfect. Bugs are quite rare (based on feedback in their forum) and they are fixing them very fast. HW support is very good (multi core CPU, AMD/NVIDIA GPUs). Prices are very good when I'm comparing with other plugins.

As for supporting different host applications:

- NeatVideo v4 plugin first released in 2015 is supporting VP17

- NeatVideo v3 plugin first released in 2011 is supporting VP17

- v3, v4 and v5 work in VP13 & VP15 (I pretty sure everything will be OK in earlier versions).

I'm using v5 it is faster/better.

 

- v3, v4 and v5 work in VP13 & VP15 (I pretty sure everything will be OK in earlier versions).

I'm using v5 it is faster/better.

 

My recent experience has been v4 and v5 OFX of Neat Video does not work in VP16. So is it only odd versions of Vegas it works in?

I do not think so. I just do not have VP16, VP14 and a bit lazy to install VP12 I have to check.

It is possible that you have to update NeatVideo as old versions know nothing about newer host so they updating plugin and adding support of new hosts. For example, I have had NeatVideo v4.8.5 installed and it was not visible in VP17. When I installed v4.8.7 it appeared in VP17 with no issue (it is also possible that it was not there as I installed VP17 after plugin).

I'm talking about Vegas plugin, not about OFX version of NeatVideo.

 

I'm talking about Vegas plugin, not about OFX version of NeatVideo.

Thanks, I guess I'm confused then since you mentioned that v3, and v4 of Neat Video works in Vegas. I'm new to trying out Neat Video, was there a v3 and v4 that was made just for Vegas because I was under the assumption that v5.1.4 that Grazie brought to our attention was the 1st version of Neat Video that was developed to work with Vegas. Therefore I was assuming those v3 and v4 you mentioned as working would have been the OFX version.

I've been using neat video with Vegas for years... I think 3 was the version I came in on? Maybe 4. I've had it no less than 4-5 years.

Nah. I'm using NV for Vegas (not OFX) very long time.

Grazie only let us know that the newer version was just released.

Technically speaking the mentioned v5.1 is the first version that officially supports VP 17 and this was mentioned in the provided changelog.

Nah. I'm using NV for Vegas (not OFX) very long time.

Grazie only let us know that the newer version was just released.

Technically speaking the mentioned v5.1 is the first version that officially supports VP 17 and this was mentioned in the provided changelog.

Sorry but I have to keep asking questions, because this just seems so confusing to me. When I looked at the NV product pages I see a NV for AE, Premiere, Final Cut, OFX, VirtualDub, etc, etc. So when you say you've been using prior versions of NV with Vegas, I'm confused by that and am wondering which NV were you using, and was it showing up as a plugin within Vegas?

So I'm scratching my head and wondering did you purchase the AE or other version of NV and it miraculously showed up in Vegas as a plugin? Maybe you can better understand my previous questions, because it would seem that if you purchased an OFX version, then it would seem to make more logical sense if it showed up within Vegas as a plugin but as you indicated that is not the case.

I bought NV for Sony Vegas. Then it became NV for Magix Vegas. I know nothing about NV OFX.