Transferring nested project to another machine

fausseplanete wrote on 6/17/2010, 11:55 PM

Hang-problem when opening a nested project on another machine:

On machine 1, Project A (veg file) has nested Project B (veg file).
These Project files are held on external disk.
Opening project A works fine - no problems.

Next I plug the disk instead into Machine 2 (has same version of Vegas)
I open Project A there but it hangs with 100% CPU.
Deleting the sfap0 files beforehand does not fix this, it's like Project A internally "knows" it's on the "wrong" machine.

No such problems when I simply open Project B (ie any project not containing nested projects) and of course no problem on the original machine.

Is this a known issue and is there any workaround?

Comments

farss wrote on 6/18/2010, 5:03 AM

Could it be that the other machine is missing a plugin?

Aside from that I'm slightly uncertain about the parent / child relationship here. Is Project A the parent of B?

Bob.

Rory Cooper wrote on 6/18/2010, 5:22 AM

Try renaming project A to ie C in machine 2 before you open it

I have had this before but it’s always a plug in issue normally Prodad

FilmingPhotoGuy wrote on 6/19/2010, 1:37 AM

The VEG file saves the paths of the media it requires. So if your MAIN.VEG file calls a nested F:\projects\effects\explode.veg you will have to make sure that that path exists.

Using a HEX editor on a VEG file you will see the path.

fausseplanete wrote on 6/19/2010, 2:15 AM

Many thanks for those suggestions.

Will check for ProDad etc.

A is the parent of B (A uses B on its timeline like a media file).

Noticed path inside veg file when opened using NotePad. Had hoped Vegas would just ask for replace-media, but not so at least on my system.

Will get back on the other suggestions. I have only occasional access to broadband at present - apologies for late replying. And now I have someone's loose pet bunny rabbit to deal with! C'est la vie. Hang on, "maybe it's trying to tell me something...".

fausseplanete wrote on 6/20/2010, 12:46 AM

AHA! So Pre-renders don't travel well it seems
...at least, not in my project's case.

i found by (3+ hour) process of elimination that clearing all pre-rendered files then doing a save-as of the child project fixed the problem, so now the parent project opens fine on both machines, even when the drive letter is not the same.

Not sure why it needed to be a Save-As not just a Save but maybe it forced some kind of further clean-up of some other kind of confusion, maybe some knock-on effect of the Pre-render issue.

I wish Vegas had just done "no prerender present - so stop looking for one"...

Rabbit & owner successfully reunited by the way!

Rory Cooper wrote on 6/21/2010, 3:13 AM

Thanks for the answer Dave .good to know