Preserving custom render templates after new install of Windows and Vegas 4

teknal wrote on 5/15/2004, 9:14 AM

Hi Everyone,

It's time for me to reload windows and all my software onto a new hard drive but the biggest problem I keep running into is having to set up my custom rendering templates. Does anyone know of a tool or a way to preserve these so that I can just load them back after installing Vegas 4?

Thanks!

Comments

SonyTSW wrote on 5/15/2004, 4:56 PM

For Vegas 4 and other older apps that use the Sonic Foundry registry hive (Sound Forge 6, ACID 4, and earlier versions), use the following instructions. Please note this is not trivial because it involves both the registry and files on disk you'll need to back up. I am assuming that you are familiar with the registry editor. The usual disclaimer about running regedit and messing with the registry applies here -- if you're not comfortable working with regedit, don't do this.

1. Run regedit on your current computer, and export the following key (it will be saved in a .reg file)

HKEY_CURRENT_USER\Software\Sonic Foundry\FileIO\Templates

2. Open the exported .reg file in notepad. It lists the paths for all of the template files on disk. Backslashes in pathnames are shown as two backslashes ('\\').

3. Back up the exported .reg file and every one of the .sft files that are listed in the .reg file.

Note: You may need to turn off the Windows explorer setting to hide file extensions and enable the setting to show hidden files and folders to see these files.

4. To restore the templates on your new machine, copy each of the backup .sft files to their appropriate path as pointed to by the .reg file. Install Vegas, and then import the backup .reg file.

Backing up and restoring your templates is much easier for new Sony applications such as Vegas 5 and Sound Forge 7. When we switched to a new registry hive for the changeover to Sony, we were able to remove the registry dependency. We couldn't do this before this as we needed to maintain compatibility with legacy applications.

Here's how to preserve your custom render templates for those and future Sony applications:

1. Back up all of the files under the following parent folder (it may easiset to zip these up into a single .zip file), where <username> is your login name.

C:\Documents and Settings\<username>\Application Data\Sony\File Templates

2. On your new machine, unzip or restore them to the same path.

Note: You can use this technique to copy templates for Vegas 5 to other user accounts. Just make sure they preserve the same file structure.

Ben wrote on 3/30/2005, 10:32 AM

>> Backing up and restoring your templates is much easier for new Sony applications such as Vegas 5 and Sound Forge 7. When we switched to a new registry hive for the changeover to Sony, we were able to remove the registry dependency. We couldn't do this before this as we needed to maintain compatibility with legacy applications. <<<

Resurrecting an old thread, but does anyone know how to do this? Specifically though, I'm not just talking about render template, but pretty much every setting in the sofrware. I know about Preset Manager, but I have Vegas and Soundforge with loads of settings and prefs that have built up over the years, many of which aren't covered by Preset Manager - this only covers plugs.

I want to bring all those settings over to a new PC with a new Windows installation - if anyone knows how I can do this it would be really, really appreciated!

Many thanks

Ben

cyanidekid wrote on 3/30/2005, 10:49 AM

Or you could transfer the whole shootin' match to the new drive with Norton Ghost, or another "clone" program...

Ben wrote on 3/30/2005, 11:08 AM

Unfortunately can't - I'm moving from an Intel-based PC to an AMD one; tried moving the drive with repair installs of XP, etc - Windows won't have it and BSODs on me. So am forced to do an install from scratch.

Would some sort of registry import work?

As pro apps, we really need an easy way of exporting Sony's software settings.

Any ideas guys?

Thanks

Ben

Ben wrote on 3/31/2005, 2:53 AM

Bump. Anyone?