List things that break Sony Vegas 8

mike_dulay wrote on 2/4/2008, 4:18 AM
Hi all,

I've been having a hair pulling time trying to render since switching from 8.0 to 8.0a then 8.0b. Vegas would inexplicably close itself in the middle of editing or render would start but hang in the middle. I'm looking to compile a list of things that make it break and what workarounds/fixes we've all used. Hints on what to watch out for help too.

My config: Windows XP SR2, Sony Vegas 8.0b, 2GB RAM, Intel Core Duo 2.0Ghz, editing HDV files extracted via HDVsplit/Sony Video Capture

1) Big JPEGs
Big JPEGs from DSLRs (3-5MB each) eats up RAM. Nested projects with full size pictures or having more than 10 big pictures mixed with HDV footage can cause crashes when editing pictures in the timeline. Or at times the render can be started but halts.

Workaround A: Resize photos or convert to PNG
Workaround B: At first I could solve it by changing the preview ram from 128 to 0 and render threads from 4 to 2.
Workaround C: Break out the JPEGs into their own clips and render to them separately.

2) Vegas crashes after opening a project or adding HDV footage; using lots of RAM
Vegas crashes when it gets nearer the end of a 4 minute HDV project. Effects used were 2 velocity envelopes, three clips with color correction. 3 transitions. It appears to happen near the end while Vegas creates thumbnail images for the video timeline.

It appears that physical RAM spikes to 1-1.2GB used out of 2GB on the system. Windows Page file goes to about 2GB, around here Vegas appears to get unstable.

Workaround A: Split into smaller vegas files and render clips separately; then get the rendered clips together in a new project.
Workaround B: Kill all other applications; hope its enough free RAM you don't crash.

3) Project previews but won't render
I've got all the clips put together with no effects, few or no JPEGs. I have a soundtrack and run preview. It all looks good and I choose a render option (Quality: Good).

When I choose WMV it runs for a while then stops 'Specified and invalid argument'. No other WMV render will work until I reboot.

When I choose MainConcept AVC it starts to 'rendering'. Time increments but progress meter doesn't move out of 0.

Workaround A: Find a format that works, go for highest bit rate/quality. Convert the video to target format using SUPER(C) or VirtualDub.

Comments

DJPadre wrote on 2/4/2008, 5:43 AM
There are alot of things that make vegas break
Memory usage has always been one of them, but i have to say that V7 is so solid in this regard that franky i am amazed.

I have 2gb here, with system allocated PF settings.
My PF hit OVER 4gb and my renders still played without a problem.

This was in V7

To be honest with you, what i think SCS shoudl do is offer a free downgfrade to V7 for those who bought into V8.
This is to simply allow a stable working environment, and for elements to go into BD or anythign V8 exlcusive, then allow V8 to save Vegs' back down to V7

Its the only fair thing to do until they can iron out the kinks.

Personally, i feel Vegas is in dire need of a complete rehaul
Premiere has had 2 since Sony bought out SF, and each new build has been incredible. Despite the fact i hate teh GUI and find the app sluggish compared to vegas, it doesnt have the issues vegas does.

It has its own, but none as dire as this

In any case there are alot of element that need work, from memory management through to output settings through to reading a basic files metadata without puking (ie ive lost count how many times believes progressive footage to be upper field first.
These might seem trivial, but ve had countless issue and lost productivity becuase of these problem.

As it stands, i dont use Vegas 8, UNLESS im cutting MPG2 or wanting to delivery AVCHD
Xander wrote on 2/4/2008, 5:44 AM
My config: Windows Vista 64 Home Premium, Vegas 8b, 4GB RAM, Pentium 840D 3.2 GHz, HDV (HDVSplit), PNG and Quicktime.

Crash: Rendering to HDV, AVCHD, etc when working in 32bit mode
Workaround: Nesting the above .veg in an empty timeline and rendering from there

Not experienced any other crashes.
mike_dulay wrote on 2/9/2008, 8:31 PM
Found another trick, when your project terminates while opening and you know which clip is taking it to the edge, minimize Vegas the next time you call it. When it reaches 100% you can maximize again, the clips will start to update thumbnails. Chances are the project is big, so go to the offending clip before the preview reaches it and delete. Then save!
DJPadre wrote on 2/10/2008, 8:15 AM
I just want hem to stop this bulls**t duplicate frame issues seen with progressive scan...
It really is an absolute joke... this is NOT acceptabnle consideirng Premiere, AE, and FCP now have decent progressive scan FRAME management as oposed to garbage data

YOU CANNOT WORK WITH PROGRESSIVE SCAN with this NLE using its full capacity.
Transitions should NOT show any interlacing, there shoudl be no banding with field order scaling...

Its unnaceptable.. more and more CS3 is looking teh go...

at the moment im forced to use it to be able to manage the elements i need with progressive (slowmotion) in these apps, then reimportng into vegas..
ts not good enough...

this is an ABSOLUTE JOKE

Vegas works a treat with interlaced, but not allof us use interlaced.. hell, have you seen what vegas does to 1080i converted to 1080p?
God forbid i show this shite to my clients...
Serena wrote on 2/10/2008, 8:09 PM
Something I just experienced was unexpected, but probably understandable. I wanted to do a wide pan in a dark place (architecture). So I created a panorama using my EOS 5D, compressed it to 4 Mb and dropped it on the timeline. Selected "match output format" and Vegas can't handle that at all. Quite happy if I cut the panorama into portions.
farss wrote on 2/11/2008, 1:15 PM
i think Vegas can only handle 4K x 4K. I think that limit also applied to early versions of PS so there might be some code boundary involved.

Bob.
Serena wrote on 2/11/2008, 1:54 PM
Bob, that seems consistent with my observations.