Another experiment with New Blue workflow to avoid crashes

VEGAS Pro

Another experiment with New Blue workflow to avoid crashes

Posted by Al Bergstein on January 23, 2012 at 1:31 pm

On Sunday, I edited a new timeline. After editing for a few hours, with no crashes, I needed to do some titling and dropped in a New Blue title event. While designing it I experienced a crash of Vegas. I sent it in. I then reopened and had crashes every time I tried to work with New Blue and this timeline, even when I dropped it onto a new track. So I tried something new, and it seems to work. I’ll pass this along.

I decided to try building my New Blue effects on a new project, and then rendered it out and added the rendered bit back into my existing timeline. It worked! So why is this?

I have been plagued by N.B. crashing every timeline I create with it, when other footage is present. As of yesterday, I am now opening a new project from now on, and rendering it out to MXF, which is what I usually shoot, with some mov from my 7D sometimes added in.

If you are experiencing the never ending crashes of New Blue with Vegas 11, you might try this new way to do your workflow. Adding the rendered titles back in has been no problem whatsoever. But it is absurd as a solution long term. Anyone else finding that this is a needed change?

PS. I do like the turn around the fixes are getting by Sony. These quick version updates, while possibly inducing a problem, are obviously coming ‘fast and furious” and show an increased desire to get bugs fixed and back to the community quickly.

Al

Al Bergstein replied 14 years, 3 months ago 7 Members · 22 Replies
22 Replies

Edward Troxel
January 23, 2012 at 5:54 pm

I’ve not seen any particular issues when adding a title on the timeline with other footage and would appreciate knowing more about your system (OS, video card, video driver), your version of Vegas, which build of Titler is installed, and details about your project so the issue could be duplicated. The easiest way to do that would be for you to start a help ticket at newbluefx.com.

Edward Troxel
Steve Rhoden
January 23, 2012 at 7:00 pm

I grabbed Newblue Titler when it just arrived. But had
to take it out of my workflow for the time being, due to
several issues i cant bother getting into right now.

From i read the first press release of this new product i was
like WOW, this is a long awaited plugin. But when i saw that
its gonna be fully GPU dependent i knew that there
was gonna be issues for several editors….etc.

Steve Rhoden
(Cow Leader)
Film Maker
Filmex Creative Media.
1-876-832-4956
https://filmex-creative-media.blogspot.com/
Al Bergstein
January 23, 2012 at 8:33 pm

Ed, I just got out of a client meeting. I’ll pull that info together for you later today. In fact, I’ll try and duplicate the crash(es) and send you the crash dump directly. I’ve forwarded them onto Sony, they should have them in their internal developer bug report db.

Al
Al Bergstein
January 23, 2012 at 9:03 pm

Well, Ed, that didn’t take long. I just went into my timeline, pulled up New Blue and did a title with an animation. I’ve pasted my crash dump info below. I hope that I’ve included enough information. I didn’t know if you wanted this posted here, or sent to your email, but I couldn’t find an email listing under your profile, so I assume this is ok. If not, feel free to delete the post and copy it off. Hope this helps! I’d prefer not to have to start a new project for every titling effect! If there is something in particular I need to change in my system, like if it’s *srongly recommended* to get an advanced CUDA card, rather than the ATI card, then I’ll do it. But to be clear, I was experiencing an inordinate amount of crashes with nVidea, and these new blue crashes are so far the only ones I’ve encountered in over a week of editing with the ATI card.

Also, my system is extremely stable, *other than this issue*. No blue screens, crashing of any other sort.

The key statement is at the bottom, “unamanaged exception”. This is what I always seem to get.

So the overview of my system is as follows. While I no longer am using nVidea (due to the amount of crashes that were seemingly video related issues), I’ve moved back to an ATI 1 GB card.

I am running two internal drives, both have lots of free space on them. Vegas is on C: drive along with the OS.

Project files are stored on F: also internal 1TB. Lots of free space.
Original video files are stored on X: which is a 2 TB drive, RAID 1.
This particular timeline is working with both Canon 7D MOV footage, and AVCHD footage shot on a HMC150.
7D Streams example:
Video: 00:00:22.923, 29.970 fps progressive, 1920x1080x12, AVC
Audio: 00:00:22.923, 48,000 Hz, Stereo, PCM
Streams
Video: 00:00:36.537, 29.970 fps progressive, 1920x1080x12, AVC
Audio: 00:00:36.537, 48,000 Hz, Stereo, Dolby AC-3

Project Properties: Custom (1920×1080, 29.970 fps)

OS Name Microsoft Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name AL-DELL-DESKTOP
System Manufacturer Dell Inc.
System Model Studio XPS 8100
System Type x64-based PC
Processor Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz, 2934 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Dell Inc. A05, 7/8/2010
SMBIOS Version 2.6
Windows Directory C:Windows
System Directory C:Windowssystem32
Boot Device DeviceHarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = “6.1.7601.17514”
User Name Al-DELL-DESKTOPAl
Time Zone Pacific Standard Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.96 GB
Available Physical Memory 4.11 GB
Total Virtual Memory 15.9 GB
Available Virtual Memory 10.9 GB
Page File Space 7.96 GB
Page File C:pagefile.sys

Here’s the Perfmon report on the graphics card:

AdapterCompatibility ATI Technologies Inc.
AdapterDACType Internal DAC(400MHz)
AdapterRAM 1073741824
Availability 3
ConfigManagerErrorCode 0
CurrentBitsPerPixel 32
CurrentHorizontalResolution 1920
CurrentNumberOfColors 4294967296
CurrentNumberOfColumns 0
CurrentNumberOfRows 0
CurrentRefreshRate 60
CurrentScanMode 4
CurrentVerticalResolution 1080
Description ATI Radeon HD 5670
DitherType 0
DriverDate 20100517000000.000000-000
DriverVersion 8.740.0.0
InfFilename oem82.inf
InfSection ati2mtag_Evergreen
InstalledDisplayDrivers aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
MaxRefreshRate 75
MinRefreshRate 50
Monochrome 0
Name ATI Radeon HD 5670
VideoArchitecture 5
VideoMemoryType 2
VideoModeDescription 1920 x 1080 x 4294967296 colors
VideoProcessor ATI display adapter (0x68D8)

___________________________________________________________________
CRASH DUMP – Vegas 11.0 (Build 521 but it could be any of the last 11.0 builds. It’s happened since I upgraded).

File: C:UsersAlAppDataLocalSonyVegas Pro11.0gpu_video_x64.log
File: C:UsersAlAppDataLocalSonyVegas Pro11.0dx_video_grovel_x64.log
File: C:UsersAlAppDataLocalSonyVegas Pro11.0svfx_video_grovel_x64.log
File: C:UsersAlAppDataLocalSonyVegas Pro11.0dx_grovel_x64.log
File: C:UsersAlAppDataLocalSonyVegas Pro11.0vst_grovel.log
File: X:video raw footageCentrum_explorations3 Vegas Project Filecentrum explorations V3.veg

Problem Description
Application Name: Vegas Pro
Application Version: Version 11.0 (Build 521) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:Program FilesCommon FilesOFXPluginsNewBlueTitlerPro.ofx.bundleContentsWin64TitlerPro.ofx
Fault Address: 0x000000003466238B
Fault Offset: 0x000000000000238B

Fault Process Details
Process Path: C:Program FilesSonyVegas Pro 11.0vegas110.exe
Process Version: Version 11.0 (Build 521) 64-bit
Process Description: Vegas Pro
Process Image Date: 2012-01-17 (Tue Jan 17) 00:51:16

Al
Mike Hinkel
January 23, 2012 at 9:27 pm

My New Blue Problems were fixed with the beta update of the titler. However, other third-party plug-ins do not play nice with it. When trying to do a New Blue title followed by a Boris BCC 3D extruded text event it was crash city. I ended up having to render each separately and then putting it to the project. I wouldn’t know how to act if the new and improved actually went as smooth as it should.
Frank Stevn
January 24, 2012 at 3:25 am

My Vegas Pro 11 crashes when try to use NewBlue Titler Pro.

I submitted a ticket to https://www.newbluefx.com back in October 2011.

The last answer of NewBlueFX Customer Support:

Tuesday, 01 November 2011 08:49:01 “I have sent the logs to the developers. When I hear something from them, I will definitely let you know.”

That’s all!
James Houghtaling
January 24, 2012 at 4:49 am

As of last weekend I had at least 10 crashes in a row trying to insert a title into the beginning of a 5 minute project timeline. In almost every crash I got the option to submit a full report to Sony. On a couple crashes it went directly to desktop. the crashes happened as soon as I tried to edit the style of the title. I gave up and used the title in its default font. It was just a fun project so it didn’t matter. I’m using Vegas 64 build 521 and the most recent version of NB titler (which as I recall you can’t tell which version it is until you download it) I think a version number and release notes are the industry standard – maybe I just missed that but I do recall others complain about the lack of a version number on the download page.

—————
My Hardware:
Core i7 2.67GHz; Nvidia GTX580, 12 gig RAM.

My Software:
Vegas Pro V11 with Boris Continuum Complete 7, VASST Ultimate S; Bluff Titler; AE5; PhotoPaint and other stuff.
Edward Troxel
January 24, 2012 at 1:53 pm

I really need you to start a help ticket at newbluefx.com so I can help you properly. The crash dump doesn’t really help a lot but if you start a help ticket then I can ask the proper questions and get you to try other things.

Edward Troxel
Edward Troxel
January 24, 2012 at 1:55 pm

Steve, the same goes for you. If you start a help ticket then I can work with you to figure out what might be happening and also to give you some things to try.

Edward Troxel
Edward Troxel
January 24, 2012 at 2:02 pm

If you go to the Titler GUI and go to Help – About, it will tell you the version/build number. The current build as of today is 111213. I do realize that if the Titler GUI never loads, it makes it real hard to get to the build number.

Over the past couple of months we’ve learned a lot about issues and have found that a large percentage of them are related to the video driver installed. As of today, here’s the current recommendation:

nVidia: use the 2.90.53 beta driver
ATI: use Catalyst version 11.10 or 11.11 (Catalyst 11.12 seems to have some issues)

There have been MANY cases where simply updating the video driver eliminated the Titler Pro issues that people were seeing.

Edward Troxel

Page 1 of 3

1 2 3 →

Reply to this Discussion! Login or Sign Up

Creative Communities of the World Forums