Q. VP11 Nest into VP10? Possible?
A. No.

Nested projects must be able to be opened by Vegas and Vegas 10 cannot open a Vegas 11 project so you can't nest Vegas 11 projects on a Vegas 10 timeline.

~jr

But isn't the nest a proxy? An interim rendered proxy?

G

"But isn't the nest a proxy? An interim rendered proxy?"

Yes but the proxy is created by the parent, As the parent is 10 it cannot open the V11 project to create the proxy.

Maybe, just maybe you'd think you could create the proxy by first nesting 11 > 11 and then 11 > 10 but something tells me it will not work, worth a try I guess.

Bob.

I get the following error:



...Jerry

Thanks Jerry.

Bob that was along the same line of thought I was thinking. A Proxy is a Proxy is a Proxy, it's built into the DNA of its meaning. Like a Prerender file.

Hmm....

G

"A Proxy is a Proxy is a Proxy, it's built into the DNA of its meaning. Like a Prerender file."

Indeed and that's another thing about Vegas that confounds me.
Being able to edit proxies with ease and then match your low resolution / quality proxies back to camera originals is just part and parcel of what is given in other systems and even between systems.

I know this is not how you're trying to work and might never need to. It's just a "feature" that can be used in many ways and even the developers might not be cogniscent of all the ways a feature can be of benefit to the users.

Bob.

Well, two surface issues with "a proxy is ...":

1) The proxies would still have version numbers, were it true. Vegas 10 can't open a Vegas 11 proxy. *EXCEPT* ... that's just not true.

2a) The proxy is only the audio track. Generally it's a .wav file. .wav is no respecter of Vegas version numbers so any particular version of Vegas won't care what other version created it.

2v) The video portion is *NOT* a proxy, but in fact is the actual .veg file of the nested project. You can tell this is true because a nested project opens up the first time requiring only the length of time necessary to render the audio. Elsewise, a complex project might take many, many hours of rendering to produce a video proxy file before it could be nested, and this just doesn't happen. If there was a video proxy it would be similar to Vegas' "render to a new track" function.

So, hey, you could use Vegas 11 to render to a new track, keep track of where you created that new video "proxy" file, and then use that file in your Vegas 10 project. Note that of course you'd lose the ability to drop down a level and edit the nested project, since it's no longer a project but a rendered file. You'd have to go back to Vegas 11, make the changes there, and render a new proxy all over again, then go back to Vegas 10 and carry on. This also shows that in the normal nesting situation the video is not a proxy, since you can open it up and edit it.

<musing>Personally, i never really found the render to new track option that much more useful than simply doing a render of the part i wanted to a new file and inserting that new file in my project where i wanted it.</musing> So in this case that would work just as well or even better than the render to a new track option, especially if you had no real need to replace that section of your Vegas 11 project with a rendered version.