Comments

Grazie wrote on 9/3/2019, 12:16 PM

@Corkey - Not been my experience. I have other issues with it, but screwing up my System isn’t one of them.

james-ollick wrote on 9/3/2019, 12:21 PM

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.

Last changed by james-ollick on 9/3/2019, 12:22 PM, changed a total of 1 times.

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 7900 XTX 24GB graphics card, Corsair 1000 watt power supply. Windows 11.

VP 21 BCC 2024 Boris FX Continuum Complete, Titler Pro v7. Various NewBlue effects.

Grazie wrote on 9/3/2019, 12:39 PM

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.

set wrote on 9/3/2019, 6:29 PM

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.

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

Jack S wrote on 9/4/2019, 10:55 AM

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.

My system
Genshin Infinity Gaming PC
Motherboard Gigabyte H610M H: m-ATX w/, USB 3.2, 1 x M.2
Power Supply Corsair RM750X
Intel Core i7-13700K - 16-Core [8P @ 3.4GHz-5.4GHz / 8E @ 2.50GHz-4.20GHz]
30MB Cache + UHD Graphics, Ultimate OC Compatible
Case Fan 4 x CyberPowerPC Hyperloop 120mm ARGB & PWM Fan Kit
CPU Fan CyberPowerPC Master Liquid LITE 360 ARGB AIO Liquid Cooler, Ultimate OC Compatible
Memory 32GB (2 x 16GB) DDR5/5200MHz Corsair Vengeance RGB
MSI GeForce RTX 4060 Ti 8GB - Ray Tracing Technology, DX12, VR Ready, HDMI, DP
System drive 1TB WD Black SN770 M.2 NVMe PCIe SSD - 5150MB/s Read & 4900MB/s Write
Storage 2 x 2TB Seagate BarraCuda SATA-III 6.0Gb/s 7200RPM
Windows 11 Home (x64)
Monitors
Generic Monitor (PHL 222V8) connected to GeForce RTX 4060 Ti
Generic Monitor (SAMSUNG) connected to iGPU

Camcorder
SONY Handycam HDR-XR550VE

Grazie wrote on 9/4/2019, 11:12 AM

@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.....

james-ollick wrote on 9/4/2019, 7:10 PM

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.

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 7900 XTX 24GB graphics card, Corsair 1000 watt power supply. Windows 11.

VP 21 BCC 2024 Boris FX Continuum Complete, Titler Pro v7. Various NewBlue effects.

james-ollick wrote on 9/4/2019, 7:40 PM

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.

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 64GB Corsair Vengeance RGB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 7900 XTX 24GB graphics card, Corsair 1000 watt power supply. Windows 11.

VP 21 BCC 2024 Boris FX Continuum Complete, Titler Pro v7. Various NewBlue effects.

Former user wrote on 9/5/2019, 6:17 AM

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.

 

RoadWarriorRadMan wrote on 12/8/2019, 7:32 PM

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.

set wrote on 12/8/2019, 9:11 PM

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

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

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

newblue-mj wrote on 12/10/2019, 2:18 PM

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.

Thanks @set for the head's up.

@RoadWarriorRadMan ,

I'm sorry to hear that you're having trouble with Titler Pro 7. Can you tell me a little more about what's happening?