New Blue Titler Pro 2 problem on new Edius computer

[David Ice]

Hi guys,

I just got a new Edius computer built (6.53) and am having some problems with New Blu Titler Pro 2. It runs at a glacial pace.....as in frame...frame....frame. It's nowhere near real time, even with a simple title with no animations or lighting effects.

Also, I can't for the life of me get Titler Pro 2 to open in any track other than VA1....and it obliterates any extant video there. This isn't any good? Any suggestions? THANKS!

David Ice

Intel I07 3930K, GeForce GTX 570CG, 32GB ram, Asus P9X70

[Jerry]

New Blue Real Time performance is non-existent in Edius. It is present in Premiere CS6 and in Vegas 12.... if you turn the GPU off.
This includes Titler 1 and Titler 2. You can get more out of it if you are using 1440x1080 file sizes.
Even with a GTX 690, the performance drops drastically in 1920x1080 in Edius.
The GPU versions allow rendering to be faster...that is it. Just because it says GPU driven doesn't necessarily mean
real time. It is unfortunate.
I have Titler 1 but I use Vistitle for my titles. I get RT with all animations including 3D and texture layers...with multiple titles.

[GrassValley_SL]

Are you clicking the track (targeting) you want to create the title in. Right click ->New ->titler pro.

If you use the T button move the track patch to the track you wish to create titles in.

[Jerry]

Right Click on the V or VA track you wish to use and this will pop up.

New Title.png

[NewBlue_MJ]

Hi David,

I do apologize for your experience with Titler Pro so far. On the majority of computers, Titler Pro clips will need to be rendered before they can be played back in realtime in Edius. Are you able to render your Titler Pro clips in Edius and then play them back in realtime?

As for your second issue, it looks like there have been a number of good suggestions about how to make sure you're adding a title to the right track. Did these ideas help you? Is that part working correctly for you now?

[Jerry]

Titler Pro clips will need to be rendered before they can be played back in realtime in Edius

Marcus, forgive me for being direct. After reading this statement I am a little puzzled. Is this the new marketing strategy for NB and it's poor real time performance within Edius?

Why has New Blue not optimized the Titler Pro product and it's GPU Filter packages for real time playback within Edius? Titler Pro 2 did not improve performance one bit within Edius. Titler 1 was released about 1 year ago.
One would think that with the release of Titler 2 performance would have increased. It is disappointing at best.

That said, I get real time playback with Titler Pro 1 and 95% of the filters when used in Premiere Pro CS6. If I did not get real time playback in Premiere I would not have anything to say. But, it seems that NB has chosen to put the most effort into Premiere optimization.

If that is not the case, why has nothing been done to address the performance shortcomings of the NB GPU product line within Edius.
Inquiring minds want to know!

[NewBlue_MJ]

Truthfully Jerry, I always recommend that people render their Titler Pro clips no matter what NLE they're using. Rendering adds an extra anti-aliasing pass that tends to make the titles look smoother and cleaner.

As to why you're experiencing faster performance with Titler Pro in Premiere versus Edius, I couldn't say for sure. I can assure you that we don't favor one NLE over another, and we put in as much work on Edius as we do on the other NLEs we support. Perhaps part of the reason for the speed difference is with Premiere being 64-bit while Edius is still 32-bit at the moment.

Either way Jerry, I certainly appreciate your passion for Edius, and I am glad for all the help that you're provided in testing our products. Certainly there is still room for improvement in some areas. I'll see if we can allocate some time to improving performance in Edius soon.

[Jerry]

Thanks for responding Marcus. It isn't only the Titler that isn't realtime, but most of your product line is not realtime despite purchasing GPU enhanced versions.
These perform better in Premiere as well.
Hopefully, you can improve performance fairly quickly. I'll see you at NAB.
Thank again.

[John Lewis]

I dont think its just titler pro though Marcus
Nothing plays RT for more than a few seconds in filters either, why switch off GPU to get better results on products where a premium is paid for to get GPU accelerated products. I run a gtx 690 which cant cope so i guess maybe even the titan is out of the question

[rob stowell]

Having found this thread, I realise I'm not alone :)
Looking for tips running titler pro 3 to speed things up. I'm working with Neo 3 on an HP notebook, Win 7 pro 64 bit, i7 processor, 8GB ram, but only a 512MB gfx card. I managed to get titler pro 1 working ok on a desktop with a little less grunt, but I had other hassles, so I never got used to the workflow.
Glacial is about right for titler 3 on this machine. They play, if at all, so slowly they might as well be stopped. It only takes a moment to render a small piece of the timeline without a title. But a 4 second key takes 30 minutes to render. I can't seem to adjust the length of titles on the timeline at all - maybe I'm not doing it right, but I suspect because the machine can't calculate fast enough to allow me to drag them. (The titles don't turn up in the bin, either- is that how it's supposed to work?)
Someone mentioned turning off the GPU 'accelleration' in Edius - is this a good idea? How do you do it? Are there buffer settings in Edius that might help?
I like the final output, but the workflow isn't a flow so much as a limp :)

[Jerry]

It's a shame you're on NEO. Otherwise, I would recommend Vistitle.

[rob stowell]

Bit late!
Although I've been considering it. Does vistitle not work in Neo?
I'm a little perplexed by Titler Pro's lack of performance- it runs ok in its own window, but as soon as you go back to edius, it's as if there was a fight over GPU resources (which are scarce) while RAM and CPU are hardly utilised.
Shame, as the results are nice - just far too long waiting, and then fine-tuning is ridiculous.

[Jerry]

Nope, no go for Neo and Vistitle.
Performance of New Blue filters and Titler, or the lack there of, has been documented many times on this forum over the last couple of years.
Keep in mind that New Blue products are basically 'cookie cutter' products. It is made to go into several programs. I guess you could call it a 'Jack of all trades and master of none' type of program.
On the other hand, Vistitle is written specifically for Edius, adhering to the SDK.

[rob stowell]

To be fair, titler pro 3 seems to be working nicely now on my desktop work machine, running Edius 7. Not sure how complicated the projects are, and there was a minor slow-down red-line on a lighting effect, but so far so good.
Not sure if I now have to deactivate it on my laptop - hope not, but really it's no loss...

[createmedia]

I have had to turn off NB GPU acceleration it gives memory leakage into the second FX3800 GPU card with Nvida driver 340.52 and latest NB despite Nvidia control panel saying open GL rendering via GPU1. Every time a new NB effect is added and double clicked the memory usage in GPU 2 rises between 3 and 5%.

The implication of turning GPU acceleration off is that a glow effect takes 45 seconds to render with GPU on and 9 minutes without.

It not only does that in Edius but in Premiere Pro CC2014 on the same PC (system 4 in signature).

Latest Nvidia driver 340.84 got muddled up with which GPU it was talking to in the Nvidia control panel trying to allocate GPU1 to open GL (after I clicked apply the drop down flipped to say I had selected GPU2 which I had not) so I went back to 340.52, which doesn't do that.

We have of course two combinations here NB and the GPU driver, who does the finger point to to fix it?

Mike