Just noticed today that there is a new update for Titler Pro. The build number is 120718. Notes seem to indicate that the cause of previous crashes has been remedied. Has anybody checked this out yet?
Are you seeing any watermarks on the output? You should not be seeing any watermarks. Just ignore any requests to activate. Everything will simply work fine in Vegas Pro 11 as long as you are using the OpenFX version of Titler Pro and the Starter Pack."
So, I reinstalled the currently newest Version 1.0 Build 120718 over my Build 120402 and this time I didn't even need to reactivate. However, I still feel uneasy about the "requests to reactivate" on their installed EFX and Transitions. To me it seems a sort of marketing nudge to keep reminding me that those samples are a gift that needs to be paid for by upgrading. My response to that is: Hey, they were part of a package I already paid for and you should take that up with SCS not me!
Sorry, but this whole thing lacks of professionalism to my OLD thinking. Nuff said, I'm outa here, I got better things to do then play with NewBlue...
Edit: Geez, discourteous me, I would also like to say, thank you NewBlue for the TitlerPro as I love it (when it isn't crashing every other move) and thanks for the free EFX and Transitions (that is as long as they don't time out soon)...
I'm going to be cheeky here and slip in a new user's question.
I'm trying to teach myself NewBlue Titler Pro. A steep learning curve but am making progress.
You guys are experts so forgive me. But I can't find a way of pasting attributes from one paragraph to another. Am I missing something? Or maybe there's a workaround?
every time I'm gonna shake in the text NewBlue 3D titler, vegas pro 11 falls. need to be saving step to not lose the project,
Problem really is with NewBlue because outos plugins funcionan perfectly vegas pro 11;
I'm so confused that no longer know what I use and test the upgrade.
My problem is when I create several titles in the project, every step he closes. and to restart Vegas.
I tried the current version and old version. compatibility mode and same thing always happens
That reply makes me angry in so many ways, I don't even know where to begin.
I think I'll let someone else handle this one, I have to keep my blood pressure down.
We can't help you if we don't know you are having an issue.
I went back and forth with NewBlue FX support a few times, trying all their suggestions on NBTP, then they just stopped responding leaving me with an open ticket.
My issue was/is NBTP not showing up in Premiere CS6.
When we got it to a point where it shows up, Premiere CS6 crashes if you try to use NBTP. Not to mention the AfterEffects errors that there are multiple copies of the NewBlue FX on my system.
In Vegas, it works, crashes, don't work, works, crashes, freezes, kills vegas, etc.
There's way too many other plugins that work to be fooling around with a company that just doesn't get it.
Hmmm, I didn't realize NBTP was having problems in Premiere CS6, I thought all the problems were confined to Vegas 11 (really, I'm being serious for once), I had thought it was a problem with the code written for Vegas 11, but this realization that it doesn't work with other video editors changes my view of the problem.
And as for reporting the crashes in a report to NewBlue....been there done that, as I'm sure a lot of people have. I've also tried several suggestions made by NewBlue as well as suggestions made here in this forum.
The statement that "we can't help you if we don't know what the problem is", is the most outlandish thing I've heard so far coming from NewBlue. Just how many crash reports do you need to know there's a problem?!?! That statement may even top the infamous "we're looking into putting version numbers on the website" which they've been saying for a year now.
As I said, I don't need the aggravation any more, I'm delightfully happy with BorisFX BCC 8. All the same plugins available from NewBlue, plus more. And they work perfectly....no crashes! Costs a little more, but you can't put a price on peace of mind!
As co-founder and CEO of the company, I think it's time I stick my head in here, so please feel free to bite it off!
There is a lot of very understandable frustration about the lack of version information in the Titler Pro downloads. This was an oversight on our part. It didn't matter much when we had simple plugin collections. But, with the complexity introduced by releasing Titler Pro both as a bundle with Vegas and simultaneously as a stand alone product (yes, the same bits work in both cases - running Titler Pro inside Vegas 11 automatically "unlocks" the retail product) we upped the complexity. Add a release snafu a few months ago where there was a divergence, and the confusion is real and unfair to our customers (let alone our diligent support team!)
Anyway, enough excuses. We are working on a solution and plan to have our website and app upgraded in the next two weeks to have a system in place to clearly identify the build, and have a summary of what is included with each update as well. We hope this will make it much easier for our customers to keep builds up to date.
I personally apologize for the frustration this has caused many of you.
And, one more thing. Please know that Edward and Marcus, our public face for support and forums, are incredibly passionate about getting things right for our customers. Every support email or ticket is copied to my inbox, so I know how personally they take every issue and how tirelessly they campaign to make sure each one is solved. And, many of you have known Edward longer than NewBlue - he's as dedicated as they get to the Vegas community (and indeed I believe I first met him on this forum.) So, try not to shoot the messenger! We are all on the same team!
Indeed, last week Edward wrote up a lengthy tome on how we need to fix our versioning. This is the blueprint for our upcoming solution.
So, please report your problems, especially using our ticketing system, but also here on these forums. We want to know about every single issue every customer is having. We take this personally. We believe that for every person who says something, there are many more who suffer in silence and that's totally unacceptable. All of us on the NewBlue team cringe when we hear of a customer difficulty. It's not just business as usual, though it may seem that way at times. Like you, we are authors, and we care enormously about our audience's experience.
As for crash issues, you have no idea how seriously we take these. Yes, the vast majority prove to be driver issues, but we can't pass the buck. Instead, we are working to improve the error reporting and automatic fall backs so the software can figure it out for you as well as our support team.
We look to you, the Vegas community, to help us make our products better. Your candid comments, advice, and support truly make a difference.
Cu do’s to you Todor, I am very impressed that a CEO would come here and admit that mistakes were made and that they are being worked on.
I would like to see SCS step up and do the same thing, maybe if SCS like you would do that, tempers would not flare as much and this community would be a better place.
WHEN you get all the kinks un kinked I feel that the product will be very nice, I have used it for a few things and it has worked fine for me, but I know others have had problems.
It is nice to see a passionate person as CEO and one that is willing to as you said stick ones neck on the block.
I know that you know but just to mention Edward is a very great person to have on your team (and ours of course)
I just say Thank you and keep popping in once in a while, just to say HI !!
very good. Now I see that is an undertaking would, vain and solve our problems with NewBlue vegas.Vou and wait these two weeks and return to the NewBlue plugins.
thank you
This is not the only forum/NLE where people are having issues with NBTP. So it doesn't matter to me, who comes on here and says what about this crappy piece of software that evidently has issues. What does matter is the software working as advertised with no crashes and frustration. Actions speak louder than words. Stop all the talk and promises and fix it!
I guess I'm kind of in the middle. While it is appreciated that NewBlue is communicating with its customers, when you're this deep in **** and the program performs so poorly, I'm afraid that actions DO speak louder than words. Especially when we're hearing the same words over and over again.
I guess we'll know six months from now. If things get back on track and fixed, we'll know the CEO's intervention was for real. If things linger on as they have for past six months, we'll know the CEO's intervention was just for show. I anxiously await the outcome.
I have Sony Vegas Pro 11, latest build on a Sony Vaio L-series with a Nvidia Geforce GT540M and was having the crashing problems every 2nd time I put a NewBlue Titler on the timeline or did an edit from the timeline. I submitted a Help Ticket and the response was quick and useful, so far everything is working fine with the advice I got, it was just getting the GPU to work at high performance with Vegas Pro.
All though frustrated to start with, it's all good now and love the program,
keep the spirit
Marcus
rEvo, Does it crash if you turn off GPU? (apologies if you've already answered this) I'm one of the ones who hasn't seen a NBTP problem, but I don't use GPU.
Vegas version is OK. (no gpu)
Premiere version is not OK.
Lots of my other NewBlue FX plug-ins don't even show up in Premiere. NewBlue FX suggests a method by which you open a .log file to see which plug-ins are not loading. Then you have to do a registry hack and change an Ignore Value.
Seeing as this is a Vegas forum, I'll just sing my praises for NBTP working in Vegas and continue my support ticket w/ NewBlue about my CS6 issue(s).
_____
As a follow up:
NewBlue support sent me a file called "PremiereEffectFixer_x64.exe" which automatically fixes the registry for the 'ignored' fx in premiere. (Very Helpful) After manually selecting the right plug-in path for CS6, all the plugins show up in Premiere. (I had to choose between installing/using them in Premiere or After Effects)
Although I'm still a bit gun-shy, Vegas(64) appears to be working fine w/ NBTP and all NewBlueFX!
"Anyway, enough excuses. We are working on a solution and plan to have our website and app upgraded in the next two weeks to have a system in place to clearly identify the build, and have a summary of what is included with each update as well. We hope this will make it much easier for our customers to keep builds up to date. "
Oh, and please get someone to finally fix my crash issue - Viewing Ticket TECH-UC36UX6DTF.
I have now sent you 2 demo videos clearly showing the issue, two full sets of crash logs and a sample project. What the hell else am i supposed to do. Its been months.