And now he's back? ...interesting.

Yeah I know.. eating Humble pie while foot is inserted in mouth - my frustration can get the better of me at times ;-)

I understand about using DI's and I prefer using Cineform - My question was more around how to manage longer form projects in sections that are more easily managed compared to having one long timeline, although I've read of some Vegas Pro users who do exactly that.

What I've discovered when editing in Ppro: RAM usage goes up like crazy - With several sequences in the project, but only 2-3 of them open, I've seen PPro using close to 4GB of RAM just sitting there doing nothing and that just seems ridiculous to me.

I 've read of others who create sequence Vegas Pro projects, then import those Veg Files into a master Vegas Project before rendering out - is that still considered the ideal way of doing things in Vegas?

I have used Vegas on a number of long form projects and find it's bin behavior very frustrating. Sometimes files switch bins and other times the icons flash like crazy when scrolling in thumbnail mode. Premiere is much better for organizing in bins without issues. I do have 24gigs of ram though. If you must use Vegas on long form you might want to work directly from the explorer window in Vegas and sort that way.

search the term "nesting" or "nested" or "nest" in the forum. To clear up a misunderstanding that may be promulgated - nesting is not an alternative to DI, but rather an adjunct workflow.

You will nest very seldom, and only for a good reason in very short complex composites - maybe 30 seconds or less of complete timeline. The reason for nest is to create sequences that will have multiple uses. Say nest 1 is composed of timeline 1 combined with timeline 2, but in the future you will use timeline 1 unchanged in combination with timeline 3 and even later timeline 4.

Cliff - do you recall the time you were here before - read this:
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=912654

Speaking of recombining .veg programs you will need both Vegasaur and Vegas Production Assistant 2 to complete your workflow tools.

All of this just reiterates what you need the most - a DI - every step of the way - and all of your sub-projects get merged into longer and longer DI's until you are ready to deliver output.

Sounds like a great way to increase the chance of a Vegas crash. Kiss, that is the adage to follow with Vegas.

Working with Nesting Project in Vegas Pro is a bit heavy, and I only use for short compositing motion, and in the end, I usually just render them to any intermediate format I use, including reduce the possibility of having rendering stuck (rendering halt in the middle) or crashes for long projects.

There's one pros for Sony Vegas Pro compared to Premiere Pro, where you can have multiple instances of Vegas Pro run, and you can do copy-pasting between them both.

Add: I rarely working with those project bins, so I just drop those clips on the timeline, and choose there, but everyone has their own different working style.

>>then import those Veg Files into a master Vegas Project before rendering out

I've been working on a long form project that now is running 2 hours. I've used sections of 5-10 min. I then render the sections to a Sony MXF file and combine these files into the longer form. I think this is more reliable than using "nested" veg files. This kind of workflow seems to me to be common sense. I cannot for the life of me understand why anyone would want to deal with a timeline that is even 30 min if there is the option of working in sections.