Newblue FX updating procedure

diverG wrote on 8/16/2014, 10:01 AM
NB FAQ list is no longer accessible; hence the question.
Is there a published procedure to be used when updating NBFX plugins?
I ask because in my experience simply closing the NLE and other open application and then applying the update results in the need to re-activate the plug in. It would appear that it is best to de-activate the plug in prior to updating.
This is contrary to applying an update to Vegas, but then again there is no way to de-activate Vegas.

To be fair NB are pretty good when it comes to resetting the activation counter.

Geoff

Sys 1 Gig Z-890-UD, i9 285K @ 3.7 Ghz 64gb ram, 250gb SSD system, Plus 2x2Tb m2,  GTX 4060 ti, BMIP4k video out. Vegas 19 & V22(250), Edius 8.3WG and DVResolve 20.2 Studio. Win 11 Pro. Latest graphic drivers.

Sys 2 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP19, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

Comments

NormanPCN wrote on 8/16/2014, 6:48 PM
I have always just updated over the top of an existing install. I have had a problem only once, and that was with the most recent installs and then only with one of my many NB plug-ins.

The most recent, 140723, changelog did say there were updates to the activation system, and that may have caused my problem. NewBlue email support cleaned that up in a couple of hours.
Spectralis wrote on 8/17/2014, 10:49 AM
I really don't know why NB can't create an updater like Red Giant and Adobe use so that everything stays up to date. I have a lot of different NB products (about 10) and find it incredibly difficult to keep track of the latest versions. Keeping up to date is one of the worst aspects of their products.
NormanPCN wrote on 8/17/2014, 2:59 PM
Same here. I have quite a few. You have to check, update and install each one individually. Very tedious.

I have found this page easier to check and download versions. Of course, you need to know your current version.

I prefer to manually update. Case in point. The new versions of the effects have broken some compatibility on my setup. The previous build was reliable. I am not sure NB is going to be able to do anything about this.
jetdv wrote on 8/19/2014, 12:49 PM
I recommend this procedure:

1. Reboot
2. Install the new build

If you are moving to a different machine, you definitely want to deactivate on the old machine and then activate on the new machine. There is no need to deactivate when simply installing an update.