The download for Vegas users is always here:
http://www.newbluefx.com/so/sonytitlerpro/

no mention here of versions (there never is) or any update. Are you looking at the correct download? Not the generic Windows version.

Paul.

You know, with all the complaints about Vegas specific release versions, you'd think by now they could have figured out that posting versions on that web page would be a real plus.

Just my $0.02's worth.

Tom

Downloaded and installed the version you reference. It gave options for VEGAS. Didn't even ask for my registration number.

Also, it gave options for just Vegas Pro or Vegas OFX, both 32 and 64 versions on install.

(of course, I had the previous version from Vegas installed.)

So far, so good.

I, too, find the lack of version numbers very confusing. I am currently running build 120402. Check for updates indicates the updated build is 120528 with extensive fixes for Vegas V.11. But, when using the link mentioned above to download, it downloads only the older build-not 120528. When you download the available file from the update window, it installs build 120718 (which looks like the generic version). Also, there is no longer a warning not to use this version for Vegas 11 and the included notes refer specifically to fixes to Vegas. So I am confused as to how to obtain build 120528.

It is totally confusing. Assuming you had the version from the Sony link you received when buying/upgrading Vegas, mine showed I had v.120402 installed and there was a newer v.120528 when looking at update via the menu. However, after updating mine still showed v.120402 on the Help tab in NB.

I then downloaded the version from NB and installed. It showed options for Vegas. I now have v.120718 installed. It seems to be working fine. It didn't even require a re-entering of the registration.

tom

The link in an earlier post

http://www.newbluefx.com/so/sonytitlerpro/

gives version 120402 as at 26 July 2012, and the file name is

NewBlueTitlerProForSonyVegas11Setup.exe

Previous versions also had this name but the file sizes were different. Those I have are

Version --- File Size
111013 --- 58734809
111024 --- 58398554
120208 --- 65769859
120402 --- 66037186

However, downloading from this site

http://www.newbluefx.com/titler-pro/

claims to give a version for Mac and Windows, but the file is named

NewBlueTitlerProForWindowsSetup10.exe

Its file size is 86,063,038 and when installed reports version 120718.

It is supposed to work on other video editors as well.

I am going to wait 'till jetdv pipes in.

Just want to be sure, you know?

Tom

I went ahead and installed v.120718 on both my workstation and laptop. I'm running Vegas 11 x64. Things are working good on both. This version (NewBlueTitlerProForWindowsSetup10) allows setup on multiple platforms including Vegas.

tom

The current "Windows" will work fine in Vegas Pro 11. You do need to make sure you only install the "OpenFX" version, though. The DirectX version is there for older versions of Vegas Pro and Movie Studio that did not support OpenFX.

Isn't OpenFX one of the things still causing trouble in V10 and V11? With my other NewBlueFX plugins, I've been using the non-OpenFX versions for stability.

I am very angry with NewBlue titler. Already updated it., And every three texts he closes vegas, need to be saved directly.
Vegas Pro 11 very unreliable. Not looking forward to vegas 12, just hope that stabilize the 11 version.

First disclosure here: I am not a licensed owner of New Blue Titler or even VegasPro11. The entire fiasco of Titler in trial bundled with an early buggy VegasPro11 is one for the books. It could have been prevented and should have been because everyone is now spooked.

As PeterDuke so aptly points out through his careful analysis of versions coming down - NEWBLUEFX has quietly been working on a release for Titler that can be installed on various platforms - and this includes the 32bit world of VegasPro9 with DirectX.

Originally this development was not supposed to be cross-licensed with the earlier bundled release for VegasPro11 users - BUT I wonder if this "rule-out" has been changed.

Hence, the point - for users who want to try it - install the DirectX version in Vegas11 and report what happens. AND for those in Vegas9Pro install it in 32bit app and see what happens. We look forward to some full field reports in this regard.

Had 528 installed.
Per jetdv I downloaded at the link provided.
after installed TP version was back to 402
downloaded the update from the TP help - installed.
Now Vegas crashes every time upon launch.

If you use the DirectX version, you WILL get a watermark unless you purchase a retail serial number. If you use the OpenFX version, there will be no watermark in Vegas Pro 11 but you will get a watermark in all other versions of Vegas unless you purchase a retail serial number. So, yes, you MUST use the OpenFX version in Vegas Pro 11 for that reason.

I understand some people are having issues. I also understand the VAST MAJORITY ARE NOT HAVING ISSUES. So it comes down to what's different for those that are. There are so many variables that it's hard to give everyone concrete answers.

For example, what video card/video driver version are you using? We have had a LOT of people that found simply updating their video driver resolved their issues.

Another example, how many screens are you using? We've seen cases with people using ATI cards and Titler Pro on the secondary screen caused crashes. Put Titler Pro on the main screen and everything worked fine!

We've been trying hard to resolve reported issues. With so many variable systems, variable OS's, OS upgrades vs clean installs, video cards, video drivers, multiple installed devices (See Grazie's media manager post as an example) that could cause a conflict, etc... it's no wonder some people have issues.

Jet, could you please provide a specific link to version 120718?

As stated earlier, when I downloaded from the link the provided I actually got v 402.


Tnx, Steve

http://www.newbluefx.com/downloads/Windows/NewBlueTitlerProForWindowsSetup10.exe

Same as the link found here:
http://www.newbluefx.com/shop/videofx/effects/titler-pro.html

Had to use Revo Unistaller at level 4 to remove all NBTP - then downloaded again from the exe link you provided. All is well again.


Steve

So it appears as JetDV seems to point out - there is now only one installer available for any and every version of NB Titler Pro that you could desire.

Now the question arises - as JetDV points out - that if you want it to go into the VegasPro11 using OFX - you can use the previous license granted from the Sony bundled install. If you choose to install it as direct-X anywhere you will be asked for $299 for a new license?????.

As some have seen that the installs can get very messy - IS IT better to do a clean install regardless of the OFX/Direct-X 32 bit/64bit choices? that you must make at the install point. Then just use the appropriate license fed into the install?

jetdv - I don't know the percentages of who is or isn't having problems with Titler Pro, but a claim that the "VAST MAJORITY ARE NOT" are both speculative, not entirely accurate, and not at all helpful. Do you have facts to back up this claim?

I don't know if you happened to see the pie chart I made which was based on end user reviews of Vegas 11, but it showed only 33% of those responding found Vegas 11 perfectly stable (those who gave it 5 stars for stability) the other 66% gave it 4 stars or lower.

Since Titler Pro is so tied in with Vegas 11 and many of the crashing problems reported here in this forum (and work arounds to these problems) specifically mention NewBlueFx's Titler Pro, I really have to wonder about your statement.

And even forgetting about the percentages for the moment, the severity of the problem is also in issue. You seemed to indicate that "a LOT" of people found simple fixes to get Titler Pro working: updating a video driver, not using a secondary screen, etc. But again what we've seen and read about in this forum is that the root of the problem seems to be a lot more severe, perhaps something written in the code of Vegas 11 that's not even NewBlueFX's fault. But still, the problem persists, it's severe and there seems to be no simple fix for many of the users here. In fact when people are reporting a crash in Vegas 11, one of the stock suggestions now is: "Have you uninstalled NewBlue Titler Pro?"

And last must not least, WHAT is the deal with you guys and version numbers? Putting version numbers on your website next to the plugins, and including the version number in the file name, IS something within your power to do. The lack of version numbers is a big sore point with your customers, and I'd think NewBlue would want to do anything it can at this point to keep the complaints to a minimum. We've only heard excuses so far: "It's not as easy as you think to put version numbers on the website". How hard is it to put a version number in the file name?!?!??!

To Leee,
This is sort of ...a response.. to your concerns and I do feel your pain. I have been in the software business since before Windows 3.0 and I understand the concerns that work into this from both sides of the aisle.

I would suggest that JetDV has been guarded in his release of info as any businessman might be. So, yes to generalize that many are having success in the VegasPro11/BlueTitlerPro bundle does not really help. Unfortunately there is no real easy way to quantify these impacts - just as you yourself were critiqued in your careful study of VegasPro users. I do know that NewBlue is fully aware of how many licenses they released, and in general how many complainants they have. BUT can that ratio be trusted into a somewhat kind of good statistical finding of how many users have no complaint.

Probably NOT.

What would be helpful as you suggest is a good versioning system- better documentation, and upfront release of info on what they are trying to accomplish. How many knew they were going back to the drawing board to bring-in the direct-x user?

VideoITguy, yes I understand what you are saying. It's almost impossible either way to come up with exact numbers, but I DO know, wild exaggerations leaning either way, usually turn out to be false.

There are also those people that are still having problems that are not complaining anymore, like myself, I've just given up on NewBlue plugins, written them off as a loss and moved on to BorisFX's BCC8.

But I still read these message boards and still see advertisements around the Internet for NewBlue, and am astounded that they still have not implemented a way to display plugin version numbers on their website or in the file names. I just don't get it.

Most other executables seem to carry this info and you can see it by Right-Click -> Properties->Details.

Like this for the Quicktime Installer.