Serena, Pro 12 will run NBT 1.0 just fine.
NBT 2.0 is a completely separate titler package.

Mike

Thats a good question Serena, though I have used the link given to me by Sony to download NB TP, when I purchased V12.

Titler Pro 1 comes bundled with Vegas Pro 11 and 12. You should update to the most current version as per the link that comes with Vegas Pro 12.

Titler Pro 2 is an optional upgrade available with Vegas Pro 12. It adds many new features and, if purchased, will give you a retail serial number meaning you can use it in all supported NLE's on your machine.

I have been struggling to get NewBlue Titler1 to work since the first day that Vegas 11 was released last year. I've tried every NBT update, with GPU on and off.

As soon as Vegas 12 was available last week I tried NB Titler1, but immediately got the same white/frozen screen in VP12 as I did in VP11

I have therefore completely given up on this pile of junk software, and have absolutely no faith in this company's products, and will certainly not be wasting good money on NB Titler 2.

Moral = AVOID !!!

Did you notice when you installed the latest NBT 1 update, build 120815, the NewBlue Starter Pack effects are not activated? I am not seeing a watermark so I assume everything is okay.

ed

Actually, the link supplied by Sony took me straight to build 815, so yes I have the latest update. Again, it seems strange that it is working fine in V11 but V12 does not want to know.

gripp, if it's not working on your system, please start a help ticket at newbluefx.com so we can get your system settings and try and determine what in your system is causing it to fail.

Titler Pro 2 is an optional upgrade available with Vegas Pro 12. It adds many new features and, if purchased, will give you a retail serial number meaning you can use it in all supported NLE's on your machine.

jetdv, if I had known ( no menttioned in the ad) the Titler Pro 2 upgrade would work with all other supported NLEs installed on the system. I would have upgraded.

ed

I've had tons of crashes wtih NB Titler Pro with Vegas Pro 11 and 12. It tends to be a bit more stable when I disable GPU acceleration. I'm close to giving up, too.

Ed, you might call Sony and see if it can be added after the fact.

Thanks, Ed

I have sent Sony an email.

Ed

for people struggling with Vegas 11 or 12 can I suggest trying the following.
uninstall video drivers.
boot windows into SAFE MODE
run driver sweeper in safe mode
install nvidia drivers 296.10 in safe mode
reboot

I did the above and Vegas 12 is running fine with no more strange problems.
windows 7 64
Nvidia gtx 560 ti 448 core
i7 ivybridge @4.3 ghz
16 gb ddr3

worth a try.
john

I've used Vegas since it was Vegas Pro for audio only back in 1999 or maybe it was 2000. Anyway, I've bought all the upgrades over the years and Vegas 12 was so cheap I reckoned why not. Tried to put a NewBlue title at the front of a clip...crash. Tried again...crash again. Version 11 was flaky too so I uninstalled it and stuck with 10. And V12 seems to be flaky from the get go. So I guess I'll continue to use Vegas 10 for Ken Burns effect and stick with Premier Pro CS5.5 for editing work. Rather sad, this instability.

SuperMicro Board, 32 gigs RAM, dual quad XEONs and nVIdia QuadroFX 4800. Windows 7 64 bit Ultimate.

Not sure if this will help, but I had similar problems and quit using NBT. See Q&A thread on SVP12. New Blue doesn't use the GPU's on graphics card in ANY way. It relies completely on your CPU.

Red Diamond, that is not true. NewBlue Titler Pro is fully GPU accelerated. It will not run without a compatible GPU. The older effects were CPU only but the new 3.0 versions of the effects are GPU accelerated.

JetDV, what are NBTP's card requirements? The published data is as vague as SVP's when it comes to compatibility.
One thing for sure, SVP 11 or 12 won't recognized peterB's QFX4600. See this link: https://developer.nvidia.com/cuda-gpus. His computer language is only 1.0. You need 2.0 min with SVP 11 0r 12.

I had same exact nVidia card. It now sits on a shelf and will be used in a computer that cost less than the card to build.

When I removed my GPU, NBT stopped working. It DOES require a GPU as JetDV says. It will NOT work with Intel HD4000 graphics which is a shame.

*Radeon HD 2400, GeForce 8600, GeForce 120 or Quadro FX 4500 or better. Intel HD Graphics not supported.


You do need OpenGL 2.1 or higher.

I had a similar problem arise today. Vegas Pro 12, NB Titler Pro 2.0 upgraded (both as 64 bit) and each time I selected Titler 2.0 in the media generator Vegas would crash.

After a lot of system investigation I narrowed it down to a faulty installation of the NB Titler Pro 2.0. It appears to load 32 and 64 bit versions and put the 64 bit version in an 'x64' directory under the 32 bit version.

To fix it I started regedit and checked the NB settings, changing the locations of the Titler pro installation directories to more correct values (Program File (x86) for the 32 bit version and Program Files for the 64 bit version). I then pulled all the 32 bit versions of software I had in the Program Files (x86)/New Blue directory and moved them to a temp location, as I did not want Vegas to load the 32 bit versions at all. Now everything in the x64 directory was moved to the correct 64 bit installation directory entered into the registry (Program Files/New Blue/Title Pro 2.0/). So all the 64 bit version of NB software I had installed matched the correct locations in the registry.

Restarted Vegas and now it is working perfectly again.

Hopefully this is of some help.
- Geoff

Geoff, can you send full details of what you did to NewBlue support?

Generally speaking, it is OK that some files are in "Program Files" and some are in "Program Files (x86)". But I'd really like to hear exactly what you did so we can test it out here.

Yes, it's usually OK. However I had a problem with Cubase seom time ago where some installations were installing both 32 bit and 64 bit versions of plugins and that's what prompted me to investigate this in case it was of a similar nature.
It turned out that there were 32 bit and 64 bit versions of many plugins installed, so they were moved out of the 32-bit plugin directory (in Program Files (x86)) and the 64 bit plugins left intact (in Program Files).
The only exception was Titler Pro 2.0, which seemed to install a 32 bit plugin in the 64 bit area (usually not a problem) and a 64 bit version under an 'x64' directory. It appears that Vegas was only loading the 32 bit plugin, and not seeing the x64 bit version.
I moved the 32 bit plugin out of the 64 bit area and put the 64 bit (contents of x64) into the Titler Pro 2.0 directory in 'Program Files' instead. Also changed the installation directories in the registry to match.
That seems to have fixed the problem. Vegas is loading just the 64 bit version (it should be all that is available) of all the NB plugins and behaving now.

I've had Vegas 12 and New Blue Titler (the version that came with Vegas) running stable for months and today I swapped out the graphic card because the GeForce 9800 was overheating and having dropouts.

Upon installing the Radeon HD 6770 from an old machine, Vegas started crashing every time I attempted to open any project that had a New Blue generated media within it. Vegas would crash the moment it attempted to load the media to the timeline.

I uninstalled New Blue and the projects load fine.

This Radeon- based card had been stable on the old machine with both Vegas 11 and 12.

I reinstalled the GeForce 9800 and no more crashes. Also tested the machine with my Quadro K4000 with no noted problems.

When tested with my friends Quadro K2000, the system would crash every time I tried to render with the GPU enabled if there was any New Blue generated media on the timeline.