![]() |
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
| |||||||
| UK Digital Video (uk.rec.video.digital) For the discussion of all aspects of digital video, including all digital video formats, camera use, editing, post production & all associated equipment, hardware and software. Advertising is prohibited. |
| | Thread Tools | Display Modes |
|
#1
| |||
| |||
| I did an OS wipe/reinstall and put my saved presets backs into the presets folder. I saw that I had to actually create a preset for the folder to be created and then saw that a weirdly named file was created at that time (something like "{}" with numbers and letters inside). I saved my presets to both the general presets file and then into that one with the funny name. They just don't show up. How do we get VV4 to recognize these older dxp files, anyone know? Must I "import" them instead of just copying them into the folder? Thanks. |
|
#2
| |||
| |||
| On Mon, 28 Mar 2005 23:06:52 -0500, Traveller wrote: I did an OS wipe/reinstall and put my saved presets backs into the presets folder. I saw that I had to actually create a preset for the folder to be created and then saw that a weirdly named file was created at that time (something like "{}" with numbers and letters inside). I saved my presets to both the general presets file and then into that one with the funny name. They just don't show up. How do we get VV4 to recognize these older dxp files, anyone know? Must I "import" them instead of just copying them into the folder? Thanks. Sometimes I even surprise myself g. Though I didn't have a clue, I kept trying to find out what to do. No documentation anywhere, but I stumbled around and totally by accident figured out what to do. I attribute success to the fact that I happened to create some test presets while the registry was still open and to the fact that I've edited INI files in my time. I happened to see the behaviour in the key, I think it's called, for the presets setting in the registry. I was also in the presets folder so like d'uh, saw that the curly brackets in Windows corresponded to curly brackets in the registry with the same name. The next step was when I looked at the contents in that key and it was just like editing the INI file of my Win3x card program. I played around for nearly an hour but I got the presets to be recognized. My registry skills are extremely rudimentary but I do know how to export to a reg file, which I did, so I saved that now in the zip file backup of my presets. Totally lucky stumbling process but I figured it out. What a relief because I saw a big job ahead trying to re-create the presets. I already had them it was just to get V V 4 to recognize them which is what the reg files does. Thanks everyone. |
|
#3
| |||
| |||
| Traveller wrote: On Mon, 28 Mar 2005 23:06:52 -0500, Traveller wrote: I did an OS wipe/reinstall and put my saved presets backs into the presets folder. I saw that I had to actually create a preset for the folder to be created and then saw that a weirdly named file was created at that time (something like "{}" with numbers and letters inside). I saved my presets to both the general presets file and then into that one with the funny name. They just don't show up. How do we get VV4 to recognize these older dxp files, anyone know? Must I "import" them instead of just copying them into the folder? Thanks. Sometimes I even surprise myself g. Though I didn't have a clue, I kept trying to find out what to do. No documentation anywhere, but I stumbled around and totally by accident figured out what to do. I attribute success to the fact that I happened to create some test presets while the registry was still open and to the fact that I've edited INI files in my time. I happened to see the behaviour in the key, I think it's called, for the presets setting in the registry. I was also in the presets folder so like d'uh, saw that the curly brackets in Windows corresponded to curly brackets in the registry with the same name. The next step was when I looked at the contents in that key and it was just like editing the INI file of my Win3x card program. I played around for nearly an hour but I got the presets to be recognized. My registry skills are extremely rudimentary but I do know how to export to a reg file, which I did, so I saved that now in the zip file backup of my presets. Totally lucky stumbling process but I figured it out. What a relief because I saw a big job ahead trying to re-create the presets. I already had them it was just to get V V 4 to recognize them which is what the reg files does. Thanks everyone. I realize that I'm too late for you now but I found this on the Sony Vegas forum just today. The original post was almost a year old which is why a quick search didn't turn it up :-( Mike 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. |
|
#4
| |||
| |||
| On Wed, 30 Mar 2005 18:40:01 -0500, "Mike Kujbida" wrote: Traveller wrote: On Mon, 28 Mar 2005 23:06:52 -0500, Traveller wrote: I did an OS wipe/reinstall and put my saved presets backs into the presets folder. I saw that I had to actually create a preset for the folder to be created and then saw that a weirdly named file was created at that time (something like "{}" with numbers and letters inside). I saved my presets to both the general presets file and then into that one with the funny name. They just don't show up. How do we get VV4 to recognize these older dxp files, anyone know? Must I "import" them instead of just copying them into the folder? Thanks. Sometimes I even surprise myself g. Though I didn't have a clue, I kept trying to find out what to do. No documentation anywhere, but I stumbled around and totally by accident figured out what to do. I attribute success to the fact that I happened to create some test presets while the registry was still open and to the fact that I've edited INI files in my time. I happened to see the behaviour in the key, I think it's called, for the presets setting in the registry. I was also in the presets folder so like d'uh, saw that the curly brackets in Windows corresponded to curly brackets in the registry with the same name. The next step was when I looked at the contents in that key and it was just like editing the INI file of my Win3x card program. I played around for nearly an hour but I got the presets to be recognized. My registry skills are extremely rudimentary but I do know how to export to a reg file, which I did, so I saved that now in the zip file backup of my presets. Totally lucky stumbling process but I figured it out. What a relief because I saw a big job ahead trying to re-create the presets. I already had them it was just to get V V 4 to recognize them which is what the reg files does. Thanks everyone. I realize that I'm too late for you now but I found this on the Sony Vegas forum just today. The original post was almost a year old which is why a quick search didn't turn it up :-( Mike 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. Thanks so much. I did go the registry export route and did get my templates to work though the font didn't come through. The templates at least give me font size and text and placement, I just have to change the font each time I use one. I probably could re-save, but haven't gotten around to it. Kinda silly having only partial results in a save of the presets, though, eh? I mean, you'd think it would have kept the font correct, too. But this is still much better than when I started after the system wipe/reinstall. Thanks much! |
|
#5
| |||
| |||
| Traveller wrote: snip Thanks so much. I did go the registry export route and did get my templates to work though the font didn't come through. The templates at least give me font size and text and placement, I just have to change the font each time I use one. I probably could re-save, but haven't gotten around to it. Kinda silly having only partial results in a save of the presets, though, eh? I mean, you'd think it would have kept the font correct, too. But this is still much better than when I started after the system wipe/reinstall. Thanks much! Glad it worked for you. I agree that Vegas needs work in certain aspects of it's preset savings. Maybe with Vegas 6? We'll know for sure on Apr. 18 at NAB. I'll be there in person along with several hundred other Vegas lovers waiting patiently!! Mike |
|
#6
| |||
| |||
| On Fri, 8 Apr 2005 20:11:09 -0400, "Mike Kujbida" wrote: Traveller wrote: snip Thanks so much. I did go the registry export route and did get my templates to work though the font didn't come through. The templates at least give me font size and text and placement, I just have to change the font each time I use one. I probably could re-save, but haven't gotten around to it. Kinda silly having only partial results in a save of the presets, though, eh? I mean, you'd think it would have kept the font correct, too. But this is still much better than when I started after the system wipe/reinstall. Thanks much! Glad it worked for you. I agree that Vegas needs work in certain aspects of it's preset savings. Maybe with Vegas 6? We'll know for sure on Apr. 18 at NAB. I'll be there in person along with several hundred other Vegas lovers waiting patiently!! Hi, Mike. I was reading about Vegas 5 and it is much better at saving presets than 4 because it _is_ just a question of saving the preset files themselves, i.e., no need to export the registry entries like in 4 to a reg file to be merged into registry on new installation. That sounds good. Unfortunately, it says that V 5 is for W2K and up and I'm on Win98SE, so it'll be a while before I can upgrade. Still, I find 4 extremely adequate for my needs even with this little registry fiddle. g |
|
#7
| |||
| |||
| Traveller wrote: On Fri, 8 Apr 2005 20:11:09 -0400, "Mike Kujbida" wrote: Traveller wrote: snip Thanks so much. I did go the registry export route and did get my templates to work though the font didn't come through. The templates at least give me font size and text and placement, I just have to change the font each time I use one. I probably could re-save, but haven't gotten around to it. Kinda silly having only partial results in a save of the presets, though, eh? I mean, you'd think it would have kept the font correct, too. But this is still much better than when I started after the system wipe/reinstall. Thanks much! Glad it worked for you. I agree that Vegas needs work in certain aspects of it's preset savings. Maybe with Vegas 6? We'll know for sure on Apr. 18 at NAB. I'll be there in person along with several hundred other Vegas lovers waiting patiently!! Hi, Mike. I was reading about Vegas 5 and it is much better at saving presets than 4 because it _is_ just a question of saving the preset files themselves, i.e., no need to export the registry entries like in 4 to a reg file to be merged into registry on new installation. That sounds good. Unfortunately, it says that V 5 is for W2K and up and I'm on Win98SE, so it'll be a while before I can upgrade. Still, I find 4 extremely adequate for my needs even with this little registry fiddle. g I'd highly recommend upgrading to XP (home or pro) and doing the Vegas upgrade. The power of scripts alone is a major reason to do this. You can upgrade any version of Vegas to Vegas 5 for $200 right now and, if things are the same as last year, the price was only $150 for the first month following the new version release. The rumoured new features coming in Vegas 6 have a lot of us drooling in anticipation:-) Mike |
|
#8
| |||
| |||
| On Mon, 11 Apr 2005 21:34:48 -0400, "Mike Kujbida" wrote: Traveller wrote: On Fri, 8 Apr 2005 20:11:09 -0400, "Mike Kujbida" wrote: Traveller wrote: snip Thanks so much. I did go the registry export route and did get my templates to work though the font didn't come through. The templates at least give me font size and text and placement, I just have to change the font each time I use one. I probably could re-save, but haven't gotten around to it. Kinda silly having only partial results in a save of the presets, though, eh? I mean, you'd think it would have kept the font correct, too. But this is still much better than when I started after the system wipe/reinstall. Thanks much! Glad it worked for you. I agree that Vegas needs work in certain aspects of it's preset savings. Maybe with Vegas 6? We'll know for sure on Apr. 18 at NAB. I'll be there in person along with several hundred other Vegas lovers waiting patiently!! Hi, Mike. I was reading about Vegas 5 and it is much better at saving presets than 4 because it _is_ just a question of saving the preset files themselves, i.e., no need to export the registry entries like in 4 to a reg file to be merged into registry on new installation. That sounds good. Unfortunately, it says that V 5 is for W2K and up and I'm on Win98SE, so it'll be a while before I can upgrade. Still, I find 4 extremely adequate for my needs even with this little registry fiddle. g I'd highly recommend upgrading to XP (home or pro) and doing the Vegas upgrade. The power of scripts alone is a major reason to do this. You can upgrade any version of Vegas to Vegas 5 for $200 right now and, if things are the same as last year, the price was only $150 for the first month following the new version release. The rumoured new features coming in Vegas 6 have a lot of us drooling in anticipation:-) Mike Yeah, well, when I win the lottery ... lol Seriously, can't afford any upgrades at all and my computer does a really adequate job on everything, even editing. It just takes a little longer to re-encode stuff. So I have the computer do all that type of work overnight. One day, though ... |
| Thread Tools | |
| Display Modes | |
|
|