Just bought and installed a new 80GB drive which will be used exclusively for Vegas work, separate from my system HD. After everything was all up and running, I copied the folder with all my Vegas data (project subfolders containing *.veg files and associated wav files) to the new HD. I assumed the paths for the wav files would be relative to the veg file, but after loading up a project on the new HD, I noticed that the wavs for the individual tracks were still referencing old drive. I opened the veg file into a text editor and did a find/replace to change the drive letter, and all worked fine after that.
The reason I assumed the paths would be relative was because I’d been given Vegas projects on CD from a buddy (same version as me, I believe), and everything worked when the veg files were opened and read directly from the CD... I asked him about this and he said he’d done nothing special with the file paths except copy them the same way I did. There doesn’t appear to be any settings in Vegas to make file paths relative – the only thing I know of is the absolute file path setting under the “Audio/routing” tab in the session properties.
What am I missing here?
Thanks
-momo
Vegas 1.0
P4 1.8 GHz
Win 2K
80 GB Maxtor 7200 rpm HD
The reason I assumed the paths would be relative was because I’d been given Vegas projects on CD from a buddy (same version as me, I believe), and everything worked when the veg files were opened and read directly from the CD... I asked him about this and he said he’d done nothing special with the file paths except copy them the same way I did. There doesn’t appear to be any settings in Vegas to make file paths relative – the only thing I know of is the absolute file path setting under the “Audio/routing” tab in the session properties.
What am I missing here?
Thanks
-momo
Vegas 1.0
P4 1.8 GHz
Win 2K
80 GB Maxtor 7200 rpm HD