[MDrummer] Need tipps for sample import strategy

[elassi]

I'm importing some stuff


and face a question I don't know to answer yet.

Have a sample-cd (Latin percussion) that offers three kinds of sets/kits:

1) Percussion sets
Complete kits (e.g. AfroCuban) with up to eight velocity layers per instrument.

2) Instrument sets
Single instruments (e.g. Bongo) but with several playing styles like "open 1finger" or "open 3finger" etc. These playing styles are not available in the other kits (see 1+3)

3) Velocity sets
Single instruments (e.g. Bongo) with less playing styles but more velocity levels (up to 20) than provided in the other kits.

------------------------------

Now the question: how to assign them to MDrummers sample library structure? With the first sets (1) it's quite obvious. These are complete kits and should be treated like drumsets in MDrummer.

But what to do with the other collections? Guess it'd be fine to treat them as components. Or include them to the ready-made drumsets (1)? Since they're more rich in velo layers and playing styles? But there might be double samples then. Or refrain from the drumsets (1) at all and build new ones from the material listed under (2) and (3) only? *scratches head*

To make it even more complex several of those samples have so called "exclusive mode" in their AKAI programs meaning one sample mutes the former (well known from closed hihats disabling open hihats). The CD comes with a PDF so I can clearly identify them. Should I establish the exclusive mode later on or is there a work around by renaming them in a smart way before the import?

Thanks for any hint.

[MeldaProduction]

Whoooo, damn, that was long .

Ok, so I wouldn't make components from them simply because the drumset generator would then add them in all generated drumsets, which I don't suppose you want. So, I'd create separate drumsets from them. Now if to use the automatic sample import, that's a question. But you can always try and see how it works. I mean maybe your library has such a structure, that just won't work. But maybe it will. The importer knows velocity layers and stuff, so it might. But the "closing" that's up to you. I think with the "articulations" you will have to do it manually anyway. You will probably need to set MIDI notes directly and setup the closing. But good thing is that you can always import the velocity layers automatically simply by drag & dropping the set of samples to the drum editor. The rest is up to you what you will think is more convenient.

[elassi]

Whoooo, damn, that was long .

Yeah, I know! Therefore I really appreciate your quick response.

It turns out that I'm going the manual "handcrafted" way in this case.

[MeldaProduction]

That's probably better, your case is a little bit complicated it seems. The automatic import is more for traditional drum samples.