New Blue FX Titler Pro 3 bug

David Johns wrote on 8/20/2014, 10:09 AM

I have never had much luck with Titler Pro. So far, each time I've tried it, it has weird behaviours (too long to explain here).

So today I just tried to use the preset templates and just added my name and title. All looks fine in Vegas, plays back smoothly.

But when rendered:

(flashing name and rectangle boxes at the start). Happens regardless of Sony AVC or MainConcept AVC render.

Also I notice the flare jump-cuts from position to position despite being within the "fixed" portion of the TP3 timeline

I tried using TP3 for a client project a couple of weeks ago, had the same issue - flash frames on render - but assumed I'd done something silly in the Title Designer and didn't have time to solve it. Maybe not me after all.

Am using the latest version of TP3 (or at least, it tells me it's up to date)

Sigh. Can anyone suggest a fix (or another Titler that's cool and plays nicely in Vegas?).

David

Comments

NormanPCN wrote on 8/20/2014, 10:59 AM

I tried the project template you used in the video and it worked fine for me rendering to playback and rendering to Sony AVC.

I am using build 140725 of TP3. In the past, I have seen the NB updater say it was current and yet there was a new build online.

I have an AMD GPU with driver 13.12. GPU is important since TP3 is a 100% OpenGL 3D rendering app.

Save that title sequence as a project, and open it with TP3 stand alone, no Vegas, and can it render a MOV file properly there? If it does then at least you can drop the MOV file into your video project. The MOV TP3 outputs is an image sequence with PNG files with full transparency.

NewBlue certainly has their bugs, and I am affected by them as well. I still have outstanding, reproduced, bug reports in TP3. Simpler things that can be worked around in my case.

David Johns wrote on 8/20/2014, 3:11 PM

Hi. Thanks for trying that. Would you humour me and try it on a 25p project, out of curiosity (I'm in the UK so my timelines are either 25p/i or 50p)

I too have an AMD card; not sure which driver but I checked it was up to date fairly recently I think.

I'll try your standalone .mov idea, that could be good.

Cheers
Dave

NormanPCN wrote on 8/20/2014, 3:43 PM

I tried it in a 25p project and it still works for me.

I have seen a problem with the current AMD 14.4 driver with the Vegas noise generator effect, so I am sticking with 13.12 for now.

Lovelight wrote on 8/20/2014, 5:54 PM

GPU off may help.

David Johns wrote on 8/21/2014, 6:10 AM

Oh, trust me, I have GPU firmly switched off all the time else Vegas is just too unstable.

However, I think I'm right in saying that TP3 uses the GPU independently of Vegas so that wouldn't make a difference in this issue.

Thanks
Dave

David Johns wrote on 8/21/2014, 6:11 AM

Thanks for trying. I'll double check what versions of everything I'm running. Such a nuisance though.

Regards
Dave

jetdv wrote on 8/21/2014, 9:55 AM

David, please make sure you send all information to NewBlue.

Also, please make sure you are on the newest build.

David Johns wrote on 8/22/2014, 10:19 AM

Hi

What's the preferred method of communication with NB? If email, to where?

As already stated, TP3 insists it is up to date.

Regards
Dave

jetdv wrote on 8/22/2014, 10:25 AM

support at newblueinc.com

If you go to www.newbluefx.com, there's an "Ask" button on the right-hand side. That will also let you send an e-mail or, if available, start a chat session.

Amata wrote on 8/22/2014, 2:42 PM

Sorry no answer for New Blue FX Problem but just wish to second your Titler Pro issues , I have never been able to get it to work in any shape or form even at V12 version.

I believe that Vegas was designed for SD Max my personal experience would say that in SD editing applications it worked 60% of the time to 50% of its claimed ability.

I am sorry to say that I am looking for an NLE that will edit HD PLUS the ability to apply FX and preview same in the preview window in HD with the FX applied so I can actually see what I have done and what my out put will look like.

OldSmoke wrote on 8/22/2014, 5:56 PM

@Amata

VP12 and 13 are working fine over here with HD 1080 60p and 4K files from my AX100 so your statement is more then inaccurate.

David Johns wrote on 8/23/2014, 6:36 AM

@amata

Not sure I agree with that; Vegas Pro has always been great for HD editing for me (provided I switch any GPU acceleration of playback or rendering off); real-time playback of course depends on which effects you add and how many and I grant you Vegas isn't the best at this.

As for Titler Pro, I have sent their support an email but given some other peculiarities I find with it, I'm not confident about using it for real. Shame, 'cos it's got a nice feature set, on paper.

Regards
Dave

videoITguy wrote on 8/23/2014, 3:02 PM

VegasPro in the iterations that have been plagued with the least bugs, for example VPro 9.0e, or VPro 13 build 373 are more than adequate. There is nothing that can stop you from building a robust platform for editing and compositing and it can include all the third pary efx including NewBlue that you can afford to pay for.

Lovelight wrote on 8/23/2014, 9:10 PM

Except for the memory leaks, GPU off, and ram preview set to 0, nothing can stop us.