VEGAS Pro 17 - New Blue Titler Pro Express issue

doug-small wrote on 9/11/2020, 5:29 PM

Any suggestions to resolve are really appreciated.

Observations:

  • I get a large red "X" (and the letters "FX") when I try adding a title to my Vegas Pro 17 project. The title I created is there, but these other artifacts are also added (as if I'm software/plugin isn't licensed or activated). Obviously, I can't utilize this add-in until the artifacts are removed.
  • A NewBlueFX (separate window) opens and I'm logged in, window displays "Current" next to "Vegas Pro Complete version 3.0.160926" so I assume this means I'm licensed and activated. Am I missing something? (BTW I believe this add-in came with Vegas Pro 17 when I purchased).
  • In Vegas Pro 17, the plug-in is named "NewBlue Titler Pro Express - OpenFX". Wasn't sure what that OpenFX implied or if I have some customized version of New Blue. But mentioning in case it helps.

Attempts to resolve

  • I have tried resetting my NewBlueFX.com password and restarting Vegas Pro 17 (still have issue). I've contacted NewBlue support to see if they have any suggestions.

I also am getting these auto-save errors (unclear if related):

C:\Users\Doug\AppData\Local\Temp\scr0.cs(20) : The type or namespace name 'Vegas' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Doug\AppData\Local\Temp\scr1.cs(3) : The type or namespace name 'Sony' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Doug\AppData\Local\Temp\scr1.cs(8) : The type or namespace name 'Vegas' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Doug\AppData\Local\Temp\scr1.cs(20) : The type or namespace name 'Vegas' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Doug\AppData\Local\Temp\scr1.cs(3) : The type or namespace name 'Sony' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Doug\AppData\Local\Temp\scr1.cs(8) : The type or namespace name 'Vegas' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Doug\AppData\Local\Temp\scr1.cs(20) : The type or namespace name 'Vegas' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Doug\AppData\Local\Temp\scr1.cs(3) : The type or namespace name 'Sony' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Doug\AppData\Local\Temp\scr1.cs(8) : The type or namespace name 'Vegas' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\Doug\AppData\Local\Temp\scr1.cs(20) : The type or namespace name 'Vegas' could not be found (are you missing a using directive or an assembly reference?)

 

Comments

jetdv wrote on 9/11/2020, 6:39 PM

Vegas Pro Complete was a free bundle with VEGAS Pro 14. That bundle was not included in later versions of VEGAS Pro so it will get a watermark in versions 15, 16, 17, and 18.

As for the error messages with the script, that must have been an extremely old installer. Please try the newest installer (which is nearly 4 years old) but you'll still get a watermark.

http://www.newbluefx.com/downloads/Magix/NewBlueVegasProComplete-161118.exe

To remove the watermarks, log in at www.newbluefx.com/login and upgrade to the current version of Titler Pro.

 

doug-small wrote on 9/17/2020, 5:26 AM

Thanks for the information @jetdv. NewBlue support confirmed everything you said.

I'd assumed the plug-ins would carry into new versions of Vegas but that's not the case. Makes me hesitant to purchase another NewBlue plugin, which may (or will) only watermark the next time I decide to upgrade Vegas Pro. Perhaps this was just a one-time sales/product blunder with VP14 (introducing plug-ins that aren't forward usable).

Dexcon wrote on 9/17/2020, 5:42 AM

@doug-small  ... Third party plugins bundled with a particular version of Vegas Pro often are licensed locked to that version and thus don't work in later Vegas Pro versions. If they do, consider it a bonus. In a way, consider the bundled plug-ins as low cost teasers which may result in a sale of the full retail product.

However, purchasing the full retail product from a third party company such as NewBlueFX should usually be expected to work in later versions of Vegas Pro as they are not license locked to any particular release.

An exception did occur last year with the release of Vegas Pro 17 for those with FXHome's Ignite plugin package. Ignite had to be updated to meet a coding change in VP17; however, only those with a then current Ignite subscription had access to the Ignite update.

Dell Alienware Aurora 11

Windows 10 Home

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: 1TB M.2 PCIe NVMe SSD

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

E & F drives: 2 x 2TB Barracuda HDDs 2.5"

 

doug-small wrote on 9/17/2020, 5:50 AM

@Dexcon - thanks for the explanation, "teaser" explanation makes sense and glad to know that full retail version NewBluew Pro Titler should theoretically work with future versions. Appreciate the response.

jetdv wrote on 9/17/2020, 8:32 AM

I will say that all current "bundles" provided by NewBlue are full retail products so they will not expire in future versions of Vegas. And, in reality, the Vegas 14 bundles and Titler Pro 1 included with Vegas Pro 11/12 are really the only bundles that have expired in later versions.