Leee, I don't know anything about your pie chart but I do believe Titler Pro is being unfairly vilified. I think it's unfair to say simply uninstalling Titler Pro will make Vegas more stable and am still unsure exactly where that came from. If Titler is installed but not used, it will not affect Vegas in any way. The only exception to this is ONE case where Titler Pro is not initializing properly causing Vegas to not start and we are researching this issue with that person.

We are looking at the versioning information. I'm not sure yet what the final solution will be but we are looking at a few options. The Check For Updates feature is always available too. And, yes, it's not as simple as just adding the build number to the file name but I will be pushing for that to be part of the solution. We have to be careful we don't break things in the process of making things better.

As for my claim, all I can go by is the number of Vegas users with Titler Pro compared to number of complaints that we have had. And most of the complaints we've received have had their issues resolved. Yes, we still have a handful of open issues but compared to the hundreds who have downloaded it, that is an extremely small percentage.

As for someone having an issue we don't know about - well... we can't help them if they haven't reported anything to us. That's why I always request when I see issues here that they go to newbluefx.com and start a help ticket there.

I don't think anyone is trying to vilify NewBlue, especially myself. I've posted several times how (up until the Vegas 11 fiasco) NewBlueFX were my favorite plugins for Vegas and when they work, they're great.

As for the uninstalling titler pro, I have used that work-around and it has worked. In fact I was reluctantly forced to uninstall all my NewBlue plugins because every time I clicked on one of them, Vegas crashed. Don't ask me what version numbers they were, all I know for sure were they were the GPU versions.

As the previous poster mentioned, I'm sure there is a significant amount of people not reporting/complaining any longer because after all this time, they just want to be able to work with Vegas 11 without any crashes. And by following the workarounds that have been suggested, including among others, uninstalling Titler Pro, users that had previously been unable to use Vegas 11, are now finding it semi-stable and functional enough to actually work on projects.

And finally, I hate to sound angry or mean, but you have been "looking into" implementing a version labeling system for almost a year now (I still have messages from you from 8 months ago saying the same exact thing). How long does it take to "look into"? And why are you unable or unwilling to add a simple version number to the file names. Surely that doesn't need to be "looked into", just rename the friggin' file! I have a dozen NewBlue update files on my hard drive, and they are ALL labeled the same exact thing. The only way I can tell one from the other is by the "created date" which was created by my computer, not NewBlue.

To Jetdv,
Points taken! Just uninstalling TP made no difference that I could see. In my case, the crashes mostly occurred with the TB window open and while executing a change in the title or effect. If this continues I will file a report through New Blue. We really do appreciate your participation in these forums.

And why are you unable or unwilling to add a simple version number to the file names. Surely that doesn't need to be "looked into", just rename the friggin' file!

And break every link on our website! And, yes, we are looking into it! But trying to come up with a solution that will not break every link on our website.

Before I switched to the world of scientific research and academia I spent about 30 years in the corporate world as a vice president of engineering at various high-tech companies. I would have been highly embarrassed if it took my employees over a year to sort out a web design issue as you describe. Furthermore, If I did not respond rapidly to a major customer complaint such as this, my job would have been on the line. One must therefore wonder if NewBlue has an actual office and engineering team or are you folks merely a garage operation?

Peter

And break every link on our website!

I am with Peter here. Spent the majority of my previous life in s/w development.

Having to field so many irate posts and likely support calls, one would think, just bite the bullet and get it done and spend the saved cycles fixing the major issues.

Dealing with, perhaps, a few broken links would be a small price to pay to placate frustrated customers that you don't want to alienate.

Tom

jetdv said, "And break every link on our website! And, yes, we are looking into it! But trying to come up with a solution that will not break every link on our website."

You simply create a new site for the new way of naming the files and give a link to the old site for the older versions of the files.

So you have a new site for new versions and the old site for older versions. Eventually the old site will fade away because it will no longer be needed.

As for not reporting on NewBlue Titler Pro Software, I still have the original version on my computer. Because of all the posts I have seen about it I was extremely reluctant to even mess with it beyond that. And because of the absurd version mess I was not sure what to install.

There is absolutely no excuse for this to have gone on as long as it has. That is severely unprofessional!

Finally, if your current site is such that all the links would be broken then it is an extremely poorly designed site!

Yes, I realize the current links could be updated. However, it's more than just renaming files and updating current links. Surely you all realize that. There's also maintenance to consider and procedures to put in place so that everything is properly updated when each new update is released.

As for sticking with the original release versus updating the current one, the current version has MANY bug fixes and also MANY new features that you're currently missing. I would go ahead and update.

I don't know, I guess I'm missing something. For the website: No links have to be changed, only the text on the webpage NEXT to the download link(s). Every time there is a version update, just go into an HTML editor and add some text next to the latest version link that says, "This link is for update 1234.56"

And if for some strange reason you have a link that is "set in stone" to a specific file name, why not just add another link below the original link pointing to the file name WITH the version number in the title? But again, I can't understand why you would create such a rigid system, if that is indeed what the problem is.

As I said, there are many other web creation experts around here, and I only know a little more than the basics. Any website I create, I keep it simple. So maybe your website is so complex, with inter-related links, file names and pages, all dependent on one and other, that changing one file name would bring down the entire house of cards! Maybe a simpler approach would be better. Something maybe a little more flexible and easier to work with?

hey Jetdv.. If you would provide us a direct link to the updated version, since I have owned pro 11 I have yet to download pro titler do to not so positive comments. That said I'm willing to give it a shot.
thanks

Chaunc

OK

I'm confused as to the most current version.

Is this this one? I have this installed on my shiny new Dell XPS laptop and everything seems rock solid (so far).
http://www.newbluefx.com/so/sonytitlerpro/

Or this one?
http://www.newbluefx.com/titler-pro/

Kimberly, you're confused?!?! How can that be?
I mean there is SO much good information on those two pages that you linked to, including system requirements, features, compatibility, everything except what the latest version number is. Oh that's okay, just click on the download link of each page, and you'll be able to tell which one is which. No? Well, I'll be a monkey's uncle, both files say "NewBlueTitleProforWindowsSetup10.exe" Are they both the same file? How can you tell?
No problem, just down load both, install both, and then you can perhaps check the version number in the "about" box.

See, that's not that difficult. Far more easier than what NewBlue might have to go through to perform a "brain surgery" type of operation just to stick a label number next to the download link.

Am I being sarcastic? You bet. Am I pushing the point? Maybe a little
Am I angry and frustrated? Only just enough to want to kick my cute little dog.
Am I going to stop? No, I have nothing better to do, and I believe in justice for the little person. I believe consumers should not have to settle for anything but an excellent product when they pay their hard earn dollars in purchasing it. And I believe companies should not only make as good a product as they can, but without excellent customer service and customer relations, you might as well be buying a broken calculator.

Kimberly:
your link under "is this the one"? leads to a version only for Vegas11.

Here is JetDV's response earlier in this thread - at the request of finding the latest update: "Reply by: jetdv
Date: 7/26/2012 11:10:09 AM
http://www.newbluefx.com/downloads/Windows/NewBlueTitlerProForWindowsSetup10.exe

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


Note the name of the file he has suggested - this is likely the latest code - because it's a universal install for all systems, GPU or direct-x 32bit or 64bit.- So the likely answer to all this - it may in fact not have anything different for Vegas11 GPU use - but it certainly has code applicable to more circumstances.

I had asked him if this was cross-licensed for the bundled install, but he did not answer that specifically - he did indicate you would get a watermarked install if you chose to use direct-x.

@jetdv "Yes, I realize the current links could be updated. However, it's more than just renaming files and updating current links. Surely you all realize that. There's also maintenance to consider and procedures to put in place so that everything is properly updated when each new update is released. "

Actually, it IS just a case of renaming a file... Its a website. If it was that difficult, how can you explain why all other plugin manufactures have this basic info on their sites? You know what, why not set up your own page and place the files on it - then tell us how complicated it is to change a filename or HTML line.
Note to your web designer: if this is too difficult without breaking your entire website, then please reconsider your job position as a web designer. I am trying not to be cheeky or condescending, but please have a word with your guys, this is ridiculous. Someone needs to think outside the box.

PS. my own crash copy paste NB fx was never fixed. Cant remember how long ago it was filed, was it a year maybe? The only fix i found meant using the 32 bit version of Vegas, this reduced the crashing. But SCS have announced that 32 bit will be discontinued on the next release of Vegas. So basically - i'm stuffed if i update.

PPS. During the initial contact with your tech guys, i was told to try the Windows version build as a test. After downloading and installing it - NB titler crashed even more. I was then instructed to go back to the Vegas build. So my advice to anyone trying the Windows build is - don't. Been there.

Overall, my experience with NewBlue has been disappointing. And i say that with some regret because we Vegas users are constantly being ridiculed from other NLE users - namely FCPx and PPro in particular, they think we are a joke. That's nonsense of course but its the way we are perceived in the industry. Having better plugins, with high stability, epic grading controls, motion tracking and pro titles all helps to dispel this negativity towards Vegas. Any plugin with instability should be removed from the set of tools until its fixed - properly. Its damaging to our NLE and to our reputation as a world class NLE.

Paul.

Okay, I don't post here much, but I am (for one) a little frustrated with this Vegas Pro 11 and NewBlue TitlerPro plugin mess. I purchased Vegas Pro 11 with the promise of NewBlue TitlerPro and (I thought) a sampling of effects and transitions. However, if I try to update to the newest OFX build 120718 (or even the one before that) I seem to lose the ability to use the free efx and transitions that during my use with NewBlue TitlerPro build 120402 were successfully activated. My original (Sony Vegas Pro 11 provided NewBlue TitlerPro and, I thought, sample efx and transitions) serial number no longer seems to activate the efx and transtions. What happened? ;-(

Digvid - contact NewBlue support about your problems - and then we would like to hear your final report back here.
Thanks

Hello All:

I have Vegas Pro 11 and the NewBlue Titler Pro on my new Dell XPS laptop. So far it runs solid, no crashing, no annoying messages, renders pretty fast for the scope of my projects -- hope I don't jinx it now that I've said it : )

Initially I did receive some messages/crashing around not having sufficient GPU to run the NewBlue Titler Pro. I found on Forum that you must fiddle with the nvidia settings to tell the system to use nvidia. After that no problems.

I cannot explain why this system works well other than it's brand new and hasn't had time to accumulate too many barnacles? Here are the specs in case that is helpful to anyone:

Vegas Pro 11, Build 683

NewBlue Titler Pro from this link:
http://www.newbluefx.com/so/sonytitlerpro/

Processor
3rd Generation Intel® Core™ i7-3612QM processor (6M Cache, up to 3.1 GHz)

Operating System
Windows® 7 Home Premium, 64bit, English

Memory3
16GB3 DDR3 SDRAM at 1600MHz

Video Card
NVIDIA® GeForce® GT 640M with 2GB GDDR5 VRAM

Regards,

Kimberly

Kimberly, thanks, but that link is for build 120402 and yes it does install and activate with all privileges. That's why it says "for Vegas 11", in doubt. However, if one who has purchased Vegas Pro 11 (and got NewBlue Titler Pro plus assorted NewBlue EFX and Transitions with it) wants to keep those EFX and Transtions "ACTIVATED", than currently we can't update to NewBlues most recent build 120718. The question is, is there any difference between the two builds to warrant losing the EFX and Transition Activation...

@ DigVid

It might be a idea to log into NewBlue and raise a ticket as to why the 'extra' NB EFX & transitions are no longer available. It could be a simple oversight.

NB respond fairly quickly usually within 24hrs.

Please post the reply.

@ DiverG and videoITguy

I have sent a ticket to NewBlue about this situation.

Just to clarify. If I install the vegas11setup Build 120402 (that jetdv suggests), than all is well with the preinstalled (and supposedly free) samples of NewBlue EFX and Transitions.

Actually, they install every time you install an update for the TitlerPro anyway. And, when that update is used, you will be instructed to enter your serial number before it installs.

However, the OFX (default) version inside of vegas10setup Build 120718 or any build, to date, after the above mentioned, and the one prompted in Vegas Pro 11/NewBlue TitlerPro/Help/Update, will install w/o asking for the serial number. When you go to open it in Vegas Pro 11 then one needs to Activate it. Which simply thats a click on the Activate button. However, I noticed, the preinstalled NewBlue EFX and Transitions need to be reactivated; and when I try to do it, suddenly my Sony Vegas Pro 11/NewBlue serial number is no longer sufficient.

Very frustrating and time consuming.

I will get back once I hear from NewBlue Tech...

DigVid - THIS IS EXACTLY the info that we want to bring to the attention of JetDV.... please review all the posts in this thread that I have made and also review JetDV's responses.

What you are pointing out is exactly what this thread has been trying to determine - what is the process that NEWBlueFX as a company trying to accomplish with the different initiatives of their install packages.

Now, perhaps your "fail" is just unique to your system - but I would like to see better info coming out of NewBlueFX.com