Charles Avanti
Forum Replies Created
-
-
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
-
-
Hear are detailed instructions found a link on Vimeo.
https://eugenia.gnomefiles.org/2007/11/09/exporting-with-vegas-for-vimeo-hd/
Charlie
-
-
-
-
I think you will get better DVD quality if you render in Vegas the “MainConcept MPEG-2” USING the “DVD Architect X?X?X?X video stream” template. Click “Custom” and set the bitrate you want to use (after you have determined it using a bitrate calculator).
Don’t use “Optimize” in DVDA. You should have less problems.
Charlie
-
-
