I have NewBlueFX Titler Pro 7 and installed it. The only issue I have found, so far, is that it will not load within VP17 as an effect or as a media generator. It works fine as a standalone and it works fine in VP15 and 16. I have an open trouble report with NewBlueFx for a fix. So far I have tied everyone one of their suggestions and the issue is still there. I am awaiting the next suggestion or patch. NewBlue has always been good in resolving any issue I had in the past.

The only issue I have found, so far, is that it will not load within VP17 as an effect or as a media generator.

@james-ollick - Not my experience. Loaded fine.

It seems there's a little bit of difference on workflow between TP6 and TP7.

TP7 'forces' you to save every title that is made, while TP6 do not. Probably this workflow 'broke' the versions compatibility.

And due to my frustrating previous 'missing' generated TP6 titles (gone back to default every time I reopened the Vegas project), I saved every TP6 titles back then.

Yes, It appears that Titler Pro 7 'breaks' projects with titles created using Titler Pro 6. However, this is not true. The methodology used with Titler Pro 7 is different to Titler Pro 6. Titler Pro 7's assets, ie its titles, are stored separate from its host's NLE. This makes for a more efficient caching mechanism. In order to migrate a project with titles created with Titler Pro 6 you need to open the first title in your NLE using Titler Pro 7, then systematically save each title with its own unique name to your hard drive (I use a sub folder within my project folder) until you've saved them all. You can then click the green tick at the bottom right hand of the screen to close TP7 down and return to your NLE. If you create all your titles in one go, as I do, the thing to remember with TP7 is that when you create a new title on the timeline it's important to save this with its unique name as soon as possible because, by default TP7 names each new title 'Title'. If you don't, on exit you will be confronted with the task of saving multiple titles, giving each a different name, and this can get tedious.

Another thing that's changed is the concept of Title Templates. As far as multi-title management is concerned this concept has been replaced by the concept of 'Design Sharing' and works in a slightly different way. But that's another story.

@Jack S - Yes, I agree. Without actually stating this, it would seriously appear as if NB have wandered away from what we’ve had up to V6, individual Title creation. It seems as if it’s more directed towards Project Sharing and individual creations to then be Handed-Off to the next Operative. Pity.....

Not sure exactly what corrected the issue. I uninstalled and reinstalled TP7 and VP17 a couple of times. But I have found TP7 works in VP17 when I run VP17 as Administrator. If I do not, it will not work. So, I am a happy TP7 user now.

Now that I have TP7 working in VP17, I tried loading a few of my old titles created in TP versions from 2012 to present created in TP6 and they all work. BCC Continuum Fx also work in the standalone version of TP7.

When searching for lost TP projects in Windows simply search for .nbtitle files on your storage drive.

Yes, It appears that Titler Pro 7 'breaks' projects with titles created using Titler Pro 6. However, this is not true. The methodology used with Titler Pro 7 is different to Titler Pro 6. Titler Pro 7's assets, ie its titles, are stored separate from its host's NLE. This makes for a more efficient caching mechanism. In order to migrate a project with titles created with Titler Pro 6 you need to open the first title in your NLE using Titler Pro 7, then systematically save each title with its own unique name to your hard drive (I use a sub folder within my project folder) until you've saved them all. You can then click the green tick at the bottom right hand of the screen to close TP7 down and return to your NLE. If you create all your titles in one go, as I do, the thing to remember with TP7 is that when you create a new title on the timeline it's important to save this with its unique name as soon as possible because, by default TP7 names each new title 'Title'. If you don't, on exit you will be confronted with the task of saving multiple titles, giving each a different name, and this can get tedious.

Another thing that's changed is the concept of Title Templates. As far as multi-title management is concerned this concept has been replaced by the concept of 'Design Sharing' and works in a slightly different way. But that's another story.

That's a pretty awful user experience... and can be a mountain of work for large projects. Not to mention if you have to open an older project that used Titler Pro 5/6, for any reason.

I'd pass on upgrading specifically to avoid having to do this. The benefits of a the [paid] upgrade aren't worth the trouble I'd have to go through to deal with this.

They should have rolled out an update for TP5/6 to allow users to automate this to a large degree (dialog box with a list of titles, and you get to put the names in and bulk save them, etc.). Apple did something similar when they announced dropping support for CODECs. Their NLEs were updated to off to migrate offending files to a supported CODEC.

Horrible planning, and I'm sure lots of people are going to be caught by this.

Welcome back to the madness! I quit VP at version 13 and TP at version 4. I expected now that they're up to VP17 and TP7 the issues would be solved. But nope! I bought VP17 and I'm leasing TP on their TotalFX360 package that I subscribed to just to get a taste of what's new. TP7 has some SERIOUS issues as discussed above and other issues that I've encountered. I'll be on the phone and computer talking to NB on Monday. So frustrated but, alas, not surprised.

NB Staff Marcus Johnson @newblue-mj is currently in this forum.

https://www.vegascreativesoftware.info/us/forum/hello-from-newbluefx--117644/?page=1