Nested veg files not opening

[Bill Church]

Sounds like you definitely need more RAM allocated to the application while editing, vice rendering. I’d try setting to at least 6000MB, vice 600MB. Should make a big difference.

Bill Church
Briarwood Productions LLC

[John Rofrano]

[Bill Church] “Sounds like you definitely need more RAM allocated to the application while editing, vice rendering. I’d try setting to at least 6000MB, vice 600MB. Should make a big difference.”

This is a misconception. You want to actually set the RAM preview LOWER because it is only use for performing a RAM preview via Shift+B and it TAKES AWAY memory from other editing tasks and rendering. I would set the RAM Preview back to it’s default (128MB or 256MB).

[Paul Gregory] ” I’m using Vegas Pro 10.”

Are you using the 64-bit version? and are you using the latest 10.0e Build 738?

I would also try adding the nested veg files one at a time. Vegas has to build audio proxies for each veg file and that takes some time. Also doing them one at a time will let you see if there is any one project that is causing the problem.

Finally, make sure that you open each nested project separately before you import it and clean the media pool so that there are no missing files that aren’t being used. This will cause nested imports to fail.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Bill Church]

Point well taken, John. My bad. Vegas just seems to be much more stable for me, with fewer crashes, when I set it higher. Probably just my imagination!

Bill Church
Briarwood Productions LLC

[John Rofrano]

It’s a really misunderstood concept in Vegas probably because other NLE’s actually allow you to say how much memory they should use but the Vegas setting isn’t like that at all. It just reserved memory for that one feature of RAM Preview. Of course, if you use RAM Preview a lot (like I do) you may have to set it higher at times (I keep mine at 1024MB and I have 8GB of memory) but it does take away memory from other editing tasks.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Jim Greene]

John: “Finally, make sure that you open each nested project separately before you import it and clean the media pool so that there are no missing files that aren’t being used. This will cause nested imports to fail.”

This is KEY! Vegas doesn’t seem to be able to know what the problem is when files are missing in the veg that is being nested. Gets me every time.

-Jim.

[John Rofrano]

[Jim Greene] “This is KEY! Vegas doesn’t seem to be able to know what the problem is when files are missing in the veg that is being nested. Gets me every time.”

Yea, it still gets me too sometimes and you get strange messages in the master project so cleaning the media pool is always the first thing I look for when nested project don’t work.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Paul Gregory]

Thanks for the advice but even after opening each veg file without problem I can’t get everything to open as one project. I have reduced the ram setting as well. When opening each veg file separately I noticed that one had an audio track names as Microsoft Sound Mapper. I’m not sure just what that is but this isn’t listed against the other veg files when they are open. Could this create problems? Does it matter that some veg files have more tracks than others?

Had I just rendered each segment out & then imported each new video file onto the timeline I would have spent less time on this. It’s making me ask what if any other advantages are there with using the nested veg files?

Thanks in advance

[John Rofrano]

[Paul Gregory] “I noticed that one had an audio track names as Microsoft Sound Mapper. I’m not sure just what that is but this isn’t listed against the other veg files when they are open. Could this create problems?”

No sure. Try importing all of the other projects and see if leaving this out helps. I know Vegas has to build an audio proxy for each of the projects so if there is an audio problem in one of them it can cause problems.

[Paul Gregory] “It’s making me ask what if any other advantages are there with using the nested veg files?”

I use them for intros and lower thirds and isolating 3D Track Motion and they come in quite handy for keeping the main timeline neat and clean. I also build my training DVD’s with each chapter being a nested project and I’ve not had any problems. Perhaps you are adding more nested projects then your computer can handle?

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Paul Gregory]

Thanks for that reply. When I mused that I might have been quicker if I just rendered each segment out for reuse into the final project I was thanking about rendering the segments as M2TS just like the original footage, so as not to loose any quality.

But thinking ahead, I have yet to burn my first Blu-Ray but if I wanted to do so could each segment still be rendered out for Blu-Ray or would this make things too difficult/impossible for DVDA?

Thanks in advance

[John Rofrano]

[Paul Gregory] “I have yet to burn my first Blu-Ray but if I wanted to do so could each segment still be rendered out for Blu-Ray or would this make things too difficult/impossible for DVDA?”

You want to have one large file so that you can set chapter points and navigate back and forth through it. If you use multiple files, you will not be able to navigate back past a file boundary.

~jr

http://www.johnrofrano.com
http://www.vasst.com