Comments

MacVista wrote on 6/2/2008, 12:54 PM
It's going to be very hard for anybody to offer any help without some more information.

For example:

What type of project?
What resolution are you working at?
Available space on hard drive?
When does Vegas crash, starting, editing, rendering?
Have you changed anything on your system recently?
and anything else you can think of...

The more information you can provide the more likely it is that someone will know the solution.
dosin wrote on 6/3/2008, 4:50 AM
I am using the default settings and I am working on a project with about 70 mpeg clips. It takes forever to load the project and then I can start to work but it freezes after a few minutes then I get the program not responding message. One time I was finally able to fininsh then it would not render It would just stop after 40 % complete and the program would just close. I have tries to redownload my clips and still nothing. I have over 200gb of space left on my hard drive. I have trend mico for anti virius software but this happens even after I shut it off. I have not changed anything on my computer. Please try to help me I do not know what to do.

when it closes I get the error message and it say hung app I do not know what this means
MacVista wrote on 6/3/2008, 5:56 AM
What are your project settings? (resolution etc.)
Where are the mpeg clips from, have you captured them from a camera or are you downloading them from somewhere on the internet?
Are they mixed resolutions/codecs?
CorTed wrote on 6/3/2008, 9:03 AM
I would suggest editing and rendering in smaller batches. Meaning only load a few of your clips at a time.
I have done this succesfully on various projects where 8.0b would hang up due to memory related problems, but when you keep you project short, it will work. Also try to render to AVI, then once you have all segments rendered, then string all the AVi's together and perform a final render.
I think it has been proven by many memebers here that 8.0b has memory issues especially when loading many mpeg clips on the timeline. I hope 8.0c will fix this.
Can't wait for June so they can release it...... (oh it is June !!!)


Ted
jeff-beardall wrote on 6/3/2008, 10:28 AM
just finished a project that was giving me huge amounts of crashes and errors in the render stage. when i set the ram preview amount to "0" i was finally able to render out the whole project. give it a shot...might help.

jeff
dosin wrote on 6/3/2008, 6:24 PM
It looks like my problem is with the media manager I went online and research some similar problems. I removed the media manager and I was able to render. The one project was still extremly slow to open but I am going to see what happens with a new project. Thanks

I will keep you informed.
Darren Powell wrote on 6/3/2008, 7:16 PM
Hi Dosin,

Welcome to my world.

As soon as you try to build a half decent sized project with m2t's Vegas 8.0b crashes all the time, won't render, disappears of your screen ... etc etc etc etc etc....

Don't be tricked into thinking it's the Media Manager ... all you've done by switching it off is to free up a little bit more memory ... if your project increases in size again you'll be back in shitsville.

Cheers,

Darren Powell
Sydney Australia

Serena wrote on 6/3/2008, 9:00 PM
So this is a problem of memory demands in processing many m2t clips? This suggests that Vegas is storing "decoded" GOPs in memory. Purely a guess -- I haven't seen any explanation of how Vegas deals with cutting m2t clips, but that would be one way of doing it. If so, rendering to avi or using other digital intermediates would seem to have additional benefits.
farss wrote on 6/3/2008, 9:06 PM
If so, rendering to avi or using other digital intermediates would seem to have additional benefits.

Yes. Just rendering a single track of m2t from tape at Best I've seen Vegas take minutes for a frame or several frames from tape take minutes each. Then it gets going again. It didn't crash, just took 90% of the render time to deal with 1% of the video.
If I'd had a few hundred tracks all being dealt with at once it wouldn't surprise me if V8 came crashing down. So your advice should yield a viable workaround to say nothing of it being way easier and less frustarting to diagnose problems.

Bob.
AWinn wrote on 6/7/2008, 7:04 PM
I have experienced similar problems when attempting to proceed on my project. Vegas Pro 8 consistently crashed when project media was visible, so I switched to list view. However, I can not make any progress on my project b/c of error/crashing problems. The files were loaded from Sony Hard Drive camera. Also, I attempted to Selectively prerender, however, once again program froze/crached. I must complete this profect in a couple of days. Any suggestions, or work-arounds?
Serena wrote on 6/8/2008, 1:11 AM
If you haven't done this, start a new project and load in a few files to see whether Vegas behaves then. If so, then cutting your job into scenes or segments would be the way to go. If not, you probably have a system problem and it might pay to run System Mechanic (or similar); John Meyer keep quiet -- it's worked for me ;-) ! If you are trying to pre-render without reducing the number of m2t clips, I think this won't work because the number of m2t clips seems to be the problem. You would be better using NEO HDV to turn your m2t into avi and then loading those into Vegas. You can download a trial version. Are there free alternatives, anyone?
farss wrote on 6/8/2008, 2:38 AM
You could try the SonyYUV codec as an alternative to CF, it's free as it ships with Vegas however for HD you're going to use up a lot of disk space.
Of course if your delivery format is SD then you could batch render your clips to SD SonyYUV. That'd preserve the chroma sampling gains from downconverting (more of a plus if working in NTSC than PAL if delviery is SD DVD).

Bob.