NB Titler not working with Vegas 21?

Martin L wrote on 8/22/2023, 8:07 AM

I have had trouble with NewBlue Titler Pro 6 for the last months and couldn't get it to work at all with Vegas Pro 20. It crashes almost immediately everytime. Tried erasing the NB Titler posts in the registry according to NB support instructions several times. I even tried Titler Pro 7 and Total effects which also has Titler. Same problem. Now with Vegas Pro 21 the problem is still there just the same.

New Blue responds "it seems to be related to a known bug that some Vegas users are experiencing". They are workin at it but so far no success apparantly. Almost a year have passed.

Now, has anyone of you any suggestion to how to get it to work? Any superthorough registry clean method to use that I haven't done so far?

Or is it time to leave New Blue behind and get something else to create graphic Titles with animations and effects like NB Titler? What application would you recommend?

Thanks

Martin L

Comments

Jack S wrote on 8/22/2023, 8:16 AM

@Martin L I used to use Titler Pro 5 through to 7 but got very disillusioned by the issues with it. I acquired BorisFX's Title Studio and haven't looked back. It's powerful, with great 3D capabilities. The only thing it lacks is the multi-title capabilities of TP7. If you can afford it, I highly recommend it. No problem with integration with VP21 either. It's a fairly steep learning curve, but I have created a number of tutorials on it on my YouTube Channel. Just search for Veteran Video Editor.

My system
Genshin Infinity Gaming PC
Motherboard Gigabyte H610M H: m-ATX w/, USB 3.2, 1 x M.2
Power Supply Corsair RM750X
Intel Core i7-13700K - 16-Core [8P @ 3.4GHz-5.4GHz / 8E @ 2.50GHz-4.20GHz]
30MB Cache + UHD Graphics, Ultimate OC Compatible
Case Fan 4 x CyberPowerPC Hyperloop 120mm ARGB & PWM Fan Kit
CPU Fan CyberPowerPC Master Liquid LITE 360 ARGB AIO Liquid Cooler, Ultimate OC Compatible
Memory 32GB (2 x 16GB) DDR5/5200MHz Corsair Vengeance RGB
MSI GeForce RTX 4060 Ti 8GB - Ray Tracing Technology, DX12, VR Ready, HDMI, DP
System drive 1TB WD Black SN770 M.2 NVMe PCIe SSD - 5150MB/s Read & 4900MB/s Write
Storage 2 x 2TB Seagate BarraCuda SATA-III 6.0Gb/s 7200RPM
Windows 11 Home (x64)
Monitors
Generic Monitor (PHL 222V8) connected to GeForce RTX 4060 Ti
Generic Monitor (SAMSUNG) connected to iGPU

Camcorder
SONY Handycam HDR-XR550VE

Dexcon wrote on 8/22/2023, 8:37 AM

I've generally not had any problems with getting NBFX TP7 to work in either VP20 or 21, but with a recent problem with TP7 'jetdv' suggested removing a couple of files from Vegas Pro's C drive - which worked. I copied that advice but annoyingly cannot find it right now - so "help" @jetdv.

Also, please note that the latest version of TP7 recently released is version 7.8.230213 (which it seems took some 5 months to be released).

Last changed by Dexcon on 8/22/2023, 8:38 AM, changed a total of 1 times.

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 8/22/2023, 12:28 PM

@Dexcon, I'm sure that was advice to "clear the cache" in VEGAS. There's a couple ways to do that:

1. Reset VEGAS and check the "Clear cache" box on the window that opens

2. Delete the two cache files "plugin_manager_cache.bin" and "svfx_plugin_cache.bin" from: C:\Users\{user name}\AppData\Local\VEGAS Pro\{Version #} and then restart VEGAS which will rebuild those two files.

Dexcon wrote on 8/22/2023, 5:47 PM

@jetdv  ... yes that's it. Thank you. I've put that in a Word doc and saved it to OneDrive so I should find it again if I need to.

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

Martin L wrote on 8/23/2023, 2:11 AM

@Martin L I used to use Titler Pro 5 through to 7 but got very disillusioned by the issues with it. I acquired BorisFX's Title Studio and haven't looked back. It's powerful, with great 3D capabilities. The only thing it lacks is the multi-title capabilities of TP7. If you can afford it, I highly recommend it. No problem with integration with VP21 either. It's a fairly steep learning curve, but I have created a number of tutorials on it on my YouTube Channel. Just search for Veteran Video Editor.

Thanks. I will try that if the problem can't be solved using the tips from the others here.

Martin L wrote on 8/23/2023, 2:12 AM

@Dexcon, I'm sure that was advice to "clear the cache" in VEGAS. There's a couple ways to do that:

1. Reset VEGAS and check the "Clear cache" box on the window that opens

2. Delete the two cache files "plugin_manager_cache.bin" and "svfx_plugin_cache.bin" from: C:\Users\{user name}\AppData\Local\VEGAS Pro\{Version #} and then restart VEGAS which will rebuild those two files.

Interesting, thanks. Just, how do you "reset Vegas"?

Edit: Googled and found how to do it.

Dexcon wrote on 8/23/2023, 2:15 AM

Just, how do you "reset Vegas"?

It's item 14 in https://www.vegascreativesoftware.info/us/forum/vegas-pro-faqs-and-troubleshooting-guides--104787/

https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

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

Martin L wrote on 8/23/2023, 2:38 AM

Just, how do you "reset Vegas"?

It's item 14 in https://www.vegascreativesoftware.info/us/forum/vegas-pro-faqs-and-troubleshooting-guides--104787/

https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

Yes, I found the same post through Google. So I've done the reset now and have also deleted the two cache files jetdv wrote. Time to restart Vegas - and Titler. :)

Martin L wrote on 8/23/2023, 3:33 AM

It didn't help. The problem persists. I now deleted Total FX and Vegas Pro 20 and the remaining registry post of Vegas 17 which I unistalled a year ago. I'll go through all steps again and try.

Martin L wrote on 8/23/2023, 8:22 AM

https://www.vegascreativesoftware.info/us/forum/vegas-pro-17-update-1-build-321-general-discussion--117239/?page=9#ca733557

 

Maybe, just maybe... :)

Hmm..I don't see how that touches my problem with NewBlue Titler...

jetdv wrote on 8/23/2023, 8:35 AM

@Martin L, I'd recommend a clean install of Titler Pro and then clear the cache in VEGAS as well.

  1. Reboot your computer
  2. Uninstall all versions of Titler currently on your system
  3. Go to C:\Program Files\NewBlueFX and make sure Titler is removed
  4. Go to C:\Program Files\NewBlue and make sure the folder NewBlue Titler Pro 2.0 for Windows is removed
  5. Go to C:\Program Files\Common Files\OFX\Plugins\NewBlue and make sure the folder TitlerPro.ofx.bundle is removed
  6. Go to C:\Program Files\Common Files\OFX\Plugins\NewBlueFX and make sure the folder TitlerPro2.ofx.bundle is removed
  7. Re-install Titler Pro
Martin L wrote on 8/23/2023, 8:39 AM

Yes, I have done those steps now. Just waiting for NB to give me a renewed trial of Titler 7. I own Titler Pro 6 but I guess that is old and I don't dare to try it again. I'll report the results here whenever it's done.

Adis-a wrote on 8/23/2023, 8:52 AM

https://www.vegascreativesoftware.info/us/forum/vegas-pro-17-update-1-build-321-general-discussion--117239/?page=9#ca733557

 

Maybe, just maybe... :)

Hmm..I don't see how that touches my problem with NewBlue Titler...

Well, it wasn't directly related to my problem either, I solved it quite by accident - solving something completely different. It's worth a try, I think. :)

paul-marshall wrote on 8/24/2023, 5:33 AM

 I used to use Titler Pro 5 through to 7 but got very disillusioned by the issues with it.

Jack S - if you are disillusioned it must be bad! Me too - I'm still using NB Titler Pro 7 and I'm hating it. But I'm only still using it thanks to your tutorials or I would have given up ages ago.

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

Julius_ wrote on 8/24/2023, 9:32 AM

I am running TotalFx 360 7.8.230402 with Vegas 21..I use the titlerPro...It's a bit slow but hasn't crashed (but I dont use it much). In V20 it crashed all the time and I had to use it as a standalone.

Mind you, I just updated my Nvidia drivers so maybe I have a bit more stability.

Martin L wrote on 8/24/2023, 1:53 PM

https://www.vegascreativesoftware.info/us/forum/vegas-pro-17-update-1-build-321-general-discussion--117239/?page=9#ca733557

 

Maybe, just maybe... :)

Hmm..I don't see how that touches my problem with NewBlue Titler...

Well, it wasn't directly related to my problem either, I solved it quite by accident - solving something completely different. It's worth a try, I think. :)

Hey, about this post you referred to: "VP 17 + Red Giant (Magic Bullet Suite 13.0.11 or Universe 3.0.2) plugin causes VP to crush when trying to import RED's R3Ds.

Deleting FFCache_x64_1033 file, found in C - users - name - appdata - local - vegaspro - 17.0, before VP start, solves the problem til the next VP start.

Uninstalling Red Giant ehm "solves" it completely.

Can someone repro this?

OpenCL.dll files, usually found in C-Windows-System32, were missing. Copied them from FileRepository folder to Sys32. Worked like a charm."

I don't quite understand exactly what it was that you did, or what you suggest I could try to do. Do you mean deleting the FFCache_x64_1033 file?

Martin L wrote on 8/24/2023, 1:55 PM

I am running TotalFx 360 7.8.230402 with Vegas 21..I use the titlerPro...It's a bit slow but hasn't crashed (but I dont use it much). In V20 it crashed all the time and I had to use it as a standalone.

Mind you, I just updated my Nvidia drivers so maybe I have a bit more stability.

I'll try that too. Still no responce from NB this time.

Adis-a wrote on 8/24/2023, 4:06 PM

https://www.vegascreativesoftware.info/us/forum/vegas-pro-17-update-1-build-321-general-discussion--117239/?page=9#ca733557

 

Maybe, just maybe... :)

Hmm..I don't see how that touches my problem with NewBlue Titler...

Well, it wasn't directly related to my problem either, I solved it quite by accident - solving something completely different. It's worth a try, I think. :)

Hey, about this post you referred to: "VP 17 + Red Giant (Magic Bullet Suite 13.0.11 or Universe 3.0.2) plugin causes VP to crush when trying to import RED's R3Ds.

Deleting FFCache_x64_1033 file, found in C - users - name - appdata - local - vegaspro - 17.0, before VP start, solves the problem til the next VP start.

Uninstalling Red Giant ehm "solves" it completely.

Can someone repro this?

OpenCL.dll files, usually found in C-Windows-System32, were missing. Copied them from FileRepository folder to Sys32. Worked like a charm."

I don't quite understand exactly what it was that you did, or what you suggest I could try to do. Do you mean deleting the FFCache_x64_1033 file?

@Martin L

No, just check if OpenCL.dll files are where they are supposed to be - in C=>Windows=>System32.

Mine were missing, so I copied them from FileRepository folder to C=>Windows=>System32. Crashing stooped then and I was able to use RG Magic Bullet Suite with R3Ds inside VP without a problem.

Maybe, and this is just a wild guess, it will help stop crashing VP with your NewBlue Titler Pro 6. That's all. :)

Jack S wrote on 8/24/2023, 4:48 PM

@paul-marshall Thank you.

My system
Genshin Infinity Gaming PC
Motherboard Gigabyte H610M H: m-ATX w/, USB 3.2, 1 x M.2
Power Supply Corsair RM750X
Intel Core i7-13700K - 16-Core [8P @ 3.4GHz-5.4GHz / 8E @ 2.50GHz-4.20GHz]
30MB Cache + UHD Graphics, Ultimate OC Compatible
Case Fan 4 x CyberPowerPC Hyperloop 120mm ARGB & PWM Fan Kit
CPU Fan CyberPowerPC Master Liquid LITE 360 ARGB AIO Liquid Cooler, Ultimate OC Compatible
Memory 32GB (2 x 16GB) DDR5/5200MHz Corsair Vengeance RGB
MSI GeForce RTX 4060 Ti 8GB - Ray Tracing Technology, DX12, VR Ready, HDMI, DP
System drive 1TB WD Black SN770 M.2 NVMe PCIe SSD - 5150MB/s Read & 4900MB/s Write
Storage 2 x 2TB Seagate BarraCuda SATA-III 6.0Gb/s 7200RPM
Windows 11 Home (x64)
Monitors
Generic Monitor (PHL 222V8) connected to GeForce RTX 4060 Ti
Generic Monitor (SAMSUNG) connected to iGPU

Camcorder
SONY Handycam HDR-XR550VE

Martin L wrote on 8/25/2023, 5:02 AM

Hi again! I tried most things now and I've given up on NewBlue Titler. I move on and get something else. But thanks for all your tips anyways.

Reyfox wrote on 8/25/2023, 6:20 AM

What did you move on to?

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Adis-a wrote on 8/25/2023, 6:39 AM

@Martin L

Sorry to hear that.

Martin L wrote on 8/25/2023, 7:41 AM

What did you move on to?

I'll start with Boris Title Studio. I have a license but never used it. Let's see if I can learn it.