Titler Pro 4: Look before you leap

Dave McCallister wrote on 6/19/2015, 10:26 AM
Fell for NewBlue's pitch again and bought TP4 Ultimate last night.

Immediate app crash with error message saying get a later video driver (this appears in the Vegas video window). Got absolute latest driver 353.06. No joy despite several reboots and a reinstallation of TP4. and latest Windows 7 updates.

What's worse, the installation hosed my Titler Pro 3 so now I have no NB titling at all.

Support ticket with APPCRASH data filed with New Blue. Don't expect a lot.

As always, New Blue refuses to put version numbers in their software, but the version I got was 4.0.15029.

Buyer beware.....

Dave McCallister

Comments

ECB wrote on 6/19/2015, 12:32 PM
@Dave, thanks for the heads up. Sorry for your problems. I was considering the TP4 update but no more.

Ed B
Dave McCallister wrote on 6/19/2015, 1:02 PM
Also know that Titler Pro 4 destroys an existing Titler Pro 3 installation if you have one. If you reinstall Pro 3, it will not run until Titler 4 is uninstalled. Great software engineering.

New Blue sent me a beta build which behaves just the same as the original version.
John_Cline wrote on 6/19/2015, 2:35 PM
I just haven't had very good luck with NewBlue products, they lost me a while ago and I just won't install any of their software anymore.
Kit wrote on 6/19/2015, 7:17 PM
They lost me when they reorganised their line-up which I felt penalised existing users - and the time limit on so-called upgrade credits was the last straw.
MikeyDH wrote on 6/19/2015, 9:35 PM
Yes their business model has a lot to be desired. I won't be adding anything anytime soon unless the nickel dime mentality changes. $249 for the ultimate upgrade. How much more can there be over TP3 for that kind of money?
LyricsGirl wrote on 6/19/2015, 10:49 PM
Titler Pro 4 Upgrade is out for a low cost price. I found a link to it on this site - yet nothing from NBFX. I have Win 7 pro latest updates... including all drivers. I have Vegas Pro 13 453 and Titler Pro 4 runs OK. If you have not heard back from NBFX after 3 working days email them. I have always had fast response.. in fact I upgraded Titler over a holiday weekend. Had probs with registering it and support were on it immediately. They got it fixed before Sunday tea time for me exchanging a few emails along the way.

The only complaint I have so far is that low priced upgrade. They were supposed to email existing proTitler users with the offer.

I have no affiliation with them.
If they want your custom they must give you support...so email them again and tell them your complaints.
John Lewis wrote on 6/20/2015, 2:23 AM
If ou have an acount with NB the upgrade offer is there for you, check it on their website
Enerjex wrote on 6/20/2015, 3:05 AM
Yes I upgraded a couple of weeks ago, the price then was $99 or $199 for elite. I've only spent about an hour using it so far in standalone and VP13 444/453 and haven't had a crash yet. I mainly bought it for the caching feature and it works great!
DGates wrote on 6/20/2015, 3:54 AM
The first adopters are always the last beta testers.
ushere wrote on 6/20/2015, 4:13 AM
+1 dg - nicely put ;-)
CJB wrote on 6/20/2015, 10:00 AM
I really did see anything that is earthshaking for this new release, and they want $99 for my total credits to update to basic TP4. I agree with the earlier post that NBFX has kind of blown it for their existing clientele. It's their business, but I haven't upgraded in a while and don't plan to.
jetdv wrote on 6/20/2015, 12:57 PM
Dave, if you are having issues, please contact NewBlue support. We will get you working.

If you open the Application Manager and log in, you will be shown the software packages installed as well as the version installed. The version number is easily accessible via the Application Manager.
jetdv wrote on 6/20/2015, 1:02 PM
Titler Pro 4 is a replacement for Titler Pro 3. It does not "destroy" it but it does replace it. We can certainly get Titler Pro 3 working again. There are some guidelines to follow, though. When upgrading, it is best if you:

1. Reboot
2. Uninstall Titler Pro 3
3. Install Titler Pro 4

If you are still having issues, please try this procedure:

1. Reboot (this is really an extremely important step)

2. Go to the following directories and delete anything related to Titler Pro:
c:\Program Files\NewBlue
c:\Program Files\NewBlueFX
c:\Program Files\Common Files\OFX\Plugins\NewBlue
c:\Program Files\Common Files\OFX\Plugins\NewBlueFX

3. Now install Titler Pro 4
Jumping Rascal wrote on 6/20/2015, 1:09 PM
When I experience a crash with Vegas Pro 13 (I have the Suite version), it is almost only after using TP3 within Vegas. TP3 will crash my Vegas maybe 2/5 times. TP1 used to crash a previous version of Vegas every time. Hitfilm effects by the way run fine on my system without crashing while working within Vegas. When I run TP3 as a standalone to create/save a title first for importing into Vegas later, I have no issues. I find that the other newblue items such as Video Essentials VI run with zero problems at all. Use of TP3 on occasion does provide some variety in a project and I like the lower thirds. However, given that an upgrade of the next version of Vegas Suite (Suite 13 to 14) with many software inclusions might not cost much more than the $99 newblue is asking for TP4 alone, I would certainly not buy TP4 separately. In a new version of Vegas Suite 14, at least one would expect that SCS would test all the included software to ensure that it all works as opposed to upgrading add ons such as TP4 piece by piece and finding out that there are incompatibilities.
Dave McCallister wrote on 6/20/2015, 7:56 PM
I realize the Application Manager tells me what version I have. The issue is what new version I would be installing before I install it, which would be easy if you would include the version number in the filename like everyone else does. For example: Vegas 13.0.453.

I guess NewBlue is adamantly opposed to telling their users what versions they are about to install. I cannot fathom a valid reason for this but would gladly accept enlightenment.
NormanPCN wrote on 6/20/2015, 8:49 PM
What I want is a changelog for all updates between my current version and the current version.

If my build version is 150123 and the update is 150200, then that is meaningless information to me.
Dave McCallister wrote on 6/20/2015, 8:57 PM
Per jetdv:

Titler Pro 4 is a replacement for Titler Pro 3. It does not "destroy" it but it does replace it. We can certainly get Titler Pro 3 working again. There are some guidelines to follow, though. When upgrading, it is best if you:

1. Reboot
2. Uninstall Titler Pro 3
3. Install Titler Pro 4

If you are still having issues, please try this procedure:

1. Reboot (this is really an extremely important step)

2. Go to the following directories and delete anything related to Titler Pro:
c:\Program Files\NewBlue
c:\Program Files\NewBlueFX
c:\Program Files\Common Files\OFX\Plugins\NewBlue
c:\Program Files\Common Files\OFX\Plugins\NewBlueFX

3. Now install Titler Pro 4


* * * *

Ed, I did all steps you suggested. No joy. If I uninstall Pro 4 and reinstall Pro 3, Pro 3 works fine as before. If I leave the dysfunctional Pro 4 there and reinstall 3, 3 fails until I uninstall 4.

Basically, your code does not play well with itself.

I am willing to try to make this work but I cannot see why it is a user's problem to do the file housekeeping a decent installer should do by itself.

The failure always centers on OFXBridge64.dll. Perhaps that's a good place to look?

Crash report follows:
Problem Event Name: APPCRASH
Application Name: TitlerStandalone.exe
Application Version: 0.0.0.0
Application Timestamp: 557e800d
Fault Module Name: OFXBridge64.dll
Fault Module Version: 3.0.2.19543
Fault Module Timestamp: 557e8026
Exception Code: c0000005
Exception Offset: 0000000000025bd8
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 287a
Additional Information 2: 287a0cb5ab18d792dd97b41f9f02a315
Additional Information 3: a726
Additional Information 4: a726fee3cfa05b85db97316b9dde5924

* * * *

Another observation: if Titler Pro 4 replaces Titler Pro 3, would it not be polite to mention this somewhere, anywhere? If version 3 needs to be nuked before 4 will work, could not your installer figure this out and tell the user what is about to happen?
John Lewis wrote on 6/21/2015, 2:21 AM
Try renaming the dll and try again. You can always add a n effect to a title inside Vegas anyway
set wrote on 6/21/2015, 11:17 AM
+1 John Lewis.
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
jetdv wrote on 6/21/2015, 2:07 PM
Jumping Rascal, if you could contact NewBlue with issues, that would be helpful. It would also be helpful to know what build of Titler Pro 1 and/or Titler Pro 3 is causing you an issue.

As for Titler Pro 4, there are many, many people running it without issue. I have seen a couple of reports where Titler Pro 4 did not start in Vegas and that is being researched. But NewBlue is certainly committed to making Titler Pro 4 work correctly on as wide a range of hardware/software possible.
jetdv wrote on 6/21/2015, 2:10 PM
Dave, please send all the information to support at newblueinc.com.

Typically, beta versions will be sent with version numbers in the file names. We have release builds with and without version numbers and both are used at various times.
Dave McCallister wrote on 6/21/2015, 4:58 PM
Ed:

I have an open ticket with you on this already. Caleb sent me a beta TP4 which has the same issue. He says he has other complaints on this and suspects a bug.

I just want to make sure NB is dealing with this before requesting a refund.

It is never sensible to omit version numbers, whether beta or release, unless your purpose is to confuse your users.
monoparadox wrote on 6/21/2015, 5:06 PM
"The first adopters are always the last beta testers."

So, in effect "introductory pricing" is payment for the frustration?

-- tom
Dave McCallister wrote on 6/21/2015, 5:42 PM
Just want to say that I installed TP4 Ultimate on a Microsoft Surface Pro 3 which had never had a previous Titler Pro install, and it works fine. The tablet is far too slow for serious editing, and I need TP4 to work on my six-core box.

This issue may be the installer's inability to deal with previous pieces of Titler Pro that conflict with TP4. My six-core has Titler Pro 1 which was bundled with an earlier Vegas, and Titler Pro 3 (which, oddly, is installed by NB in a folder called Titler Pro 2).