Project dependant.

Might depend on the nature of the edit.

For example, by using sub-projects (which I have done, and worked very nicely), I believe you limit the audio of said sub-project to stereo. So, if you have gone to the effort of putting a surround mix into the sub-project, it will be lost when imported into the master.

This, of course is not a problem if you are working in stereo, or if the true audio mix is to be done in the master project.

Also, I only work in SD, but I have a vague recollection of some rumblings about issues with HDV in nested projects; perhaps others could confirm or deny this.

Ciao,

marks

I've done it as multiple Veggies and nested them into a master project. Can't comment on probs with 5.1 as I've never done it.
Things to know:

1) The nested project is 'served' to the master at the sub project project's settings. This is a HUGE plus. You might need to do your titles at Best and the main body of your movie at Good. You can save a massive amount of render time nesting the titles in their own Best project.

2) If you do any velocity envelope stuff in a nested project it just doesn't work right when you playback the master. Don't freak, it'll render just fine. If you want to check your speed ramps open the nested project anyway. No big deal.

Bob.

reberclark, I'm finding it easier to edit in segments so that the entire project doesn't have to load every time. However, I've never put multiple vegas files together for one final edit. Will it retain all editing, cropping etc while importing all of the raw footage. What is the procedure? Are you importing Vegas in Vegas?

farss, silly question but how do you render titles separately from the movie and have them still together in the rendered file?

Will it retain all editing, cropping etc while importing all of the raw footage

Yes.

What is the procedure? Are you importing Vegas in Vegas?

Save the segments as thier own veg file (i.e. submaster-1.veg, submaster-2.veg, etc.).
When you create the master veg file, import the individual vegs and drop them on the timeline.

Mike

Depending on the project I will edit in segments. Especially if I have a lot of compositing for the into. That will almost always be it's own project. If I'm doing a VASST training video, each major section is a separate project file. This is the reasons that Ultimate S has the ability to import nested projects and extract markers ('cuz I needed it ;-)). Each project for the training video has its own set of markers for chapter points, then I use Ultimate S Import Nested projects to load them all into a master project and it automatically extract the markers (which become chapter points for the DVD) and then I just render the whole thing out and I'm done.

Nested projects are Da' Bomb! Love 'em. Use 'em all the time.

~jr

Two ways.
Create the titles in one project and render them out. Then bring the resultant file into you main project. Problem with doing this is you'd likely want to render to uncompressed. Uncompressed video means large file sizes compared to DV however as your titles are probably very short shouldn't be an issue. Advantage here is the titles are only rendered once. So if your titles are locked it is one good way to work.

Other approach it to bring the title veg itself into your master project as a nested project. Advantage to this approach is you don't have to render a large uncompressed file. Down side is every time you render out your project all the work the CPU has to do to render your titles is done again.

Bob.

Omar: I am importing Vegas to Vegas running 2 copies simultaneously for the import (which is really copy and paste). The only thing that doesn't transfer is envelopes as far as I can tell.

I edit in segments and render the segment out as a single M2t file which I then import into a compilation project. I work in HDTV and this keeps the playback speed consistently correct in the compilation project. I don't do this all at the end but every few days to maintain in my mind's eye a good perspective of how my movie is progressing over all.

This also makes it easier to screen WIP for visiting clients and friends and makes it simple to burn WIP DVDs.

It really pays to read these threads

Ive never nested projects before so often I would have projects 12 layers up now I can bring it down to 3 intro, body, and conclusion And you can edit each veg from your main veg , well done Vegas
I am like a kid with a new toy

From now on I am gona eat my veg’ies

Thanks guys
Rory

It really does pay to read these boards. The way I was using 2 copies of Vegas and copying and pasting sections is really way too many steps. I didn't understand that to edit a nested section you right click the section (which appears mixed down/rendered) and choose "edit in Vegas" which opens a second copy of vegas with the original file in all its glory. The way I was doing it, the source files would be unchanged after edits in the main project. With nested files the source files and the main project change with edits. Well done Sony.

> With nested files the source files and the main project change with edits. Well done Sony.

And that is the real power of nested projects. Nothing needs to be rendered. Everything stays fluid. It's just a brilliantly productive workflow.

BTW, if you use Sony ACID, you can save your output (WAV file) with an option to embed project information. If you do this, you can also right-click on the WAV file in Vegas and select Open Project in ACID and go back to ACID and make changes and render it out again. This is another great workflow enhancement.

~jr

Could you just render the titles as uncompressed to a new track in the nested project? That doesn't change the need to create the uncompressed file but it gives you a direct link back to the project. Not sure if this is really desireable, or more trouble than it's worth.

Rob

> Could you just render the titles as uncompressed to a new track in the nested project?

Sure you could, but that takes time to render and every time you make a change there is a re-render and more time lost and time is money. Nested projects is a much more elegant solution.

~jr

I'm talking about doing it within the nested project so that there's very little rendering to do when you open the project it's nested in.

It's also relatively easy to clip out and rerender a change in the new track.

You're still using nested projects but I'm thinking the nested project clip would open a lot faster in the parent. I find nested clips slow down the loading of the parent, especially if you're going back and forth to sound forge (for example). And, as you say, time is money.

Anyway, I haven't really tried it. It's just a thought.

Rob

Back in the SD days, I'd render all the pieces of a larger project into AVI's then assemble on the final T/L and render to DVDA. It was and is the only way to get real time playback to see what things actually look like, if sync is holding etc. Finally I tried nesting and am getting the hang of it.

It's great to avoid major rendering, but let's not kid ourselves, it's not render free. Every time I hit SAVE on a nested project, the master project renders the sfap0 file.

On my current project it takes 19 minutes to render the sfap0 for a 2hr nested file. NUTS. What I don't get is why the CPU load, whether for both sfap0 or peak building, never rises above 15%, and generally hovers around 7%. why not load up both CPU's and get it over with?

I took the following steps to shorten the render time:
1)created a simplified intermediate file for nesting. In otherwords, I deleted half the tracks from the original file hoping it would speed up sfap0 render time....it did not.
2)I took the FX from the nested file and put them on the event in the master file. It helped playback by around 20%, and now I can toggle them off in the master file.
3)Neat Video is a great plugin for removing grain and wrinkles from the birthday boy (50th) but it seems to be a memory hog. I had 2GB but was getting alot of crashes. Installed another 2GB which XP Pro recognizes as 3.25, and so far it seems more stable.

HTH,

Scott