NewBlue Titler products on VP14

Comments

Quitter wrote on 11/19/2016, 3:08 PM

I received it directly from Edward at NewBlueFX
i think it's ok to post the link:
http://www.newbluefx.com/downloads/Magix/NewBlueVegasProComplete-161118.exe

it's called 161118 but the Manager shows 161119

Wovian wrote on 11/19/2016, 4:26 PM

Caleb sent me a link for an updated TP4. So far so good for me.

Skywatcher wrote on 11/20/2016, 2:43 AM

Wovian, can you post the link? I have TP4 and it doesn't work . . .

James

Wovian wrote on 11/20/2016, 4:04 AM

Sure Skywatcher, try this.  Make sure you fully delete all the previous NB stuff first.

www.newbluefx.com/downloads/Windows/Beta/NewBlueTitlerPro4-161027-029.exe

Skywatcher wrote on 11/20/2016, 10:59 PM

Wovian,

It is working perfectly (so far) . . . thank a million . . . I mean a BILLION!!!

Wovian wrote on 11/21/2016, 4:17 AM

Excellent news Skywatcher.

thomas-christoph wrote on 11/23/2016, 11:23 AM

Ich finde es eine Unverschämtheit - ein neues Produkt Vegas Pro 14 wird mit veralteten PlugIns NewBlue Titler 3 verkauft - und dieser funktionierte nur sehr fehlerhaft! Ich habe mir nund den NewBlue Titler 5 gekauft - der funktioniert einwandfrei. Eigentlich müsste man Geld wieder zurückbekommen! Titler 3 - hier kommt eine Fehlermeldung die das Wort "Sony" beinhaltet. Warum? Ganz einfach: Titler 3 wurde entwickelt als noch vegas in Sonyhänden lag - jetzt eine neue Firma - neue Software, aber der Titler 3 will noch auf ein Sonyprodukt zurückgreifen!
Einfach frech so was zu vermarkten.

Grazie wrote on 11/23/2016, 11:32 AM

Just did a Google Translate!

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

thomas-christoph wrote on 11/23/2016, 12:18 PM

I find it an outrage - a new product Vegas Pro 14 is sold with obsolete plug-ins NewBlue Titler 3 - and this worked only very flawlessly! I bought myself the NewBlue Titler 5 - the works perfectly. Actually you would have to get money back! Titler 3 - here comes a error message which includes the word "Sony". Why? Quite simply: Titler 3 was developed as still vegas in Sonyhands - now a new company - new software, but the Titler 3 still wants to resort to a sony product!
Simply naughty what to market

stu-in-pittstown wrote on 11/23/2016, 7:02 PM

I was also having problems when I tried to go from TP4 to TP5.  i am using VP13 on win 10 64 bit.  FInally I have a solution so that now i can use TP5 both as standalone and in VP13.

I followed some of the advice in this forum. 

First I went to \Program Files\Common Files\OFX\Plugins\NewBlueFX and removed the folder and contents therein of TitlerPro2.ofx

To do that I had to go to computer management. Local users and groups, users, administrator and unchecked disabled.  Only then could I delete that folder.

However after rebooting that still did not allow me to run titler pro.

Then I deleted  OFXBridgeB64.dll from C:\Program Files\NewBlueFX\Common and then TP5 worked both as standalone and embedded version ..  so actually I don’t know if the first delete I did actually was necessary but this second one clearly is.

Thanks to all the ideas on the board and your earlier feedback.

The program seems a little slow to load but it does allow me to read all prior veg files that have titler pro segments embedded in them.

I loaded version of 16114-061 of TP5

Have a great Thanksgiving  - I feel much better now  😊

 

michael-scott wrote on 11/27/2016, 4:34 PM

Ok part of the problem is you have people posting different issues in the same thread and so some people are having TP4 problems with VP14 and others like me are having problems just getting the basic TP3pro working that came with VP14 suite.

 

When I run the default installation of titler pro 3 that came bundled with Vegas Pro 14 suite I keep getting these errors left and right.

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

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

 

Additionally, while I have been able to create 1 title, every other time I try to create one I try click 'Library' and the editor locks up waiting to respond. It tries to load them and just gets stuck there.

 

So I can neither create or edit any titles using TP3 and additionally I get those Type or Namespace errors on any video that has a TP3 title in it.

 

 

I have a clean installation of Vegas Pro 14 Suite and installed the NewBlueVegasProSuiteComplete-160915.exe update that the updater pushed on me.

 

HELP please.

 

Windows 10

I7 Skylake

16GB RAM

GTX1080 using 375.95

 

AVsupport wrote on 11/27/2016, 10:49 PM

Well I guess Magix might want to consider upgrading their struggling customers to the latest version of titler5, perhaps a restricted, but hopefully working version. It's crazy having legacy software around that no one wants to support, and when things don't work no one cares.

 

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

xberk wrote on 11/28/2016, 12:10 AM

Granted, NewBlue and Magix did not execute very well on the VP14 bundle. If you want to do something about it:

Contact NewBlueFx support for the latest.  Edward is very good about responding.  He will have the full picture of what you can expect in regards to running TP3 or TP4 in VP14.  In my case, I already had TP3 and wanted to use it with VP14.  Here's the download link that I was told use.

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

it's called 161118 but the Manager shows 161119.  There may be some other update to this by now. I have not checked lately.  It does run, but I don't use NewBlue much so I cannot tell you if it is equal to Version 3 or better .. or what?  Edward will have the answers.  Contact NewBLue support. 

AVsupport wrote on 11/28/2016, 5:01 AM

yes I saw the link above & reinstalled that packaged titler3..stll issues, and using the standalone version with update check suggests no further updates.

this thing is just not running how its supposed to...

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Dexcon wrote on 11/28/2016, 5:49 AM

Having installed the VP14-201 trial a couple of days ago, I was pleased to find that just about everything worked without any adverse effect on VP13.  For example, VP14 didn’t kill AC3 Pro in VP13 or DVDA6 as far as I could see.

NBFX Titler Pro 4 continued to work in VP13, BUT TP4 locked up in VP14. I lodged a ticket with NBFX, and Edward sent me a new build of TP4.  Unfortunately, the installation only installed Quick Edit – there was no access to Title Designer, it not even appearing in any of the menus.  Uninstalling the new version and reinstalling the original July 16 TP4 version resulted in error dialogue boxes appearing when attempting to open TP4 in VP13, VP14 and the stand-alone.  Basically, TP4 had now been killed.  I tried the logout and login process via NBFX’s app manager but with no improvement.  The issue was resolved by deleting TP4 and VP14 and then doing a system restore back to just prior to the VP14 install.  TP4 now works perfectly again.

I doubt if I will move on to VP14, but f I do, it will be with the Edit version to avoid the NBFX Titler problems.  But if I do go with VP14, I’ll have to rely on BCC10 Title Studio for titling.  Title Studio is very, very good, but not as good with handling eps images as TP4 is.

Dexcon wrote on 11/29/2016, 5:41 AM

Update to my previous post just above ...

I bought VP14 Edit today and, to my surprise, NBFX Titler Pro 4 works in VP14 Edit.  TP4 didn't work in VP14 Trial, but does work in VP14 Edit.  Yay!  All is good with the world again.

AVsupport wrote on 12/8/2016, 3:10 AM

Posted this in the NewBlueFX forum, a couple of weeks back:

https://www.newbluefx.com/forum/products/vegas-pro-14-and-packaged-titler-express-pro

"As you're probable acutely aware, Titler Express Pro, which is bundled with VP14, is not working since the transfer of ownership to Magix.

Titler Express PRO shows up as Version 3, which is now 2 versions behind the current Titler Version 5, and I believe a legacy product which is no longer supported (you call it that in your upgrade offer). Now, why would NewBlueFX want to offer a broken product to their potential customers with no support? Wouldn't it be much better to offer a current/supported version, with restricted functionality (EXPRESS), so that potential customers can experience the product and then upgrade as needed?

Releasing an old broken 'PRO' product into the wild is like buying off food at the markets and trying to cook it up without making everybody sick, it simply doesn't work.

I hope you can resolve this issue with the big bunch of frustrated Vegas Pro customers. Thanks for listening"

- so far, no respose. maybe someone at Magix can help this along?

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Tchak wrote on 12/9/2016, 9:12 AM

- so far, no respose. maybe someone at Magix can help this along?

It looks like that forum has very little activity from NBFX. In one of my support emails from Edward earlier this week when I was having problems with the newest update, there was a reference to upgrade to TP 5.

The current version of Titler Pro is Titler Pro 5. If you upgrade to Titler Pro 5, you will have access to all the templates and be able to use the Title Designer which would let you change fonts and anything else related to the titles.

For those looking for a help file for the edit screen. He gave me this:

Here's a page that talks about the "QuickEdit" screen:

https://www.newbluefx.com/support/help-files/titler-pro-4/quick-edit

Why would anyone purchase the newest version if the bundled version has so many problems?

diverG wrote on 12/9/2016, 3:52 PM

If you have purchased/upgraded to NBT5 and it does not function, raise a ticket directly with NB.  Explain carefully what is not working/crashing.  If they cannot fix it immediatly you may well be offered a NBT4 licence whilst they sort NBT5 out.  Take it.  You can work in 4 without being a paying beta tester.

My experience is that NBTP3 & NBTP4 work fine. A little more development seems to required before NBT5 is OK on all platforms.  NBTP4*****1607-142.exe has a different feel to NBT****16118-032.exe.  In my case this later file failed to load the libraries. 

Last changed by diverG on 12/9/2016, 3:53 PM, changed a total of 1 times.

Sys 1 Gig Z370-HD3, i7 8086K @ 5.0 Ghz 16gb ram, 250gb SSD, 2x2Tb hd,  GTX 1060 6Gb Vegas 14 & 16 plus Edius 8WG Win 10 (1809) BMIP4k video out. (PS 650W)

Sys 2 Gig Z170-HD3, i7 6700K @ 3.8Ghz 16gb ram, 250gb SSD, 2x2Tb, hdd GTX 750ti,  Vegas 14 & 16 plus Edius 8WG Win 10 (1809) BMIP4k video out. (PS 650W)

Sys 3 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP14 & 15 via humble bundle. Plus Edius 8WG

 

AVsupport wrote on 12/9/2016, 5:52 PM

Why would anyone purchase the newest version if the bundled version has so many problems?

My word! Wrong strategy from where I am sitting..Given the NBT5 full version was 'on special' for half price U$~150 a moment ago, which is not too dissimilar to what the VP14 upgrade was. Please don't expect customers accepting being forced into upgrade by not providing a working version in the first place.

For example: Click on 'Help' in the packaged TitlerStandalone and you get to 'Page not found'. great start. not.

http://www.newbluefx.com/helpfiles/redirect.php?collection=VegasProComplete&id=2&language=EN&platform=Win

There's no way I will upgrade to TP5 unless I see a functional 'Express' version first. Please sort it out, don't finger point to the other side

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

stevestemplates wrote on 3/14/2017, 8:48 PM

I remember many years ago...maybe Vegas 10 or 11, when NewBlue was first introduced with Vegas. And back then it never worked. So I never used NewBlue. Now with VP 14, I noticed that it comes with Vegas? I have not accurately loaded it into my computer yet...or at least I have it downloaded but not activated. After reading all the problems everyone else is having with this NewBlue product...I'm thinking maybe yet again, I have to walk away from using it with Vegas. Any thoughts or any success stories using NewBlue Titler Express with Vegas? Please let me know. It's like the holy grail Ive been wanting a better titler to work with directly in Vegas...oh well may not see it yet. Please comment.

AVsupport wrote on 3/14/2017, 9:11 PM

They should call it OldBlue Titler Turtle actually. That's what it is rather. broken. sad.

Last changed by AVsupport on 3/14/2017, 9:12 PM, changed a total of 1 times.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

skyml wrote on 3/14/2017, 9:37 PM

I remember many years ago...maybe Vegas 10 or 11, when NewBlue was first introduced with Vegas. And back then it never worked. So I never used NewBlue. Now with VP 14, I noticed that it comes with Vegas? I have not accurately loaded it into my computer yet...or at least I have it downloaded but not activated. After reading all the problems everyone else is having with this NewBlue product...I'm thinking maybe yet again, I have to walk away from using it with Vegas. Any thoughts or any success stories using NewBlue Titler Express with Vegas? Please let me know. It's like the holy grail Ive been wanting a better titler to work with directly in Vegas...oh well may not see it yet. Please comment.


I've been using NewBlue FX Titler Pro since version 1. Yes, here and there I had some hiccups with it but NewBlueFX always sorted it out. The problem I had moving to VP14 was that the included TitlerPro conflicted with my newer (full) version. Am very happy with version 5 and use it on every video I do. NBFX is very good at resolving issues with all their products.

AVsupport wrote on 3/14/2017, 10:11 PM

NewBlue should have a 'lite' but current Version?5 packaged and not an old broken unsupported V3 product. That's bad for both Magix and NewBlue.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.