MDrummer questions and requests

[TFF]

Started playing with importing my own samples into MDrummer. I'm not clear about some things, and have a couple suggestions about others.

First, the questions:
1) Does the "Generate complete drumsets from different sources" function include components from all folders, or just other folders in the imported folder?
2) A lot of times, when I load an imported drumset, all the drums come up with name and directory undefined. Is this normal? I've noticed sometimes when I generate new drumsets, one of the drums may be from my imported folder, and will have name and directory correctly identified.

And requests:
1) It would be nice to have an option to change how generated drumsets are named. Currently it seems each drumset is named as a list of each file used in it. This isn't useful for locating sets. It seems more intuitive to me to just remember you like how "Concussor 6" sounds rather than "ASOLKICK06+ASOLSNARE03..."
2) The name recognition system is nice, but it can be a pain if you have oddly named files. For instance, a sample for an older, simpler machine might be labelled "click". I could change the name recognition rules, but maybe for one machine, "click" means snare, and for another it means hat. Not to mention, it's time consuming. And if I forget to clear out my changes to the recognition system between imports, I could end up with some samples imported incorrectly. So, my suggestion: when the "unrecognized files" window comes up, let us set their category manually. Say, if the list of recognized kick samples is shown, double-clicking an unrecognized sample will categorize it as a kick.

[MeldaProduction]

Started playing with importing my own samples into MDrummer. I'm not clear about some things, and have a couple suggestions about others.

First, the questions:
1) Does the "Generate complete drumsets from different sources" function include components from all folders, or just other folders in the imported folder?

Only the set of data being imported is used. Generally you don't need to generate drumsets at all, because the components will be used afterwards everytime you press the "generate" button in the main screen. But it may be useful if your sample library is already "consistent", like just samples for a certain style.

2) A lot of times, when I load an imported drumset, all the drums come up with name and directory undefined. Is this normal? I've noticed sometimes when I generate new drumsets, one of the drums may be from my imported folder, and will have name and directory correctly identified.

What do you mean by "name and directory undefined"? I doesn't work?

And requests:
1) It would be nice to have an option to change how generated drumsets are named. Currently it seems each drumset is named as a list of each file used in it. This isn't useful for locating sets. It seems more intuitive to me to just remember you like how "Concussor 6" sounds rather than "ASOLKICK06+ASOLSNARE03..."

Yes, but how could this be done? In most cases people import like their whole samples collection, thus thousands of samples, naming each manually is basically impossible.

2) The name recognition system is nice, but it can be a pain if you have oddly named files. For instance, a sample for an older, simpler machine might be labelled "click". I could change the name recognition rules, but maybe for one machine, "click" means snare, and for another it means hat. Not to mention, it's time consuming. And if I forget to clear out my changes to the recognition system between imports, I could end up with some samples imported incorrectly. So, my suggestion: when the "unrecognized files" window comes up, let us set their category manually. Say, if the list of recognized kick samples is shown, double-clicking an unrecognized sample will categorize it as a kick.

The same trouble I'm afraid - imagine you import a big collection, there may be hundreds of these "problematic" samples. I think it's better to rely on sanity of creators of the sample collection . Don't know, maybe it could be done, but that's a lot of work for both of us. There are so many samples available everywhere, it seems like it's better to just ignore the weird ones.

[TFF]

I hadn't considered the issues you brought up, since I've just been importing my samples one drum machine at a time. I understand what you mean now. Although for naming kits, what I was thinking was to just have it based off the name you enter on the first page of the analyzer dialogue. Obviously that still wouldn't be great for large folders, so maybe it could be optional.

What I meant by my second question is that if I load a drumset generated during sample import and open the designer tab, each drum will say
Directory: Undefined
Name: Undefined
instead of the actual directory and file name. This also happens most of the time when I hit the generate button on the quick setup page. Mostly the imported samples show up undefined, but sometimes the actual name and directory are shown.