Comments

Dexcon wrote on 5/19/2021, 3:29 AM

Unless you need NBTP3 for use in other programs, the best way to get rid of it is to uninstall it from your computer via 'Apps and Features'.

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 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 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 5/19/2021, 4:48 AM

A large wooden Stake and a 100lb Mallet!

jetdv wrote on 5/19/2021, 9:32 AM

How does it keep locking up Vegas Pro 18? If you don't use it, it shouldn't do anything. If you do use it, how are you using it?

Please do note that Titler Pro 3 is extremely old and the current version is now 7.

Titler Pro 3 may have been installed as Titler Pro 3 in the product list if you purchased it. If you have an older bundle, it could have been installed as part of the Vegas Pro 14 bundle. If it was part of the bundle, it will watermark in Vegas Pro 18.

Gordon-Doughty wrote on 5/20/2021, 10:05 PM

Thanks for the suggestions, but I can't find NBTP3 in my program list. It only shows up in Vegas. NBTP6 is in my program list and I can use it as a stand alone, but it doesn't show up in Vegas. When I try to delete NBTP3 from the plug-in list, delete is not highlighted so I can't remove it there. I'm thinking NBTP3 may have been brought in from an old .veg file that I imported from an earlier version of Vegas. Any ideas?

Dexcon wrote on 5/21/2021, 6:12 AM

@Gordon-Doughty  ... I don't think that the .veg file has introduced TP3 as, typically, the link to NBTP will auto direct itself to the latest version of TP. More likely is that there are remnants of TP3 remaining in some of NewBlue's folders on the C drive. Just over 4 years with Vegas Pro 14, I had an NBTP problem and received the following advice from NB support:

When installing or uninstalling our products, it is always vital that you first reboot. If Vegas has been started and closed, it is quite possible for it to remain in memory and keep some of our files locked preventing a proper installation. I would also recommend uninstalling any previous version you have installed before installing the newest build. You can also do a clean install:

1. Reboot

2. Uninstall any versions installed

3. in C:\Program Files\NewBlueFX, delete the Titler folder

4. in C:\Program Files\NewBlue, delete the Titler Pro 2.0 for Windows folder

5. in C:\Program Files\Common Files\OFX\Plugins\NewBlue, delete TitlerPro.ofx.bundle

6. in C:\Program Files\Common Files\OFX\Plugins\NewBlueFX, delete TitlerPro2.ofx.bundle

7. Now reinstall the appropriate version listed above

If, after reinstalling, you get an error using Titler pro, try going to C:\Program Files\NewBlueFX\Common and remove the OFXBridgeB64.dll file.

If Vegas is not seeing the proper version of Titler Pro, start Vegas Pro 14 while holding down the CTRL-SHIFT keys, and check the “Clear cache” box in the window that opens.

You might want to check through the various folders on your computer to see if you can see any TP3 remnants in those folders.

Alternatively, lodge a support ticket with NewBlueFX as there could well be an updated approach to resolving the issue specific to your situation. The good news is that NBFX respond very quickly and helpfully to support requests.

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 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 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

jetdv wrote on 5/21/2021, 8:49 AM

@Gordon-Doughty, that's why I said this: If you have an older bundle, it could have been installed as part of the Vegas Pro 14 bundle. If it was part of the bundle, it will watermark in Vegas Pro 18.

If you're still having issues with Titler Pro, you can always go to NewBlue support by e-mailing support at newblueinc.com