EXS 24 Logic Sampler Users Group

> Ohw, that's by far the worst suggestion I could imagine...  So if 
you 
> have a 250 MB piano and make 5 variations of it, you would end up 
> having 1.25 GB of data???  Not a very nice idea.
> And then you discover that the "C3 mf" sample has a small 
transient 
> spike at the end which you'd like to edit out... but you now have 
to 
> perform the same edit 5 times instead of only once...
> IMO there's nothing wrong with having samples and "sample mapping 
> files" (instruments).  I do agree though that EXS file management 
and 
> esp. navigation could (and should) be improved massively.

Think this through a bit more before dismissing the suggestion out 
of hand.  You wouldn't need to duplicate a 250 MB piano five times!  
You would just store all the variations within the Instrument / 
Sample file the same way you can with Soundfonts.  This would be 
much more convenient since all your variations would be stored 
within one file for easier file management and portability.

Also, it would be really simple to implement a "sample edit" button 
within the EXS editor so that a sample (your C3 mf) would open in 
your editor of choice and get automatically updated.  Sort of the 
way SampleCell used to work.

Anyway, with the new Project Manager, Emagic basically assumes that 
you would WANT to save your Instruments/Samples (and all other files 
associated with the song) with each song.  So you're probably going 
to duplicate that piano anyway.

I don't think my suggestion is completely daffy as this is the 
approach Native Instruments is taking with the next version of 
Kontakt.  You'll still be able to organize your library the old 
(i.e., lame) way, but you'll also be able to save a complete multi 
and all its programs and samples in a single file.