MDRUMMER drums 'import' summary UPDATED

[goldglob]

MDRUMMER drums 'import' summary...any comments, corrections?

1, 2, 3 and 4 don’t actually ‘import’ (copy or move) samples but point to their locations on your computer; global or (if defined) custom.

1/ Drag and drop onto Drum Pad (Quick Setup tab> Drum Pad Mode).
If you dragged one file: get one velocity layer.
If you dragged more than one file: creates velocity layers.
Regardless of how many files selected and dragged you will see in MD’s browser all the adjacent files from the (global or custom) directory.
2/ Drag and drop into Drumset Editor
Works as dragging to pads. Select a Drum Type in the Drum List then drag/drop into the list panel (don't have to aim at the highlighted Drum Type). Can also drag/drop into the velocity layers panel.
3/ Import multiple samples as multi layer ( Velocity Layers> Menu).
Does the same as dragging multiple samples to pads.
4/ Main menu> Analyze and import a sample library...creates Drumset files in Drumsets/ Imported (not Samples/ Imported), which when loaded point to the original samples location (global or custom directory comes up), so does not actually import (copy/move) the samples.

5 and 6 below actually import (copy) samples to MD’s factory Samples/Imported folder.

5/ Drumset Editor/ Toolbar/ Advanced/ Import sf2 etc.
This extracts all the wavs from the sf2 and places them in MD's factory Samples/ Imported/ in a folder with the name of the sf2 . That's all this does; no velocity layers or MD drumsets are created. Info says imports a drumset, but this just means imports all the wavs in the sf2 drumset.
6/ Load an archive:
An MD Drumset can use factory samples and/or non factory (global or custom) samples. When saving a Drumset Archive ALL the samples used are stored (copied into) that archive. When loading that archive, non factory samples are imported (copied) to factory/ Samples/Imported/...., but for any factory samples present when the archive was saved , MD now just points to the original factory directory.
Note that non factory samples imported like this from an archive will appear in MD’s sample browser in Factory/Imported/long string of numbers/then a nominal reference to the last bit of the folder tree from which they were originally gleaned/ then the wavs.
The ‘long string of numbers’ folder distinguishes archive imports from sf2 imports, and the actual string of numbers seems to be unique to the computer on which the archive was saved.
The nominal reference to a folder tree is not an actual folder tree (the archive may well have come from another computer).
7/ MSubSampleSynthesizer> Generate.
Generates a subsample library from multiple samples. The wavs are imported but embedded in a mdSubSampleLib file; you don't see the wavs, just the name of the library file.

[elassi]

Thanks a bunch, goldglob!

I've marked your post for later use. Don't have the time to check it now but I'm sure it'll help me sooner or later.

[MeldaProduction]

Very well, that covers it I think . Too many options... the problems have already been fixed, update should be there soon!

[goldglob]

Excellent.

[goldglob]

MDrummer 6.01 just hit the shelves so I've edited my OP to describe the current position (the bugs I had mentioned are fixed).