Vegas 8b lockup on HDV render

[Jeremy Rasnic]

What format are you encoding to for output? Attempt doing an encode in an avi wrapper so that you can pick up the encode where it left off and then continue. I think the issue may lie with the mov files but I am unsure. Using the juicer, is there a way to export them as avi files with alpha channel? I haven’t used the juicer in a long time.

Also, based on the file types, masking and amount of items on the 30 second timeline, it does not suprise me that it is taking a while to encode. You may be running into ram issues. If you are willing to try it again, watch your pagefile usage under the task manager and see if the level climbs and plateaus at your maximum page file usage when the encode hangs.

Let us know.

j razz

[Charles Avanti]

I was rendering to a “new track”
Type= Video for Win. AVI
Template: HDV 1080-601 intermediate

I have 4 gig of RAM installed and it tested OK.

I know how to look at Task Manager and Monitor, but where do I find the pagefile usage and what do I look for? Thanks.

B-T-W I did send this to SONY.

Charlie

[Jeremy Rasnic]

The page file usage is denoted as PF and it should be located right below your cpu usage graph.

Instead of rendering to a new track, try “File”–>”Render As” and then choose your settings there.

j razz

[Charles Avanti]

I may have stumbled upon the solution…..again. I found since using/fighting with computers since 1980, sometimes when your up against the wall, it’s worth trying the wild card long shot idea.

This is what I changed:

1. I deleted 3 video tracks that were set up as parent/child that had no video on them since I decided on an edit change.
2. I used the default name of the new track “new track 2” instead of naming it “TITLE test” or something. I seem to remember something about not naming tracts “Title”, or some such name.
3. I let Windows Task manager- performance run on top of Vegas as it rendered.
B-T-W it rendered in 1 hr. 38 minutes this time.
4. I held my mouth tight to the right.
it rendered fine.

THEN, I added another video track with alpha and tried to render the whole project again, leaving the good part of “New track 1”.
This time I didn’t leave Windows Task manager- performance run on top of Vegas as it rendered, and somewhere near the end Vegas just closed altogether leaving me with no newly rendered project.

So, I tried again, this time with Windows Task manager- performance run on top of Vegas as it rendered. IT RENDERED FINE.
I noticed the CPU ran at 100% both times, but memory was about 2.20mb on the first successful render, and about 1.83mb on the second.

For what it’s worth……..your mileage may vary.

Charlie