Comments

Dexcon wrote on 9/6/2019, 8:23 AM

There seems to be some plugin differences between VP16 and VP17 - have a look through the forum over the last month for posts/comments on the plugins issues in VP17.

However, it is without question that you need version 4.1 of Ignite to get access to Ignite in VP17, and most probably you will need BCC12 (12.5.2) to get access to BCC in VP12. NewBlueFX plugins shouldn't be a problem as I've got all of my NBFX plugins accessible in VP17, even legacy plugins.

eightbit wrote on 9/6/2019, 8:33 AM

When I installed the plugins, they appeared in VP 16 because it was already installed. I've installed VP17 after installing the plugins, so how do tell it to load them? I have the impression that it doesn't know they are on my computer.

Thanks.

Dexcon wrote on 9/6/2019, 8:41 AM

@eightbit ... please read my comment a little bit more closely. Simply, Ignite and BCC will not load in VP17 UNLESS you have the latest versions of those products. Yes, older versions of Ignite and BCC will load into VP16, but only the latest versions will load into VP17. Unlike audio VST plugins in many programs including Vegas Pro, there is no Options/Preferences video plugin option to direct VP to load video plugins from a particular folder.

Also, have a look at the Ignite forum on FXhome's webpage - you'll find the same result there re VP17 and Ignite.

eightbit wrote on 9/6/2019, 2:54 PM

@Dexcon. I updated my BCC plugins, which required a new install, and they now showup in VP17. I didn't realize that VP only has the capability to specify directories for audio plugins.

Do you know if VP 17 automatically detects the OFX plugins when it is installed?

Thanks for your help!

Dexcon wrote on 9/6/2019, 6:32 PM

Do you know if VP 17 automatically detects the OFX plugins when it is installed?

In general, yes, VP auto detects OFX plugins on install. However, there have been occasions, mostly many years and VP versions ago, when it sometimes didn't work and the solution was just to re-install the plugins from the already existing exe files. From memory, it mainly related to NewBlueFX plugins, but I also vaguely recall having to do it with BCC once or twice. Again from memory, I can't recall this being a problem with VP15, 16 or 17.

eightbit wrote on 9/7/2019, 5:17 AM

Thanks again @Dexcon

AVsupport wrote on 9/8/2019, 7:32 AM

would be interesting to know what the requirements are for an OFX plugin to work with VP.

 

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.