VP17 takes 1:30 to create the video plug-in factory

james-ollick wrote on 9/22/2019, 6:31 PM

When starting VP17, running as administrator as I always do, the part where the VEGAS window says creating video plug-in factory consistently takes 1 minute and 30 seconds. Is there something I can do or change to speed this up? The rest of the startup is very fast once it gets past this point.

 

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 7900 XTX 24GB graphics card, Corsair 1000 watt power supply. Windows 11.

VP 21 BCC 2024 Boris FX Continuum Complete, Titler Pro v7. Various NewBlue effects.

Comments

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

@james-ollick … given your computer specs (from your signature), this does seem really slow. In my case with a 5 years old computer (it was good at the time), VP16 and 17 get through the video plug-in factory process quite quickly, the exception being if a new install of plug-ins had just been made. And I've not only got latest builds of BCC, Mocha Pro and Ignite Pro, but as well recent and legacy NewBlue FX amongst a few others.

What happens if you open VP17 from it's icon or exe file rather than as an administrator? Is that quicker?

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2024.5, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

Grazie wrote on 9/23/2019, 7:38 AM

@james-ollick - less than 2 seconds? How many FXs do you have? Anyway, a short Project opened fully in 15 seconds.

Grazie wrote on 9/23/2019, 7:44 AM

@james-ollick - Actually, tried again it was instantaneous, couldn't flag it. The whole, now larger project opened fully in 34 seconds.

james-ollick wrote on 9/23/2019, 8:50 AM

I have tried as administrator and just the standard click on the icon with the same results. I have BCC 2019 complete, NewBlue Titler Pro 7 and some of their other plug-ins, Ignite, SeMW auto levels, Visioncolor LUT plugin, two Sapphire units, and the free Hitfilm Fx. VP16 takes 30 seconds to get through the creating video plug-in factory process since I installed VP17. I just installed the latest VP17 build 321 update and it still takes 1:30 to load the video plug-in factory.. VP must be looking for something it cannot find and timing out at 90 seconds and moving on with the startup. It flies through the rest and loads my project quickly.

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 7900 XTX 24GB graphics card, Corsair 1000 watt power supply. Windows 11.

VP 21 BCC 2024 Boris FX Continuum Complete, Titler Pro v7. Various NewBlue effects.

Dexcon wrote on 9/23/2019, 9:01 AM

@james-ollick … just to check … do you have the very latest builds of BCC, Ignite (4.1) etc? Interestingly, I didn't think that FXHome's Ignite Express (free) worked in VP17 - if that's what you mean by HitFilm Fx.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2024.5, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

james-ollick wrote on 9/23/2019, 11:08 AM

@Dexcon I do have the latest build of BCC, Sapphire and Ignite Pro. I have not reinstalled HitFilm Express.

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 7900 XTX 24GB graphics card, Corsair 1000 watt power supply. Windows 11.

VP 21 BCC 2024 Boris FX Continuum Complete, Titler Pro v7. Various NewBlue effects.

james-ollick wrote on 9/24/2019, 7:54 AM

@Magix any suggestions?

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 7900 XTX 24GB graphics card, Corsair 1000 watt power supply. Windows 11.

VP 21 BCC 2024 Boris FX Continuum Complete, Titler Pro v7. Various NewBlue effects.

Former user wrote on 9/24/2019, 9:36 AM

@james-ollick Maybe the quickest way to find out would be to completely uninstall all of them, then reinstall them one by one.

If theres a single culprit it should show up, and you never know, after reinstalling, the problem might go away if it was some form of corrupt installation initially.

james-ollick wrote on 9/24/2019, 9:55 AM

@JN_ Thanks, I had tried that and the issues remains.

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 7900 XTX 24GB graphics card, Corsair 1000 watt power supply. Windows 11.

VP 21 BCC 2024 Boris FX Continuum Complete, Titler Pro v7. Various NewBlue effects.

Former user wrote on 9/24/2019, 11:33 AM

@james-ollick Sorry to hear that, I think that was my best shot🤔.

NickHope wrote on 9/24/2019, 12:47 PM

@JN_ Thanks, I had tried that and the issues remains.

But didn't the process show you which plugin(s) is causing the big delay? You might just be able to rename those plugins' folders, rather than uninstalling them, as per part 2 of the "Vegas won't start" FAQ post.

(or do you mean that the long delay remains, even with all plugins disabled?)

james-ollick wrote on 9/24/2019, 1:07 PM

@Nick Hope, The blue window that displays during startup just displays "creating video plug-in factory" during the long delay, then goes through the remaining processes very fast. VP always runs once it gets done with this. I do not see anywhere what individual plug-ins are loading. I wish it did, that would help narrow down the cause. I used Windows 10 to remove the plug-ins, re-started the PC and ran VP-17 a couple of times and the delay was still there with just the native plug-ins. I have since re-installed the plug-ins.

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 7900 XTX 24GB graphics card, Corsair 1000 watt power supply. Windows 11.

VP 21 BCC 2024 Boris FX Continuum Complete, Titler Pro v7. Various NewBlue effects.

NickHope wrote on 9/25/2019, 2:32 AM

There's something amiss. The "creating video plug-in factory" stage is taking about 3 secs here, and I have quite a few 3rd party plugins.

Beyond just removing the plug-ins using the Windows interface, I suggest you actually inspect the following folders after doing that, in case you overlooked something or something got left behind.

  • C:\Program Files\Common Files\OFX
  • C:\Program Files\VEGAS\VEGAS Pro 17.0\OFX Video Plug-Ins
  • C:\ProgramData\VEGAS Pro\Application Extensions
  • ...Documents\Vegas Application Extensions
  • C:\Program Files (x86)\Vstplugins
  • C:\Program Files\Vstplugins
  • C:\Program Files (x86)\Steinberg\Vstplugins
  • C:\Program Files\Steinberg\VstPlugins

Temporarily move any 3rd-party-related folders that remain and look like they might cause a delay. The VST audio plugins probably aren't the cause, but you never know. It's easy to disable them. You could also try some more of the suggestions in that post I linked to in my last comment, in particular a clean uninstall/reinstall, including cleaning your registry.

If that doesn't work then I suggest you report it to Support.

james-ollick wrote on 9/26/2019, 8:47 AM

@Nick Hope Thank you. I believe this has worked. It was the NewBlueFx folder in C:\Program Files\Common Files\OFX that was causing the problem. Now VP17 opens in 10 to 12 seconds. 🙂

Last changed by james-ollick on 3/30/2020, 9:37 AM, changed a total of 1 times.

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 7900 XTX 24GB graphics card, Corsair 1000 watt power supply. Windows 11.

VP 21 BCC 2024 Boris FX Continuum Complete, Titler Pro v7. Various NewBlue effects.

max-krasnov wrote on 10/2/2019, 2:22 PM

I am also tormented by this problem. It was off of the plug-in, I deleted it, VP 7 started to run and did not stop at "create the video plug-in factory". Having solved one problem, another appeared. I can’t use this plugin, for example, working with a chromakey. What to do?

ritsmer wrote on 3/30/2020, 4:52 AM

A couple of days after installing new plug-ins my Vegas Pro 16 and Pro 17 started to crash at start-up while "Creating video plug-in factory".

Both V16 and V17 always have used about a minute for this - at the first start after a PC reboot - but now they crashed persistently.

Reading NickHopes post above I got an idea to try something else: I opened the folder C:\Program Files\Common Files\OFX\Plugins - sorted by ascending Date modified - and then moved (not copied) the 2 newest plug-ins out of this folder to another folder on the Desktop.

After this both V16 and V17 started without crashing.

Then I moved the 2 plug-ins back into the folder - and still V16 and V17 start without crashing - and they now even build the video Plug-in factory in 1-2 seconds where they used about a full minute before.

Then I rebooted the PC to check if the improvement stayed - and it did.

PS: The 2 first plugins were the new version 4.1 IgnitePro and IgniteCore bundles - but I doubt that the problem had something to to with Ignite - it was rather something with the "Plugins" folder itself . Actually I have been able to start and use V16 and V17 several times after installing the Ignite plug-ins - until they both out-of-nowhere just started to crash.

michael-harrison wrote on 3/30/2020, 9:02 AM

If this starts happening again, try deleting the contents of the C:\Users\<your name>\AppData\Local\VEGAS Pro\17.0 folder and restarting.

The first startup *will* be slow but the ones after that should be speedy

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

ritsmer wrote on 3/31/2020, 2:14 AM

That might also be a good idea - doing so here, however, just makes V17 "Stop working" while creating video video plug-in factory. Tried to start it 3 times.

Fortunately I could put back my copy of that folder - and now V17 starts very quickly again.

ritsmer wrote on 4/1/2020, 8:46 AM

Wanted to reset Vegas 17 - entered TRUE in Internals restore all settings - and now Vegas 17 crashes at every start attempt while creating video plug-in factory. Think we have something fishy here...

ritsmer wrote on 4/1/2020, 8:53 AM

... again removed the 2 newest plug-ins (as described above) and now V17 starts without crashing.

Then put back the 2 plug-ins - and still V17 starts without crashing.

I think this is something that our Vegas programming gurus should check.