Properties' global change for existing projects

megabit wrote on 6/15/2008, 11:42 AM

I don't have much experience in scripting with Vegas, and guess it's some script I need to achieve to following:

After I added a new RAID 0 to my system, I'd like to move some folders to new locations (like the Vegas renders output dir, temp dir etc). Using Project Properties, it can easily done for all new projects; however, how do I do it for ALL my EXISTING projects? Opening them one by one, changing these properties and saving would be rather tedious and time consuming task....

Any advice appreciated

Comments

Former user wrote on 6/15/2008, 11:49 AM

From my experience, temp directories and such are global. They are not saved as part of a project.

If you have temp folders on other drives, you would need to move those files to the new temp folders, etc.

Dave T2

megabit wrote on 6/15/2008, 12:40 PM

Yeah, OK - temp dir is set in Vegas preferences rather than Project Settings, so it can be changed easily for all sessions, with new or existing projects. But those 2 directories (for video and audio) you set in Project Properties - you can only set them easily for the current or all new projects; any old project will look for the old settings that were in force when the project was last saved; I'd like to change that for all my existing projects in one operation....

Former user wrote on 6/15/2008, 1:11 PM

I think those are global as well. Try changing them and checking the box for START ALL NEW PROJECTS..

Then load an old project, I don't think they will change.

Dave T2

megabit wrote on 6/15/2008, 2:15 PM

They will.

Former user wrote on 6/15/2008, 3:35 PM

Okay, I am using Version 6 and have not seen this, but honestly I don" t change my settings so I can't swear to it.

Dave T2

Chienworks wrote on 6/15/2008, 4:33 PM

Each subsequent version of Vegas seems to have gotten fussier and less user-centric about file locations. It could very well be that the design philosophy behind version 6 was 'if the user chooses a directory let's use it', and the philosophy behind version 8 is 'we know better than the user, so ignore global changes and make them do the work every time if they think they have a clue'.

Ok, that's a bit spiteful i realize, but things seem to be drifting worse for file and directory handling with each new version.

megabit, perhaps just waiting until the next time you open each project to make the change wouldn't be too huge a burden. If you're talking about a very large number of projects, how many of them are you going to reopen in the near future anyway?