Comments

Nizar-AbuZayyad wrote on 11/9/2024, 6:09 PM

the project im working on wont open at all, whenever i start it , it gives this error and shuts down

Steve_Rhoden wrote on 11/9/2024, 10:37 PM

Part of your issue is deriving from the Newblue line of Plugins you have installed. You were advised in another post about them, but you still have it on your system.... So i will suggest uninstall and remove every single Newblue plugins and its folders from your computer, empty your recycle bin, and restart your system. Then see if you notice any difference.

Nizar-AbuZayyad wrote on 11/10/2024, 3:48 AM

@Steve_Rhoden It was exhausting to track down and delete all the NewBlue files, including hidden ones scattered everywhere. It took me about an hour to finally remove everything. I feel like Vegas is running faster and performing better without the NBFX plugins. I think they're not compatible with Vegas and cause too many issues and crashes.. I will keep monitoring things though.

Dexcon wrote on 11/10/2024, 3:55 AM

Unless you've already done this, consider running a registry cleaner such as the free CCleaner (the registry cleaner is listed under the Tools menu) which should remove any remnants of uninstalled programs from the registry.

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

Nizar-AbuZayyad wrote on 11/10/2024, 4:06 AM

@Dexcon Thank you, i will download the CCleaner now and check things up.

3POINT wrote on 11/10/2024, 4:43 AM

the project im working on wont open at all, whenever i start it , it gives this error and shuts down

Probably because you removed the NBFX plugins (and used them before in your project) you get this error message. If new projects open without issues, than forget this project. I also recommend to disable in preferences this setting, to avoid that Vegas hangs during startup when trying to open a corrupt project.

jetdv wrote on 11/10/2024, 7:55 AM

It was exhausting to track down and delete all the NewBlue files, including hidden ones scattered everywhere. It took me about an hour to finally remove everything. I feel like Vegas is running faster and performing better without the NBFX plugins. I think they're not compatible with Vegas and cause too many issues and crashes.. I will keep monitoring things though.

First of all, NewBlue plugins wouldn't be "scattered everywhere". To remove all NewBlue plugins from VEGAS, it's best to uninstall but you can just go to:

c:\Program Files\Common Files\OFX\Plugins and simply remove the "NewBlueFX" folder (and/or "NewBlue" folder)

Then, when restarting VEGAS, make sure you clear the cache!

Yes, NewBlue plugins are compatible with VEGAS. I have TotalFX installed (which is every effect, every transition, and Titler Pro) and VEGAS is working fine!

Nizar-AbuZayyad wrote on 11/10/2024, 12:08 PM

@jetdv I found them scattered everywhere because I still had folders from previous Vegas versions (18, 19, 20, and 21) that I hadn’t deleted. They were spread across different folders in Vegas, so I had to remove them manually. Although they were compatible, they caused frequent crashes, especially with "Titler Pro." Just clicking on it in Vegas effects made the software lag and go into "Not responding" mode.

jetdv wrote on 11/10/2024, 1:19 PM

@Nizar-AbuZayyad, VEGAS Pro 18, 19, 20, and 21 may have been over various folders but the NewBlue plugins should be where I stated (with base files also placed in c:\Program Files\NewBlueFX.) If you remove the files from c:\Program Files\Common Files\OFX\Plugins then VEGAS won't see the plugins - period - for current OFX plugins.

Now, if you had really old DirectX plugins installed, that could be a different story.

I'm sure the "compatibility" issues you are referring to would have been caused by Titler Pro and not the other effects/transitions. However, even with Titler Pro, the vast majority of people are using it with minor to no issues. If you have issues with Titler Pro, please do contact NewBlue support so those issues can also be found and fixed. Many times, it's just a video driver issue. Sometimes, other things can happen.

Nizar-AbuZayyad wrote on 11/10/2024, 2:49 PM

@jetdv Yes, it’s definitely the 'Titler Pro.' The other transitions I tried and used never caused any issues. I’ll try doing a clean install of the NB plugins sometime and will exclude Titler Pro if possible. Thanks for your insights and advice! Someone mentioned before that you’re the NBFX expert in the forum :D