EXS 24 Logic Sampler Users Group

Thoughts from the mind of Ben Hall, 13-11-2002:

>  > >> - Got to the EXS instrument editor, under "Edit > Preferences" setup a
>>  >> command for "next patch", say "PrgChange 01".
>>  >> - Create a sequence containing that very command.
>>  >> - Set a cycle around that sequence.
>>  >> - Go have a day at the beach or so, this will take a while now. When
>you'll
>>  >> be back all your patches should load fast.
>
>For me, this kind of worked, but often when searching for samples or loading
>samples while Logic was playing the cycle, I'd get an audio overload error
>and Logic would stop. So I'd wake up the next morning only to find Logic had
>stopped three instruments into the 2000 or so I'd wanted to process.
>
>A better way for me was to assign a function key to "Next EXS Instrument",
>and simply hold it down. This way, the EXS just starts loading each
>instrument sequenctially in turn, without the complexities of trying to keep
>playing during tons of disk access.

I'm sorry but to me this sounds exactly identical to the proposed 
"cycle" solution.  The point obviously is to have *only* the "next 
instrument" command in the cycle, and not have the exs play any 
"real" midi stuff at the same time.  I used this trick a couple of 
times in the past and it works like a charm.  No overloads or 
whatever.  The only problem that might occur is if you have multiple 
samples with the same name, and the exs asks which one you want to 
use -- then you'll be stuck with a dialog somewhere midway during 
processing.

-- 
Hendrik Jan Veenstra  <h@...>
Omega Art: http://www.ision.nl/users/h/index.html