Saving Presets and Banks

[hesnotthemessiah]

I have been using the Scope platform for a few months now but I just cannot get my head round how the Preset/Bank format works in Scope.

How do you save a Preset (Program in VST plugin speak) for a device to it's own folder which is placed within another folder which holds all your other files for that particular song?

Do you have to save a Preset(Program in VST plugin speak) to a bank and then save that Bank to save the Preset?

Can you save/load individual Presets (programs in VST plugin speak)?

Have I got the following right?:-

In the same way that a Bank for a VST plugin is a set of Programs -
So a Preset in Scope is a series of "settings" (no Scope term for these "settings"?).


A Bank in Scope is a collection of Presets in Scope -
No such convention for a VST plugin.

Hope that made some sense! My head hurts.

[Aries]

TRICKS & TIPS :-

Tips and advice for getting the most from Scope. No questions here please.

Should be in PROBLEM SOLVING

John please transfer to PROBLEM SOLVING

[hesnotthemessiah]

Sorry, I thought the replies would be more likely to turn out as tips on how to save settings in presets/banks to your own individual song files and the ways in which other users save their device settings.

[hubird]

weird thinking...

[Frisbee]

Hi Hesnotthemessiah

Have you solved the problematic to save banks and presets?

That´s the way I do it:
I create a new bank and my new preset.
I save preset and bank.
Now I save the whole project.
After reloading the project there will be the right setting.
It is also a good idea to rightclick the presetlist on the first numberentry to get the "autoindex" option.This is quite usefull, because now you can control the presetlist from your sequenzer.

What I don´t know is how to save a device with my selfmade presetlist, so that I can load this device with my own presetlist at any time.
Any suggestions?

Frisbee

[hesnotthemessiah]

Thanks for the tip frisbee. I initially found Scope's bank/preset system confusing. When I use my sequencer (was Cubase VST5 now learning Live 5) I create a song folder then store all my various settings for that song in this song's folder - these can be audio files, Scope project files, Live sets, and VST plugin settings, all of which are given their own folders within the song's folder. Each VST plugin I use would usually have it's own settings stored in it's own folder within the song and, when I feel the need to save any edits, I would access the folder and save the plugin's setting, usually with an incremental name (ie. 1-1 or 1-2 or 2-1 etc.) It does seem a bit pointless to have to create a bank so you can save a Scope plugin's settings - why can't you just save a Scope plugin's current settings to a folder and then reload these settings if needed without having to create/load the bank first? The only use for saving a Scope plugin's settings to a bank, that I can think of, is so that you have the option of program recall via midi - something I have never needed to do myself.

<font size=-1>[ This Message was edited by: hesnotthemessiah on 2005-09-06 21:25 ]</font>

[Shroomz~>]

In this order (in Scope/Noah speak) :

1. Create a new Scope 'project' named whatever.
2. In this new project create a new 'bank' for each of your synths & FX.
3. Create your new 'presets' within your new 'banks', save the presets, then the banks making sure that you're not saving multiple banks at once (ie make sure you only have your new bank loaded for a final bank save. This way you'll be able to load just that bank back up on it's own should you need to.
4. Now save the Scope project.
5. Always make backups of anything you want to keep, coz ya just never know

<font size=-1>[ This Message was edited by: Shroomz on 2005-09-07 02:50 ]</font>

[Shroomz~>]

This might just be personal taste, but i thought it would be worth mentioning that for all intents & puposes it would be easier to keep your Cubase project, midi & audio files in seperate folders from your Scope stuff. What is normally logical, is to have a save folder for each different type of file & simply name them all as per your track name.

Your working on a track called 'bawsack'.
You could have 'bawsack' or 'Bsack' at the start or end of every file name. So, it'll consist of audio tracks BawsackKick.wav, BawsackSnare.wav, BawsackHats.wav, BawsackBass.wav, BawsackPads.wav. Midi tracks BsackDfill01.mid, BsackDfill02.mid etc. Save them all in a Cubase project called Bawsack1.cpr in your normal Cubase projects folder along with your other projects.

Same goes for Scope if you work this way. The essence of the idea is that you can keep all relevant files in local locations where they're meant to be & still call them up for a track by the trackname or abreviation of it used in your project file naming.

[hesnotthemessiah]

Thanks for the reply Shroomz . I just spent half an hour typing up a reply and lost the lot when I was asked to enter my username and password to post it. So I am a bit naffed off at the moment and don't feel like typing it all up again. I am going to bed....................