EXS 24 Logic Sampler Users Group

Now I'm confused - aren't these GUI settings retained when you do a 
"save as instrument", or am I confusing this with something else?  I 
haven't been doing a lot of work with the EXS lately, so I'm a bit hazy 
on the details.
- Lenny

Sascha Franck wrote:

>Paul,
>
>The plugin settings are somewhat "ambivalent" when it comes to the EXS.
>
>In general, everything done in the EXS editor is saved inside the *.exs files. And, on a sidenote, everything done in the EXS editor
>*has* to be saved as recalling a song won't do the job (pretty much as stupid as it could get, especially when you're working with
>"songbased" instruments).
>
>Now, everything done on the EXS GUI is saved along with the song and can be saved as a plugin setting. To avoid confusion (as if
>things weren't confusing enough allready): Nothing done in the EXS editor will be saved with a plugin setting!
>
>In addition, you'll get a third option to apply the GUI settings to the *.exs file (found in the GUIs option menu).
>
>When to save as what is another question and there's some reasons to do it this or that way:
>
>- In older Logic versions there's been a limit of instruments accessable. Should you be using more instruments, saving slight
>GUI-altered variations of existing ones as plugin settings could've been a good idea.
>
>- Not applying any GUI settings to the actual *.exs patch could be of benefits too, as you could adjust the GUI on whatever patch,
>then call up another instrument and the GUI would just stay as it was on the previously loaded patch. Let's say you had a pad with
>some nice modulation settings loaded and wanted to transfer those to another pad - impossible in case the other pad had some GUI
>settings applied allready. Working fine in case there weren't any...
>
>Anyways,  even if the "GUI copy" thing might be useful at times, generally the approach of having different file types for one
>plugin is lame. Just as lame as the fact that you have to save each and every instrument, even if you only plan to use it on one
>particular song. There's no other softsampler requiring such stupid actions.
>
>Regards,
>Sascha
>
>
>
>
>________________________________________________________________________
>EXS Users Group - new web forums! http://logic-users.org/forums/EXS
>- To UNSUBSCRIBE: email exs-users-unsubscribe@yahoogroups.com
>- Search the entire archive: http://logic-users.org/forums/EXS/search 
>Yahoo! Groups Links
>
>
>
> 
>
>
>
>
>
>
>  
>

-- 
=========================================================================
 Lenny Stearns                                     lens@...
 Alexandria, Virginia
=========================================================================

Paul,

The plugin settings are somewhat "ambivalent" when it comes to the EXS.

In general, everything done in the EXS editor is saved inside the *.exs files. And, on a sidenote, everything done in the EXS editor
*has* to be saved as recalling a song won't do the job (pretty much as stupid as it could get, especially when you're working with
"songbased" instruments).

Now, everything done on the EXS GUI is saved along with the song and can be saved as a plugin setting. To avoid confusion (as if
things weren't confusing enough allready): Nothing done in the EXS editor will be saved with a plugin setting!

In addition, you'll get a third option to apply the GUI settings to the *.exs file (found in the GUIs option menu).

When to save as what is another question and there's some reasons to do it this or that way:

- In older Logic versions there's been a limit of instruments accessable. Should you be using more instruments, saving slight
GUI-altered variations of existing ones as plugin settings could've been a good idea.

- Not applying any GUI settings to the actual *.exs patch could be of benefits too, as you could adjust the GUI on whatever patch,
then call up another instrument and the GUI would just stay as it was on the previously loaded patch. Let's say you had a pad with
some nice modulation settings loaded and wanted to transfer those to another pad - impossible in case the other pad had some GUI
settings applied allready. Working fine in case there weren't any...

Anyways,  even if the "GUI copy" thing might be useful at times, generally the approach of having different file types for one
plugin is lame. Just as lame as the fact that you have to save each and every instrument, even if you only plan to use it on one
particular song. There's no other softsampler requiring such stupid actions.

Regards,
Sascha

Lenny Stearns wrote:
> Now I'm confused - aren't these GUI settings retained when you do a
> "save as instrument", or am I confusing this with something else?  I
> haven't been doing a lot of work with the EXS lately, so I'm a bit hazy
> on the details.

The GUI settings are only saved with the instrument after you performed an "apply settings to instrument" for the first time. After
that they'll also be saved along with "save as" actions.

- Sascha

Sasha,
Thanks alot for the explanation.  I would have never figured that out from the manual.  So 
its seems like my best bet if I want to save 'plugin' settings with an instrument, is to use 
the 'save instrument as' command from the options dropdown in the EXS GUI to save 
plugin settings with my instruments.  Thanks again.

Paul