Vegas pro 9.0 rendering issue

[MediaMason]

Hey Guys, hopefully someone here can help. This problem just started to come up and has be slowing down my workflow and causing tons of issues. I've been editing with Vegas since 4.0. I upgraded to 9 since it came out never had a problem to this scale. I have been shooting with dvx100 footage for years and over this past year started shooting with the gh2 mts files. I render all my client footage to 480p for dvd payback (yes even my HD footage due to location and client hardware) my machine can handle 480p footage no problem.

Once I started shooting in HD I started proxy editing and had worked for a few projects. Over the past few days my workflow has come to a screeching halt. My proxy files crash my vegas project during loading so I started editing the HD video with draft quality (little hard to work with but I'll manage) then when I go to export my 854x480 mpg2 file the render crashes but I can render 720x480 mpg2 file with no problem. Anyone experience similar issues? I have tried tons of other video converters to fix my proxy issue but gave up on that idea thinking I was having a codex issue.

my last successful projects I had were:
family video rendered out to 1080p for internet
halloween project rendered out to 720p for internet (proxy edit)
client wedding video rendered out to 720x480p for mpg2/dvd (proxy edit, 720x480 creates pillars as well as letterbox and this is unwanted)

I've tried other projects, different computers and can't quite get a handle on this issue.

Thanks
--
Evan

 

[MediaMason]

a clean install of Vegas fixed my proxy issue. As for the pillars I was experiencing was my lacking knowledge. Since shooting with the HD footage I had it in my mind I needed to keep it as square pixels, but rendering out at 720x480 with 16x9 fixed that problem. You can't render out to 854x480. When rendering out the error would read "The reason for the error could not be determined" but a few hours later and few more render attempts rendering at 854x720 one error stated render size not accepted or something like that. it would have been nice to see that error earlier. I hope this helps someone out with a similar issue.