I started using nesting some Vegas releases ago when the program suffered from memory leaks which crashed my rendering. Someone suggested nesting my crippled project and although I didn't see the relation between memory leaks and nesting, it worked flawlessly. I still don't know what's going on under the hood but what-me-worry.
Since then, I resorted to nesting whenever I had rendering problems and it always saved the day. Sometimes, Vegas hanged in FX-laden projects (or didn't process effects without hitches) and then rendering using nesting always solved the problem.
Besides that, I often make long video travelogues, edit them in chapters and combine all chapters in a master project using nesting. Rendering then always runs like a train. What is important (also in complex projects anyway) is to give Vegas time to open the project and not do anything else in the meantime. Sometimes it seems that Vegas is not active but when you open Processes in the Task Manager you'll see there still is a lot of disk activity. Just wait till it's finished.
Just my 2 Euros.
Lou
Since then, I resorted to nesting whenever I had rendering problems and it always saved the day. Sometimes, Vegas hanged in FX-laden projects (or didn't process effects without hitches) and then rendering using nesting always solved the problem.
Besides that, I often make long video travelogues, edit them in chapters and combine all chapters in a master project using nesting. Rendering then always runs like a train. What is important (also in complex projects anyway) is to give Vegas time to open the project and not do anything else in the meantime. Sometimes it seems that Vegas is not active but when you open Processes in the Task Manager you'll see there still is a lot of disk activity. Just wait till it's finished.
Just my 2 Euros.
Lou