Newblue Titler Pro 6 takes excessive CPU load when idle.

Erkki wrote on 3/9/2023, 11:27 PM

When adding NewBlue Titler event to timeline and closing titler... Titler stays background but takes 100% of single core capacity. If it is killed, load obviously drops.

Expected behavior would be 0% titler load when it is not needed.

Picture below is from situation when one titler event has been added to timeline and titler was closed and then computer was idle (no user actions with mouse or keyboard).

After taking picture, titler process was terminated. Vegas itself was responsive. Titler clip preview had text "Error: The Titler process failed..."

Vegas version was latest 326 build. Titler version.. don't know but it is the one that came with Vegas.

Comments

Dr Zen wrote on 3/10/2023, 2:00 AM

I am a Titler Pro 7 user. I do remember lots of strange behaviour with TP6. From what I could work out, all problems are related to the Caching functions in Titler Pro 6. Older versions of Titler Pro had multiple caching settings in the Menus. Each time you created a new TP event, it would pre-render / cache everything to make it play easier while editing. The problem that I discovered, was that Titler Pro would go crazy and keep pre-rendering stuff in the background - even older projects that you weren't being used in the current project. This would cause CPU resources to be overtaken with Titler Pro crap.

What I did to fix problem:
1. Turn off all (most) of the caching modes in menus. When Titler Pro 7 was released, they removed all these settings and automated everything. I can't remember which menu item these settings are located in. Just open every menu / sub-menu and you'll find them.
2. The No.1 thing I discovered which helped the most, was to delete everything in the Titler Pro temporary caching folder. My guess is that the files in this folder get corrupted somehow, which makes TP6 think they are missing, which then starts this never ending caching that hogs all CPU resources.
You should find the Titler Pro cache here:
C:\Users\**USERNAME**\AppData\Local\Temp\Titler Pro

Something to note. In Titler Pro 7, the new default cache folder is now located here instead:
C:\Users\**USERNAME**\AppData\Roaming\NewBlue\Titler\Cache
I mention this to you, in case you have this folder location as well.

One last thing:
I love using Titler Pro, however NewBlue always does things in a really weird way, which can cause bizarre and infuriating problems! If you had even older versions of Titler Pro or Titler EX on your computer before TP6, old parts of those programs could be causing bugs in TP6. If this has happened, use REVO uninstaller to remove ALL NewBlue stuff and old folders, then do a clean install of TP6.

Regards, Derek.

set wrote on 3/10/2023, 2:33 AM

OMG.

Quick Question: is it safe to empty all the contents in these folders even though the projects are still on going?

jetdv wrote on 3/10/2023, 7:28 AM

@set, my suggestion would always be to MOVE the files somewhere else. Then test to see if the project is still fine. If not, move them back. If they are, then delete them.

set wrote on 3/24/2023, 2:32 AM

@set, my suggestion would always be to MOVE the files somewhere else. Then test to see if the project is still fine. If not, move them back. If they are, then delete them.

Just tried it today (to be safe) and yes, no trouble on removing the contents of above mentioned folders.

EDIT ADD: better double check the texts especially if you have a prerendered titles. It seems flickering. To be safe, better uncheck the prerender process of the titles. I think this can only done in TP6. In TP7, you are forced to prerender the titles.