The "Pro Type Titler" is Sony's titler. The other titler is "NewBlue Titler Pro". Then there's also the new "Sony Titles and Text" titler. So from reading this it's a little confusing as to which titler was actually being used.

I will say that most people are having no issues with NewBlue Titler Pro. For those that are, NewBlue is trying hard to figure out why and eliminate the issues. It is very CPU intensive so a compatible video card/driver is definitely required.

You and Duncan hit on the same problems I'm having. See my post to BruceUSA. There's serious work that needs to be done with this program's software interface with V11. One workaround I found (MAY work...) is to go to another title that I've already built in NBT Pro and copy it to the place where I want a new title.

Super frustrating on this, 'cuz NBT is a really neat program on the surface. I have built a bunch of chapter titles with this pgm so I'm stuck to try to make it work. (Come ON Sony/NB - let's get this right!!!)

Best of luck.

Has a proper solution been found for the New BLUE FX TITLER? Windows crashes whenever I attempt to use it.

My crashes are on-going also, but only during copy/paste/open of a NB title.
Yours sound a lost worse. Hoping for a resolution but its only going to get fixed if people submit support tickets. I have, and hope everyone else does too.

Paul.

Same situation here. About 50% of the time NBT works ok, then on the flip side it will suddenly start crashing Vegas whenever I change a setting or color. I have sent in numerous crash reports over the last 3 mo. Hope someone is working on it. Because I really like what NBT does in theory. Still terribly jaggy on small text edges though.

Also noticed (the hard way) that after a Vegas crash, sometimes the Ripple Edit button will get pushed. Last week it caused me 2 extra hours work fixing all the damage to the timeline event "ripples" that it caused. Be very careful to check this button after a crash!

Latest version of the NB Titler and latest Vegas 64, crashes every time.

NB Titler is a completely useless bit of software. Causes Vegas to freeze every time, so I've removed all traces of it from my system.

NB Titler is a completely useless bit of software.
I used to feel this way. I'm still only at about 60% confidence... with hope.
As I tried using it on various projects, frustration set in and I've nearly abandoned it.

Fix these things I've already mentioned in other threads and I may look at it as a contender:

Title/Action Safe Areas
- How else are we gonna know if we won't get cut off?
especially if we're animating text & other elements.

Alignment Tools
- Align relative to safe areas
- Align Center, Top, Bottom, etc relative to selected media
currently you have to keep going back and forth to Position X, Y, Z and copying

Replace Asset
- Applying a new image as a Texture does not maintain correct Aspect Ratio if they are different.

GUI
- Ability to view the timeline's current frame in NBTP
- Ability to rename Layers or inherit names from files.
instead of renaming under the Style tab, why not be able to rename layers on the timeline where they are more visible?
- Remember my Last Used Folder
Why must it always open the 'limited' NewBlue Textures folder?
- Library > Get More...
Waste of space & misleading if there's nothing more to get that will be recognized by NBTP

Stand Alone
- Double-click to open a saved .nbtitle in NBTP
I have to open NBTP then go File > Open

NBTP
- Stability
Various/Random/Consistent Crashes to NBTP & Vegas 11 (64).
- Speed the dang thang up!
After Effects, Boris RED, Blufftitler, ProAnimator, BCC Extruded Text... all seem to run quicker/smoother.
Creative ideas are gone by the time NBTP catches up to your thoughts & actions.
- Having to restart Premiere to update the length of the title is ridiculous.
can't remember if some of the other things I mentioned pertain to other NLE's

Website
- Let us know when to expect a v3 of plugins with NBTP recognition.

Jaggy text but, at least on my system, it doesn't crash Vegas every single time (I distinctly remember one time where it didn't).

Got the latest NBTP 120208 update and it seems worst than the previous update.

It occasionnally crashes, sometimes it is predictable while other times unpredictable. Smooth interpolation doesn't seem that smooth or at least not smooth enough for my taste if it even works. Aliasing hasn't been improved, yet they call it a pro app.

Keyframes behavior is weird compared to previous versions, I just can't get things to move like I previously did. Sometimes the keyframes won't copy or I cannot add a second or third keyframe. I need to restart Vegas in order to try an add keyframes....

3D control is not always accessible on-screen as you move your text, it should have been placed beside the NBTP preview window to show up has a switch.

As much as I like the NBTP, it just going to sit there since I am far from using it on corporate work and tired of submittng tickets for support while I do understand they are trying hard to fix the bugs.

Have been using it with Vegas 521 and today tried the new NVIDIA driver 295.73 hoping for a miracle but saw no improvement...

Rob

Updated New Blue Titier and it crashed the 1st time I went to use it. Tried it again and it crashed later making adjustments. Went back to using pro type and it works well for my needs.

I will say that most people are having no issues with NewBlue Titler Pro....
That's not entirely true jetdv.

Steve, then those people need to start a help ticket at NewBlue. I know how many support issues come in and when you compare that to the number of Titler Pro copies being used, it is an extremely small percentage.

"...then those people need to start a help ticket at NewBlue.I really don't like to "pile on", but I guess I'm going to do it anyway. It's really difficult to submit a help ticket when the crashes are unpredictable & not reproducible.

I've found that I have fewer crashes and safer results if I do my NB Titling in a separate project, render to a DNxHD intermediate, then import the intermediate to my main project. (just putting the veg on the timeline results in more crashes).

Every time I get a crash, I hit the "send report" button. Where do those reports go anyway?

...Jerry

Those reports would go to Sony.

I filed a support ticket today. NBT consistently crashes Vegas 11 (521) on two workstations running Windows 7...one desktop, one laptop. Seriously frustrating. Has there been any realistic fixes or diagnostics as to what is causing the crashes?

Yesterday I had a horrible experience with NBTP while today it is much better...

Did get one crash when copy pasted a NBTP event..... but this time the keyframes where working the way they should while yesterday it was a total mess.

And I did restart my computer yesterday after installing the newly released NVIDIA driver before I went on with NBTP just to play it safe.

So I am just confused and at the same time amazed everytime I experiment with NBTP with the creativeness it offers in making titles, that being what brings me back to it....and hopefully soon, using it in corporate work.


Edward, is it possible to have a logged version of NBTP.

Would that make easier to report crashes?

Thanks,

Rob

Latest Vegas 64 on Win 7, latest NBTP and the new NVIDIA update.
One audio track, one video track, nothing else. I invoke NBTP and puff, the Sony report screen. I dont believe there are a small amount of people experiencing this and, as has been said above, what else to report?
I might also say that while I believe New Blue are good people, I am not a beta tester and dont want to spend my work time making reports and checking settings especially as I am having problems with another unrelated program that I use a lot. I dont want to fight a war on two fronts when I could actually be doing what I bought the programs to do.

Steve, then those people need to start a help ticket at NewBlue.

- NewBlue Site needs a better roadmap or GPS.
(I've stopped going there as it was not very easy to find what I was looking for when there)
* It WAS easy to find the 'Buy Now' buttons though

I know how many support issues come in and when you compare that to the number of Titler Pro copies being used, it is an extremely small percentage.

This is probably because people:
- Bought It/ Tried It
- Used It/ Crashed It
- Abandoned It
* Just because they bought it doesn't mean they're using it

Edward, is it possible to have a logged version of NBTP.

We *HAVE* a logged version. The full retail version does have a logging option which I have used for many people.

Just this week alone, I have had several people who were having titler lssues indicate success in using Titler Pro AFTER:

1. Updating their video driver

2. On a laptop - setting it to use the full video card instead of dropping down to a low powered limited functionality mode.

"On a laptop - setting it to use the full video card instead of dropping down to a low powered limited functionality mode."Can we get some further details on that statement? Where do I set this "full video card"? NBT? Vegas? Windows? Device Manager?

I do most of my editing on a Dell Studio 15 laptop with an ATI Mobility Radeon HD 545v display adapter (non GPU accelerated).

...Jerry

We *HAVE* a logged version. The full retail version does have a logging option which I have used for many people.


How can I enable it?

When I go to:

C:\Users\USER_NAME\AppData\Roaming\Titler\globLog.txt

it doesn't show up any details other than when I launch Vegas (and got NBTP to crash), I got this:

LOGGING STARTED [12/02/24 16:23:01.031]

...and nothing more


Rob