I just deleted my last post. I just realized that in my case it's not locking up at the last frame, but instead the progress on the preview window seems to be finishing before the render. It will get to the last frame on the preview window at some percentage that is too early to be done. Then it will continue rendering and showing percentage progress, meanwhile the preview window will be stuck on the last frame. When the percentage finally gets to 100%, it will finish properly and the render will be ok. This is different than it was before, but I can live with it. Nothing like your problem I am sure now.

What was tricky about this was that I didn't realize that it had stopped on the last frame. Since the last frame was black and the progress meter was reading out a percentage less than 100%, I assumed it had stopped making progress mid-render. For now I will just start ignoring what I see in the preview window since in this revision it seems to be irrelevant.

Perfect example of User Error. One has to wait for the render to complete in order for it to be completed. Be patient with renders. After the render finishes, vegas has some over head that needs to be settled before it is completed. Technically, the render has finished, but Vegas is still working.

As for the OP try changing your preview to ram settings in preferences to 0. Good luck.

We still cannot use the youtube auto render or certain blueray and mpg4 templates for a full render. Had to stop scratchin head and move on.Hopefully there will be a resolve soon.

Since the render is complete and I do wait past that completion, I am not so sure that user error is what is going on here.

Given also that I have had crashes while sifting through the render menu prior to starting the render, there is definitely something else involved.

I may be making some other errors, and/or I may have some hardware that needs to be reconfigured.

I will let everyone know if and when I divine anything else with my setup.

Mine will lock up in the render menu as well, usually when I click on "customize template". The lock up usually lasts 20-30 seconds. I reported it to SCS back in V.10, but they have been unable to fix it.

I'm sure it's user error, tho. I've never been very good at clicking a left mouse button.

You are right in that this occurs when I click on "Customize Template", but every render I do involves using "Customize Template". Interestingly , however, the only template that has made this happen for me has been audio-only AC3Pro, and it has happened every time.

That seems like some good data if anyone from Sony is watching.....

My advice for you started where I wrote for the OP. Sorry for the confusion.

So, you are saying that high Ram settings for Preview could be interfering with render actions?

Interesting.

Not to sidetrack this, but your mention of the GRaid made me realize an adjustment I've made to my workflow in V11. I spend a lot of time during the day switching between projects, and I got used to hovering my mouse over the big X so as soon as my render finished I could exit Vegas and move on to whatever I was doing next.
Ever since the first build of version 11 I couldn't do it anymore. It would lock. After a render, after a save, or even after a few minutes of inactivity on the timeline, my GRaid will light up with constant disk activity for 5 - 10 seconds and then return to normal. If I try to do anything while this disk activity is going on, lock or crash. Doesn't happen with V9 or 10 on the same rig.

That is not sidetracking at all.......and I have definitely noticed my Graid "going to sleep" sometimes and not waking for a few seconds after I try to start playback.

This could explain all the crashes.

I find this behavior of the Graid to be pretty odd and dysfunctional. .....but you say it only happens with 11?

I do think, but cannot be sure, that most of this behavior with the Graid drive started happening after I switched it over to an eSata connection, where it had been on USB prior to that. How is your drive connected?

So, you are saying that high Ram settings for Preview could be interfering with render actions?

It's certainly possible for the RAM preview setting to interfere with a render. The safest thing is to turn it down to a low setting, but in some circumstances setting it to zero has a positive effect. You could try some trial and error tests, or just settle for some conservative number like the vegas default.

Rob

V11 is quite different than previous versions in that there is now a heck of a lot more of the rendering process still to go after what you see in the preview window has completed. It used to be just a little housekeeping at the end. Now it seems to be a whole lot more.

@mudsmith, Mine has always been connected since day one eSata. Versions 9 and 10 never caused me to vary my program-exiting frenzy that makes up my day. With 11 I have learned to ...wait for the little light....OK exit. I fired up the last build of 10 after I saw your post and I can flail around the timeline, render, save, anything and no extra activity on the GRaid except when playing the timeline with footage from the RAID. It's as if Vegas 11 is "remounting" or "polling" the drive anytime it does anything. I'm always watching the activity light out of the corner of my eye, and if it's on - I wait. Lots fewer issues.