can't open 'foreign' project files

taliesin wrote on 8/5/2002, 4:32 PM

I'd just liked to few some fx-chains created by other users. The way to share fx-chains is to save them in a .veg project-file.

Now my problem is:
I never succeeded in opening a project file if not created on my own system. Any different project file fails opening.

Is this a known bug or are there some things to take care of?

For example I wonder whether it works opening a project file if in there is a path to a folder or to a partition which does not exist on my system.

Any help appreciated

Marco

Comments

seeker wrote on 8/5/2002, 6:59 PM

Marco,

> " Is this a known bug or are there some things to take care of? " <

It's probably not a bug. You can tell from the relatively small size of the .VEG files that they basically just contain instructions for making your project out of the clips and files in the Media Pool.

It's going to be a bit difficult to move a Vegas project from one computer to another simply because the volume of stuff you are going to have to move certainly exceeds the capacity of a floppy, and may easily exceed the capacity of a CD-R. Also, as you mentioned, the VEG file contains the file paths of the "foreign" system, and you will have to somehow replicate that in your system. If the "foreign" system happened to contain all of the project, including media objects, in a single Folder, you could just copy that Folder and bring it across as a self-contained package. If your two computers were both on the same network that would simplify the process of moving these bulky files from one computer to another.

It might be better to do a DV render on the "foreign" system and move the AVI as a self-contained file. Of course, if you were wanting to "rethink" the editing approach, that might not be what you would want to do.

-- Burton --

taliesin wrote on 8/6/2002, 3:56 AM

Thanks Burton,

Sure, I can't expect to have the media files located or moved with the project file.
What I expect if loading a project file coming from a different system is that there would be a message telling me the media files cannot be found and then opening the project with offline-media. This is the way it happens when I reopen a project on the same system where all the media were deleted meanwhile. There's a message of missing media and there is only offline media in the project then.

But project files coming from different systems won't open at all. But there's an article at creative cow which actually mentions project files are the way to share fx-chains. And this is the ONLY way to share fx-chains.
Media does not matter. The only desire is to once open that project to have access to the fx-chain coming from another user.

Marco

Tyler.Durden wrote on 8/6/2002, 7:38 AM

Hi Marco,

Burton's comments on file locations gave me some thoughts... Is your Vegas installation standard, or are the Vegas program files on a directory/drive other than the default?

Which version of Vegas are you running?

Did/do you have Video Factory or another SoFo product on your system? Sometimes, preset or pref files can go to suprising places.

Regards, MPH

salad wrote on 8/6/2002, 8:31 AM

Yeah, I can't find anything you can "change"(settings). Are you getting any type of eror message? Maybe just try dropping the .veg file on the open app.?

I seem to be able to open DL'd .veg files here. I just have to "redirect" it to substitute media..........or leave offline, but they open.

My programs are on a separate partition, so that won't matter, but maybe just a reinstall............?

taliesin wrote on 8/6/2002, 3:38 PM

> Is your Vegas installation standard, or are the Vegas program files on a
> directory/drive other than the default?

Each of the VV-pathes are different to the standard, even the program files itself.

> Which version of Vegas are you running?

3.0a

You mean, I could have problems open project files created with older versions of VV?

> Did/do you have Video Factory or another SoFo product on your system? Sometimes,
> preset or pref files can go to suprising places.

Righty - I still do have VideoFactory on same system. I'll go and deinstall it and try it once again.

Marco

Tyler.Durden wrote on 8/6/2002, 4:00 PM

Hi Marco,

You don't really need to uninstall VF, but you might want to install Vegas 3.0c...

Older versions of Vegas might not open the later version veg files.

HTH, MPH

taliesin wrote on 8/6/2002, 5:16 PM

Don't know if this was the only thing causing problems to some VV-project-files.
I did deinstall VideoFactory now and now I can open some but not all foreign project files.

The error-message occuring is:

"The file is most likely corrupted or of an unknown format. A chunk has an illegal length."

Maybe this is because these project files come from the demo version of VV but mine is the full-version ...?

On the other hand - I finally recognized which the file type of fx-chains are (.sfv) and where they are saved to - maybe it's more easy to share this .sfv-file instead the project file.

Marco

Tyler.Durden wrote on 8/6/2002, 9:13 PM

Hi Marco,

Some of us folks on the COW messed about with this and came to the conclusion that .veg files are the way to go...

The preset and fx chain files are registered and are most easily managed using a .veg file.

Search the COW on chains for more info.

HTH, MPH

seeker wrote on 8/6/2002, 9:53 PM

Marco,

Marty's suggestion to install Vegas Video 3.0c over your current Vegas Video 3.0a seems like a good thing to do. If, by chance, your "foreign" system had a later version of Vegas than your 3.0a, you might be encountering a backwards compatibility thing.

-- Burton --

SonyEPM wrote on 8/7/2002, 9:09 AM

If you install 3.0c, you should be able to open this file.

taliesin wrote on 8/7/2002, 6:12 PM

Ah, yes. Right now, I am midst in a project. As soon as it is finished I'll do the upgrade to 3.0c.
I think this is it. Thanks all for the help!

Marco