Hello Everyone.
 
This is a topic that has always confused me.
According to the image below, I can save it either inside Cakewalk's preset manager (option #1) or as a file on my computer (option #2)
 

 
I would like to know how I should be saving them and which one is "safer" incase of disaster recovery.
 
In my mind each has their pros and cons:
 
Option #1 Pro:
-easy to just select instead of browsing files on your computer
 
Option #1 Con:
-if computer needs to be reformatted or disaster happens, these are not saved as a flat file (i could be wrong).  is there anyway to use this option and backup the presets?
 
Option #2 Pro:
-If computer needs to be reformatted or disaster happens, if you backup your machine, you can restore these presets as files
 
Option #2 Con:
-Cumbersome when you want to flip through your custom patches.
 
So is there any way to combine the two pros into option #1?  Basically if I use option #1, is there some file on my computer I can backup to restore these if need be?
 
Also is there anything I am missing about these 2 options?
 
Thank You!
Adam
 
 
 

I always save plugin settings with the project rather than globally. Whenever I want to save a plugin setting, I create a sub-folder named "Settings" within the project folder and save it there. Since it gets saved with the project and not on the system drive, it can't get lost in a reinstallation. If I want to re-use it later in another project I know where to find it. I always incorporate the name of the plugin in the saved name to avoid confusion, as there may be several plugin settings saved in the same folder.

Kev999
I always save plugin settings with the project rather than globally. Whenever I want to save a plugin setting, I create a sub-folder named "Settings" within the project folder and save it there. Since it gets saved with the project and not on the system drive, it can't get lost in a reinstallation. If I want to re-use it later in another project I know where to find it. I always incorporate the name of the plugin in the saved name to avoid confusion, as there may be several plugin settings saved in the same folder.

So you are using option #2 correct?
 
Only downside is you cant easily flip through I guess.  Plus loading a sound requires a few steps instead of just picking and choosing.

What I want to know is if there is a way to use Option #1 and back it up somehow so I can import the preset list again into a new install if I ever needed to.

What I typically do is either create a Track template or an FX chain (only need 1 plug in to create an FX chain).
Then I insert the FX chain and right click on it "Extract". This opens the VST preset.
There are a few ways of doing this and I've fiddled with all of them.
 
*The Pros to the FX chain is that you don't need to create a whole track template/ or insert a whole track template just to get a VST preset. You only need to insert the FX chain and extract the plug in to have that preset loaded up.
*Another Pro: the presets will all be in your FX chin directory for easy back up/save options.
*The Cons: it takes 2 or 3 clicks to insert and extract.
 

chuckebaby
What I typically do is either create a Track template or an FX chain (only need 1 plug in to create an FX chain).
Then I insert the FX chain and right click on it "Extract". This opens the VST preset.
There are a few ways of doing this and I've fiddled with all of them.
 
*The Pros to the FX chain is that you don't need to create a whole track template/ or insert a whole track template just to get a VST preset. You only need to insert the FX chain and extract the plug in to have that preset loaded up.
*Another Pro: the presets will all be in your FX chin directory for easy back up/save options.
*The Cons: it takes 2 or 3 clicks to insert and extract.
 

 
Hi Chuck,
 
thank you for that.  does this apply for VST synths though?

AdamGrossmanLG
 does this apply for VST synths though?

Track templates retain the presets of the synth track and the synths settings.
FX chains for plug ins settings

the good thing about the track template is its all there. the track, its synth and other track settings as well like pan and volume. the VST synths presets are also stored within the track template.
Those are also pretty easy to back up and light weight (A few MB's or even KB's.) I have literally hundreds saved on an external drive.
 
Saving the presets as you have outlined in your OP I haven't really done much of. I mean I have with Audio plug ins (Like Waves) but not with synths because I typically choose the template route. So my apology's if im going down a different avenue here, but maybe something to just give you an idea of a different way

AdamGrossmanLG

Kev999
I always save plugin settings with the project rather than globally. Whenever I want to save a plugin setting, I create a sub-folder named "Settings" within the project folder and save it there. Since it gets saved with the project and not on the system drive, it can't get lost in a reinstallation. If I want to re-use it later in another project I know where to find it. I always incorporate the name of the plugin in the saved name to avoid confusion, as there may be several plugin settings saved in the same folder.

So you are using option #2 correct?
 
Only downside is you cant easily flip through I guess.  Plus loading a sound requires a few steps instead of just picking and choosing.

 
Option #2 I guess.
 
This particular method suits me, but it would be less convenient for a user who routinely creates a lot of presets, whereas I only save settings that I believe that I will want to re-use.

For presets in the option #1, use Cakewalk Plug-in Manager (in Utilities menu) to export/import these presets. Tip: you can not only export many presets for one plug-in, you can export all presets for many plug-ins (still with the possibility to import individual presets when required).

azslow3
For presets in the option #1, use Cakewalk Plug-in Manager (in Utilities menu) to export/import these presets. Tip: you can not only export many presets for one plug-in, you can export all presets for many plug-ins (still with the possibility to import individual presets when required).

Hi Azslow,
 
Oh wow, I will have to look at this when I get home!   Thank you.  I didn't think of the plugin manager!  Thanks!