NewBlue Starter Pack & Vegas Pro 13

PJCHATMAN wrote on 6/3/2014, 8:48 PM
I have Sony Vegas Pro 10, 11, 12, & 13. Though only 12 and 13 currently installed on the same machine.
Vegas Pro 11 or 12 came with NewBlueFX Titler Pro 1 along with the NewBlueFX Start Pack. All of this was with one of those versions. As of v12 everything worked fine, no issue with activation.

Then I upgraded to v13; I didn't uninstall v12 because I wanted to get comfortable enough with v13 to keep it on my laptop. Well, "Activating" NewBlueFX Essentials VI was tricky. And I figured since I was able to use BorisFX RED, and BCC without having to re-activate them in v13, the same was true for NewBlueFX products.

Well, I was shocked to learn that BOTH Pro Titler 1 and Starter Pack are asking me activate within v13. PLUS the Activate button doesn't respond to the serial I used to Activate with v12. (The serial# used for Titler Pro also activated the Starter Pack, if memory serves.) But there's more...

Now after installing v13, only the OpenFX versions of NewBlueFX work with v12. Not that NewBlueFX is critical, but I assumed if have purchased them for v12 then they all should work for v13, without a new purchase. Titler Pro v1 and Starter Pack v1 are giving watermarks, specifically ST on v13 projects.

What is going on?

Comments

Dexcon wrote on 6/3/2014, 9:14 PM
The TP1 issue was covered in the following lengthy thread:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=891600&Replies=88

In a nutshell. TP1 (and thus the starter pack) is licensed only for VP11 and VP12. To get TP1 to activate in VP13, you will need to purchase a TP1 retail license for TP1 from NewBlue. Without that license, TP1 and the starter pack will appear with the watermark in VP13. NBFX did have an intro price on the TP1 retail licence, but that offer period might be over as it may have only been on offer during SCS's upgrade to VP13 intro offer period - check with NBFX anyway.

I'm not sure what has happened with your other NB FXs as functionality in VP12 remained in my case when I installed VP13. You could try reinstalling the NBFX and select the versions of the FX you want at the host page of the install process. You shouldn't need to uninstall the FX prior to doing this - overlaying the install should work.

Cheers

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.3, BCC 2026, Mocha Pro 2026, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11 25H2

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

jetdv wrote on 6/4/2014, 1:27 PM
Yes, Titler Pro 1 (and the bundled Starter Pack) will have a watermark in Vegas Pro 13. As was mentioned, this has been discussed several times but we can discuss it again.

There are two options available:

1. Upgrade to Titler Pro 3

2. Upgrade to the retail version of Titler Pro 1 (special pricing is available)

For either option, just contact support at newblueinc.com
PJCHATMAN wrote on 6/5/2014, 1:09 PM
I do not spend a lot time, as most, on internet forums. So I would not have known about these discussions.
That being said. It is what I figured, but I just wanted to know for certain that I was right. Yeah, since I have BorisFX's RED, BLUE, and BCC, those combined can do everything and more than TP 1, 2, & 3.

Anywhoo, thanks for wasting your time with me (That was sarcasm. Most would just send me a private message telling me to search for the answer and then proceed to delete my thread. So really, thank you.).

PaulJC

PS. Since I had v12 and v13 running at the same time, this may explain why I saw the watermark in 12. But, no biggie. C'ya!
CyberOtter wrote on 8/26/2014, 7:24 AM
Hey.

@edward : I got kind of the same issue here.
I don't understand what's going on :

- I have Sony Vegas Pro 13 up to date.
- I do have Titler Pro 3 registered, and up to date (i clicked "help" -> Check for updates" )
BUT
my Newblue Starter pack still appears with the NBFX watermark.

I tried to go to the NBFX website, but since i got Newblue Titler 3 from the SVP13 bundle, i can't log in with a "client ID"...hence no newblue support for me.

Any idea ?

thx
Stringer wrote on 8/26/2014, 9:11 AM
Did you uninstall earlier vervions of Titler Pro before installing ver 3?
jetdv wrote on 8/26/2014, 1:24 PM
If the most current version of Titler Pro 3 is installed and activated, Starter Pack will be as well. If you are still seeing issues, please send an e-mail to support at newblueinc.com so we can figure out what is happening. As of today, this is the current build:

http://www.newbluefx.com/downloads/Windows/NewBlueTitlerProForWindowsSetup30-140725.exe

You do not have to log into our website to send an e-mail to support. If you are having issues logging into the website, support can assist you with that as well.
CyberOtter wrote on 8/27/2014, 3:16 AM
Well thats's odd...

My Titler Pro kept saying that "the latest version is installed". But after a closer look, the link you just gave me says "build 140725" (July ?) whereas mine was saying April...

I think the updates checking module might be broken...

Anyways, i did uninstall and reinstall the latest build with the link you gave and everything is now how it should be, with no watermarking at all.

Thanks Ed
NormanPCN wrote on 8/27/2014, 9:38 AM
I think the updates checking module might be broken...

I have noticed that in TP3 for a while now. I occasionally look here for current builds.
https://newbluefx.com/downloads