Titler Pro 4: Look before you leap

Comments

ECB wrote on 6/22/2015, 6:39 AM
Dave,

When I upgraded from Titler Pro 2 to Titler Pro 3 the NB installer installed TP3 in the Titler Pro 2 folder.

ed
Dave McCallister wrote on 6/22/2015, 6:40 PM
MANY THANKS TO SET!!!!

He said:

Your system have a conflict on OpenFX feature ability inside Titler Pro 4.
Rename or move it out temporarily, and problem should go away.
The cons is your Titler Pro cannot use OpenFX.

Dave, what OpenFX collections are installed in your system?

Set


Now here is a man who has a very functional mind. My hat is off to you, sir!

One at a time I removed and then restored each OFX bundle and then tried to start TP4U. Boris Continuum Complete is the culprit that causes TP4U to die a horrible death when OFXBridge64.dll attempts to make friends with it.

I will leave the BCC stuff in another folder until/unless I need it.

I hope no future OFX plugs cause this issue. Thanks to all who helped me through this.

Dave McCallister

Tech Diver wrote on 6/22/2015, 7:31 PM
Interesting that you would want to take such an action. I would think that you would want to use BCC *much* more often than the titler.

Peter
Dave McCallister wrote on 6/22/2015, 8:01 PM
Peter:

Of course I would. I am hoping that NewBlue can resolve this so that I can put BCC back. My objective was to see if Titler Pro 4 worked at all. I can shuffle the OFX plugs in and out until NewBlue has a brainstorm. Which I hope is soon.
Dave McCallister wrote on 6/23/2015, 9:18 AM
It's all sorted out.

Upgraded BCC to latest version which does not kill TP4.

Thanks for the assistance to all who helped.

Dave McCallister
set wrote on 6/23/2015, 5:48 PM
Glad can help and nice to hear finally can work.

Btw,
I will leave the BCC stuff in another folder until/unless I need it.
How you do this? Did you just move the plugins in 'C:\Program Files\Common Files\OFX\Plugins' out there and in ?

I have another OFX related issue and this happened in DaVinci Resolve Lite.
When I run DaVinci, it freezes and need to be force-closed. Next time I run it, I was notified the OpenFX feature have to be disabled. Searching in DaVinci forums, the only way to find out which OFX is the problem, I have to remove OFX, and test each FX one by one.
If moving plugins in and out method can work instead of doing install and uninstall, I will try it soon.

Set

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

Dave McCallister wrote on 6/23/2015, 8:52 PM
Set:

I created another folder under Program Files/Common/OFX and moved the bundles to there from the Plugins folder which is also under OFX.

I took them all out except the Titler Pro bundle. I then tried opening the Titler standalone - which worked fine. I closed Titler, moved each OFX bundle back to Plugins one at a time and tried the standalone again. That's how i pinned down the issue to Boris BCC 7. Apparently both the standalone and the hosted version of Titler interrogate the OFX Plugins folder when started.

I updated to BCC 9 today which presents no conflict for Titler so all is well.

Thanks again for your wisdom!

jetdv wrote on 6/27/2015, 11:51 AM
Dave, so glad to hear that everything is now working. Unfortunately, sometimes conflicts with other software arises. Once discovered, the conflicts can be resolved.
Grazie wrote on 7/29/2015, 1:50 AM
Same here . . Started new thread.

g


Len Kaufman wrote on 7/31/2015, 10:21 PM
OK...I bit...after trying a trial version. I deleted TP3 and installed TP4 in SVP 13. It worked, BUT when I go to generate media, the text that shows up says Titler Pro3. But when you click and open, it is actually TP4. I guess I can live with that.
John Lewis wrote on 8/1/2015, 1:30 AM
That may only apply to trial version
Len Kaufman wrote on 8/1/2015, 2:24 PM
Nope. Uninstalled the trial and installed the paid version. Same result.

jetdv wrote on 8/1/2015, 2:41 PM
Len, that's a caching issue in Vegas. Do this to fix it:

Clear Vegas Cache - delete plugin_manager_cache.bin and svfx_plugin_cache.bin from:
c:\Users\{user name}\AppData\Local\Sony\VegasPro\{version#}
Grazie wrote on 2/3/2016, 7:19 AM
Tried all the remedies 'cept delete plugin manager cache:

delete plugin_manager_cache.bin and svfx_plugin_cache.bin from:
c:\Users\{user name}\AppData\Local\Sony\VegasPro\{version#}


G