WARNING new blue "update" corrupts previous titles

violet wrote on 4/30/2012, 11:31 PM

I installed the so called update and loaded a project in which there is custom kerning and spacing. The update moved the position of the text on the screen, the kerning and spacing, plus used a different font. Some other text in the same project remained OK.

I uninstalled NB titler and installed the original version that came with Vegas. The text that was screwed up is no longer. It appears correctly with all the custom settings.

So for those having no problem with the update try loading a project with some complex text done in the first version and see if it is OK. Like I said the straight text was OK only text that had been customised was corrupted.

Comments

diverG wrote on 5/1/2012, 11:08 AM

Did you update in response to an email from NBT or from the 'about' window within NBT?

If from the latter you would have noted that the installed version ended ****402.

The text in the window advised Vegas Users not to update.

The emails we received were somewhat misleading. I'm sure NBT acted in good faith but they must try harder.

NicolSD wrote on 5/1/2012, 12:43 PM

The latest version that can plug in other Windows programs such as AE and Premiere Pro does have problems. We are supposed to stick with the previous version. NB sent two emails on Friday. The second message said to disregard the earlier one.

Former user wrote on 5/1/2012, 12:49 PM

I actually installed the "new" version, which I then uninstalled in favor of the Vegas version (from the updated email).

I've actually uninstalled and reinstalled the Vegas version (the latest version) which is now crashing any time I open an instance of it.

So, it seems that, on one of my systems at least, NB Titler Pro is now plugin non-grata. Sigh.

I like the product, when it's working. I'd roll back the vegas beta, but when push comes to shove, I can do titles a few ways, but Vegas is my primary editor, so I'd like to help keep that stable as a first priority.

jetdv wrote on 5/1/2012, 12:54 PM

It does NOT corrupt any previous files. If you load a VEG files, the titles will be reverted back to plain "Enter Text". If you then exit Vegas, install build 120402, and open that same VEG file, everything will be back to normal.

jetdv wrote on 5/1/2012, 12:55 PM

Andreas, start a help ticket at newbluefx.com so we can see what might be happening on your system.

Leee wrote on 5/1/2012, 1:03 PM

diverG:
The emails we received were somewhat misleading. I'm sure NBT acted in good faith but they must try harder.

Agreed. I'm sure the folks at NewBlue are working to fix all the things needing to be fixed (ahem...like clearly labeling version numbers for EACH and every plugin on their website and within the downloadable files.) But I think in order to gain back the massive loss of their customers' confidence the key words in your message are "Try Harder". (you know, like Avis?)

diverG wrote on 5/1/2012, 4:03 PM

@ Lee

Once I have loaded NBT.exe I add an additional suffix xxxx.exe.402.
This enables me to step back correctly if necessary.

My side of the pond Avis did not spring to mind. More like my old school reports circa 1950.

Maybe we could run a book on whether SCS will have a stable V11 before NBT solve their problems. From experience I expect VP12 will arrive first.

violet wrote on 5/1/2012, 9:01 PM

@ jetdv
The text that is being corrupted is text where you change the default settings to achieve a specific look. Default text appears OK. Uninstalling the latest update then installing the original release the text reverts to how it was originally.

So it seems that the update does not read correctly all the settings for the titler in the*.veg file correctly. Nor does it load previously saved *.nbtitle files created from the original release correctly.

To me that seems to justify "corrupts" previous non default titler files.

As fo NB they don't even put version details in the metadata of the dynamic link libraries. A basic programming task that should be the first thing you do when changing the code.

pat s wrote on 5/1/2012, 9:14 PM

@ violet Quote:

"...A basic programming task that should be the first thing you do when changing the code."

Couldn't agree more. One of my pet peeves with some programmers! Sloppy code =Job security, I guess.