Crash, Crash, CRASH!

Steve Mann wrote on 11/28/2011, 8:43 AM

If you don't do RAM preview, (CTRL-B on a region), then find the minimum RAM preview setting that works for you. In tests done by another forum user (Jerry), 1Gb seems to be the sweet size.
His test is here:
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=787923

Also, I know that the "loop on region" uses preview RAM. The first pass through the region will be slow, and the frame rate improves with each pass. How well it improves is directly tied to the amount of Preview AM you have set aside.

RAM preview size seems to be a black art that likely predates the current SCS programmers. Some features seem to use some of the preview RAM for scratchpad use, which is why you need some preview RAM set aside. But, some users have found a setting of zero helps their situation. The mystery deepens.

Rv6tc wrote on 11/28/2011, 11:08 AM

I upgraded to the Nvidia beta driver and I've had much better stability. I haven't been editing as much, but what I have done has been crash-free.

(crosses fingers)

Cross-Bonnes wrote on 11/30/2011, 1:23 AM

On my first post I stated that my Vegas Pro 11 was crashing multiple times when editing, especially if I was using the NewBlue Titler pulggin. I would like to say, that is no longer the case. I followed the advice of quite a few people in here and updated my video drivers. Vegas Pro 11 is now stable as a rock. I'm able to edit with NewBlue Titler to my heart's desire. Thank you for all the help and ideas on how to fix the problem.

Ps: anyone know of good training videos for Vegas Pro 11?

Leopardman wrote on 11/30/2011, 2:45 AM

To deny that there is a bug or 2 or 3 within V11 would be foolish, however I cannot agree with a lot that has been stated on this specific thread.

I'm also tech savvy and have been building my own PC's since 1987 (says something about my age, does it!) and have build a complete new system 3 months ago per my specs.

I've been using V11 since day one that it has been released. I had a couple of crashes before the first update but with the exception of one could trace it back to other software that caused application hang problems, e.g. I frequently received an explorer hang problem. I like my gadgets, i.e. Network Meter, CPU Meter, Drive Meter etc. What I have finally managed to trace was that it was the CoreTemp DLL working with the latest version of CPU Meter that caused all my problems. I regressed to the previous version, removed CoreTemp and have not had a problem since. The other big culprit in my case was Windows Essentials AV, since I installed McAfee, no more issues/problems.

Regarding large projects: I'm working on a project that consists of 110 mxf video clips (SONY EX3), 28 m2t video clips (Sony V1E) and was asked to add 400 high res JPEG stills to it. Total lenght of the project is 2 hrs 26 mins, 5 video tracks and 3 audio tracks. I've animated all of the stills using keyframing in pan/crop or VegasAUR, had to apply Contrast & Brightness, Color Balance and Color Curves to the majority of the stills to do color correction.

I've also used NewBlue FX Splitscreen on large sections of overlapping video. Also "Sin City" effects using Secondary Color Corrector.

During the past 2 weeks I've only had one crash and as yet could not trace the source to it. I've succesfully rendered it to HDV Blu-ray at 25 Mbps 1440x1080 50i on 2 occasions, render time 3hrs with GPU OFF as I don't have a top end graphics card. Also created a Blu-ray disc using DVD Architect 5.2 with an Intro section, Top Menu, and 3 Scene Selection Menu pages. One will also note that when Architect imports the 22GB m2v file, it also indicates "not responding", from my disc and memory activity I can monitor that is still processing, give it a couple of minutes and it has read in the whole file.

I don't want to generalize however most people that I have assisted that have had problems with their PC's, not Vegas specific, has for the most part been software conflicts and secondly hardware conflicts.

My honest opinion (said with greatest respect), if one does not have a reasonable comprehension of your software and hardware and all kinds of "behind the secenes" and hidden services, chances are that one will pick up problems. Its just amazing how people download and install software for no good apparent reason and then when sofware conflicts arise, everything else gets blamed. The number of different video/audio players and convertors some have on one machine is just amazing. If one does not REALLY need it why install it? If one installs software to replace other, get rid of the other.

With all its perceived short comings, V11 rocks in my book.

Eddie
_______________________________________________
Win 7 Pro 64-bit, Intel i7 2600k 3.4GHz, Gigabyte GA-Z68XP-UD4 Mobo,8GB RAM, 500GB Boot drive, 2x1TB Raid drives,
1x500GB scratch drive, 2xBlu-ray writers, GeForce GT 440 2.1 Capable, Black Magic Intensity Pro HD External Preview

Leopardman wrote on 11/30/2011, 2:56 AM

I can also add that I have done signficant tests on preview and rendering performance for the type of projects that I work on. Results are in anither thread dealing with this.

For me a RAM Preview setting of 128 MB, 8 threads really makes previewing and rendering rock.

Eddie
_______________________________________________
Win 7 Pro 64-bit, Intel i7 2600k 3.4GHz, Gigabyte GA-Z68XP-UD4 Mobo,8GB RAM, 500GB Boot drive, 2x1TB Raid drives,
1x500GB scratch drive, 2xBlu-ray writers, GeForce GT 440 2.1 Capable, Black Magic Intensity Pro HD External Preview

Tom G wrote on 11/30/2011, 3:00 AM

Deleted
Tomthumb

drrohle wrote on 11/30/2011, 8:39 AM

In response to Steve Mann's post to try the Nvidia Beta Driver -- Tried it last night and wow what a difference! I worked in the NB Titler for almost an hour doing everything I could think of to make Vegas go "Non Responsive" and did not experience a singe hang or crash condition. IMHO the 285.79 beta driver is a "MUST HAVE" for 32/64 bit vs. of Vegas 11 running an Nvidia card.

I'll post back later after I've had more than an hour to play with it.

wildernessbill wrote on 12/1/2011, 2:31 PM

I had system crashes too BUT like any north american computer literate NON manual reading idiot

I just got the Sony Vegas PRO 11 with the titler and had system crashes

read this forum

then went and read the system requirements for both

http://www.newbluefx.com/so/sonytitlerpro/#requirements
http://www.sonycreativesoftware.com/vegaspro/gpuacceleration

Got a new card and now no problems
I was seriously trying to shove too much through a very small hole

No wonder we humans have so many problems

Red Prince wrote on 12/1/2011, 3:41 PM

IMHO the 285.79 beta driver is a "MUST HAVE" for 32/64 bit vs. of Vegas 11 running an Nvidia card.
[br]

Maybe for you, thank you. For anyone who uses an NVIDIA card for Vegas 11 with a full screen stereoscopic preview any driver past 270.81 is a “MUST NOT HAVE” unless you want to tear all you hair out in total desperation.

Leee wrote on 12/3/2011, 2:57 PM

I have most of the NewBlue FX plugins (both transitions and effects) and each plugin has two versions installed, OpenGL and "regular". Whenever I try to use the OpenGL version in Sony Vegas 10 or 11, it crashes.

Does anyone else have this problem?

But this leads me to another line of thought. The NewBlue FX Pro Titler in Vegas 11 does not have the optional OpenGL or regular versions. There's just one. So I'm wondering if this plugin crashes due to the same reason that all my other NewBlue OpenGL plugins crash?

kakman wrote on 12/5/2011, 6:38 PM

Leee,

I am having the same problems as you are experiencing, and I am sure that many others are as well.

I finally received a response from support today asking me to unistall the New Blue Titler Pro. I know that this is NOT an issue as the problems existed in Version 10 PRIOR to the New Blue Titler Pro. In addition I installed Version 11 on my laptop WITHOUT installing the New Blue Titler Pro and the issues are exactly the same.

I have updated my original bug report requesting that they investigate these issues further.

Kevin

Royce1 wrote on 12/6/2011, 4:49 PM

I have full Vegas pro 11 - and

1) It crashes when I attempt to use the Capture feature (using a sony camera)
2) It crashes after I open the TEXT - "NewBlue F/X" titles etc...

I have uninstalled and reinstalled the program - even had Sony Techs with me - walking me through to remove everything. I have tried numerous video card drivers and followed through Sony's direction of wiping out C++ and my printer drivers.

As of December 6, 2011 - Sony has stopped taking calls (saying that they are in some conference/meeting). And Sony has not responded to my emails nor my online Tech Support form.

SONY - Should have NEVER released this program - it is clearly full of bugs. I wonder what my options are since I have heavily invested in Vegas/Sony .

steeleimaging wrote on 12/8/2011, 12:26 AM

Mr. Man... clearly you are out-numbered by people who HAVE issues.

Glad you have no problems. I wish you no crashes or problems. But you HAVING no issues doesn't help those of us who do one bit.

How about solutions?

Your paragraph... "Second, many of us are quite happy with Version 11. It runs flawlessly here on two different computers. One with CUDA and one without. I have finished five projects ranging from a ten-minute demo video to a two-hour stage performance with no problems."

Congrats. No help what so ever, but congrats.

Rattangle wrote on 12/14/2011, 12:46 PM

I also had crash, crash and after doing my own troubleshooting I realized the RedPrince was correct about possibly not going with the latest Nvidia drivers.

I have a geforce gtx 460 with the latest driver 285.?? had crashes with and without using the GPU. I went with the beta 290.?? driver and had the same issues.
Went with driver 280.26 and Vegas settled down and works now. No crashes in the last week. I didn't do any more digging, after the delay with testing I had to get back to work.

Tried what others above suggested and the 285.79 Beta was solid here also.

Royce1 wrote on 4/30/2012, 11:51 PM

I have Vegas Pro 11 (64 bit) - running on Windows 7 64 bit machine.

The program kept crashing when using things like Title & Text, Chroma Keyer and even Color balance. It also crashed with NewBlue Plug in for Vegas.

Sony had me do all sorts of things - and it kept crashing.

On April 27, 2011, - I suddenly tried changing Vegas Pro 11 by using WINDOWS compatibility feature. (Right click the Icon of Vegas, choose Properties and then choose the Compatibility Tab) - The compatibility options are:

Windows Service 2008
Windows Vista
Windows Vista (Service Pack 1)
Windows Vista (Service Pack 2)
Windows 7

I decided on "Windows Vista"

THEN when I ran Vegas Pro 11 - both the Chroma Keyer and Color balance worked - and so far the program did NOT crash. I got it to render out too. I also tried “Titles & Text” and Vegas did NOT crash. NewBlue plug in also did NOT crash.

Could all this verify that Window 7/64 bit and Vegas Pro 64 bit are in conflict? I just sent off an email to Sony Support.

UPDATE: As of May 1, 2012 - More tests later... and staying solely with Windows Vista Compatibility mode, I had two layers of video - chroma keyer, and moving titles of title & text - and additionally two different sets of Newblue titles all going at the same time - and it all worked correctly. Made various adjustments, and changes - and closed it and reopend files, and more adjustments. No crashing whatsoever. So if this Vista compatibility switch continues to hold up - then at least the owners of Vegas Pro 11 can get work done - until Sony properly addresses the issue.

rmack350 wrote on 5/1/2012, 4:41 PM

Royce1, I think you should start a new thread for this. Once a thread gets this long fewer people want to look at it.

Rob Mack

UKharrie wrote on 7/13/2012, 8:40 AM

Not a Pro User, but Architect S crashes after nearly an hour Doh!

What I think might be useful, is if Sony included a short video with a mix of files "Project Test" which is known to run correctly (obviously), That at least would mean you'd know the installation was basically clean. Then perhaps "Project Hard Test" could include some stuff that might cause a problem - maybe even with suggestions how to get round it, things to avoid.

Using the software isn't an issue, although I've managed to crash software by doing too much before it's had a chance to catch-up (seems like it) and I'm none too keen on USB keybpoards either. In my case I was having a cup of tea several feet away!

What do others think about a "Standard Test DVD" of increasingly difficult projects?

As a sweetener, they could be clothed-advertising for the product, or an advanced tutorial etc, etc.

(I haven't had any response from SC since early June2012.)

Then folk could at least report "I'm OK up to #4, etc" - which might be a project that gives the graphics card some grief, etc. logically if the earlier tests were OK, then the area to examine is . . . .

ritsmer wrote on 7/13/2012, 10:58 AM

"mix of files "Project Test" which is known to run correctly"

Sounds like a good idea. Would also be a good tool to test if your PC had a problem.

When people post here about a problem in their system - and add with enough info for others to recreate it - several users do try it and report back.

I have found, however, that it can be a bad idea to report back if everything works well on your machine and when you cannot recreate the error - because you are immediately blamed for posting useless info (!!) and sometimes you're even called a fanboi........