Can't open project with NB Titler Pro event

mark-woollard wrote on 11/16/2013, 10:43 AM
Yesterday, I added a NB Titler Pro 2 event to the end of a project in VP12 build 726. It's also the latest build of Titler Pro. It played fine, so I shut everything down.

Today I tried to open the project. It won't open. It hangs at the point where 6% of the project is loaded. How do I open the project to be able to delete the NB Titler Pro event? I'm assuming it's the offending item.

Comments

Kimberly wrote on 11/16/2013, 1:36 PM
When you added TP 2, did it take long to load and was the performance slow? I'm asking because TP 1 works flawlessly for me and TP 2 is so slow is it unusable. It takes a good 6+ minutes for TP 2 to launch and it's very sluggish after that. (I've worked with Edward at New Blue on it so this is NOT a rant against TP 2. For now I just use TP 1 and it meets my needs.)

Anyway, if TP 2 is the root cause, trying opening the project and letting it sit for a loooooooooooooog time. Maybe it will get past the stuck point and open, at which point you can remove TP 2 and see what happens. Or maybe it will crash and give an error message that names the culprit -- sometimes the crash report details show which plug-in is causing the problems.

If you have any incremental saves or back-up files you might be able to get those opened. If you do get the project open, be sure to do incremental saves with every major change. Project1, Project2, and so on. That way you can roll back if anything goes astray.

You may have tried all this but I wanted to mention it just in case there are some new ideas.

Good luck. It sucks when a project won't open.
Kimberly wrote on 11/16/2013, 1:44 PM
One more idea!

Create a new Vegas project and add an instance of TP 2. Save, close, and try to reopen. It if opens, that is a sign that TP 2 is not the problem.

If you have a number of other FX in the project you could repeat this with each FX. That will be tedious but it may narrow the scope to identify your problem. Once you know the root cause, other Forum users may have some ideas for you.
mark-woollard wrote on 11/16/2013, 3:01 PM
Thanks for the suggestions Kimberly. Sure enough, TP2 added to a new project crashed Vegas.

I tried waiting longer for the corrupt project to open--about an hour. It was still hung on 6%.

TP2 is unusable.
NormanPCN wrote on 11/16/2013, 3:19 PM
>TP2 is unusable.

I guess I am lucky. I've only used it a couple of times, but no problems so far.
AMD GPU setup for me.
Chaotica wrote on 11/16/2013, 3:45 PM
I have been using Titler Pro 2 quite extensively over this past summer & have had very few problems with it. Those which I did run into were either solved by reporting to NB support which helped their developers to implement a fix or performing a clean install of TP2 & my graphics drivers. I have run into the problem of TP2 crashing or halting upon startup & either taking VP12 with it or bringing the loading of a project file to a complete stop. Looking through the TP2 log indicated that it was failing at initializing the GPU capabilities which led back to conflicting video driver files which somehow had not been cleaned out during a driver upgrade.
System Info: AMD FX-8150, RADEON 7970, 8GB RAM
NormanPCN wrote on 11/16/2013, 5:06 PM
Looking through the TP2 log

Where does NB cache their video driver info. I don't see any NewBlue folder in the AppData structure. Registry maybe?
Kimberly wrote on 11/16/2013, 5:38 PM
@pathlight:

I've found that a lot of my stuff works better if I have GPU off in Vegas, but in the Nvidia Control Panel the high performance Nvidia processor is on for Vegas. My unit is a laptop with the GeForce 640M card and the 327.23 driver. I can't explain why TP 1 works great and TP 2 does not. Must be something really different under the hood from 1 to 2.

Regards,

Kimberly
Chaotica wrote on 11/16/2013, 5:50 PM
It doesn't make a log file explicitly available. There are 3 items in the TP2 program folder( turnOnLogs.reg, ReportUtility.exe, turnOffLogs.reg) which are used for generating a log(if you're comfortable doing so on your own or as directed by NB support). Use the first registry modification to turn TP2 logging on, run TP2 to generate some fresh data, use the ReportUtility to get a log txt file, then turn off logging again with the last one.

What can be handy is having a log report of when your system(and TP2) is running fine - that way if you run into an issue & generate another log report at that time you have something to compare it against.
jetdv wrote on 11/18/2013, 9:22 AM
Actually TP2 is very usable on the vast majority of machines. Pathlight, if you are having an issue, please do contact NewBlue support. We are working on some Titler issues right now. I have a beta build you could test and the developers may wish to connect to your machine to see why your machine is failing.
mark-woollard wrote on 11/18/2013, 11:47 AM
Edward, thanks for your offer. I will follow up in a couple of days once I finish a project I'm working on.

Meanwhile, uninstalling TP 1 and 2 allowed me to open the project and continue working.
mark-woollard wrote on 11/19/2013, 2:41 PM
Edward, thanks for the link. NBTP 2 build 131115 seems to have solved the problem.
jetdv wrote on 11/20/2013, 10:41 AM
That sounds great. As 131115 is a beta version, we're working on cleaning up a couple of more things and will release a new build soon.
Derm wrote on 11/20/2013, 1:00 PM
Can I get that link, cant see it on the NB site.
Updated to latest Vegas 12 add Titler 2 , program freeze. Getting to be a regular occurrence
jetdv wrote on 11/21/2013, 10:44 AM
Send an e-mail to support at newblueinc dot com and we'll make sure you get the link. As it's truly a beta version, I want to wait until the official release before posting a link on the forum.