The definitions of "layers" is getting me confused. When you watch the you tube video on auto mapping they ask how many layers he wants for the snare drum. He chose 16. When he auto mapped there was still velocity 1-127 but that was separated into 16 groupings or "layers". Isnt every instrument going to have a 1-127 range regardless of how many layers you use? I thought the amount layers determined the depth and dynamic range while 1 was the minimum and 127 was the maximum of the range.
The OP never responded so unknown if it was 16 samples or 100+ samples mapped to 16 velocity "ranges".
Hopefully the latter.85MB is a lot for a snare.
You could auto-map a round robin to just one 0-127 range if you want to.The two Powerstation kits are like that , especially the hi-hat.
I use the 127 auto mapping because I can build kits with 1,000 samples under the 200mb limit and utilizes both layers and dynamics per zone.The more ranges gives the ability to be more precise/specific when adding/replacing samples to ranges and create unique instruments.
I have converted my studio into a sampling studio for the past 8-10 months and bringing in drummers/kits specifically building a data base for the STRIKE module.A lot of them are cover/Tribute bands and I get to sample various brands/manufactures and in exchange along with some studio time I also "tune" their kit's and outboard gear according to the band/group/album there are trying to duplicate which is also helpful to create "Artist' presets
The STRIKE module has some unique features and you can create/isolate your own velocity "ranges" then put a sample into it that has entirely nothing to do with a drum sample.It will sound only when that velocity range is struck.You can also move different velocities into different ranges.
I think the term "layers" gets misinterpreted or overused and is determined by it's application.
I see it used frequently in different areas of music production.
Over the years it was common for piano/keyboard as one velocity sample was one layer..some samples are multi-layered or multiple velocity.I myself got into the habit of using it also from guitar modeling,multi-tracking,sample building etc.
I see it referred to constantly in drum samples.
As far as Alesis drum modules go...
There are Drum modules that have more than one Instrument/group of sample(s) that make up a zone.
The STRIKE has two "layers"..A and B...per Zone
The "layer" consisting of single or multiple samples/velocities or as in the case of the STRIKE..a single instrument file(.sin) links to the location of the sample(s). The samples do not need to be in the same folder.
When using auto-map you are creating an instrument/file linked to a single sample or multiple samples/velocity "ranges" that are "listened to" and sorted by the module.
Since each "layer" can have up to 127 samples/velocity "ranges".. you can have over 250 samples per Zone.
You can then control the dynamics between the two "layers".
Edit:
The Auto Map feature detects the "perceived" loudness of the sample(s) and favors creating the most natural-sounding instrument possible.
I have found it to be not as accurate as claimed as samples that are originally numbered/divided into velocities are not found in that velocity folder.I have used normalized and non and still find samples scattered in a range of velocities.
Auto Map an internal kit such as the PS kit snare "PS Taye MapleSnHd Amb 1" and you will see .010-.013 velocity ranges in the 67-72 range and velocities of .032-.036 in the 97-102 range..etc.
Still a lot of bugs in the editor..including graphics overlaying on top of each other,text cutoffs.
On a positive note as far as creating instruments...40+ character sin files are supported..
The only downside is the UI screen/graphic partially covers under Voices.
Probably the reason why the editor won't allow above 30 (26 +file extension)
If Alesis would get rid of the knobs and go with sliders it would be viewable.
and the STRIKE module does support a 128GB SDXC card...that's a lot samples.
The downside is the STRIKE Editor takes 1min-1 1/2 mins to load per 100,000 samples..which is about what I have been getting on a 32GB card