I have a couple questions about how MDrummer references samples.
1. Say I have one machine with the factory library installed to /Volumes/Samples/MDrummer and another machine with it installed to /Volumes/Libraries/Melda. If I create a project on one machine and open it on the other, will MDrummer correctly find the samples? In other words, does MDrummer store references relative to the factory library path, or are the references to absolute paths on disk?
2. When adding samples to MDrummer, does it copy them to its own library (and if so, do these samples behave the same as above) or does it store references to the original file paths?
Thank you
Questions about Mdrummer sample references
-
- KVRian
- 975 posts since 10 Jan, 2007 from London
From my notes:
1, 2, 3 and 4 below don’t actually ‘import’ (copy or move) samples but point to their locations on your computer.
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 of the source 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 , 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 samples. When saving a Drumset Archive ALL the samples used are stored (copied into) that archive. The archive can be saved to any location on your computer. 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. The archive itself remains intact.
...............................................................................
7/ MSubSampleSynth> Generate.
Generates a subsample library from multiple samples. The wavs are imported (copied) but embedded in a mdSubSampleLib file; you don't see the wavs, just the name of the library file.
8/ Multisample Generator creates samples from longer audio files and saves them to the factory MultiSamples folder.
9/ Installing 'packs' or 'products' involves samples and settings being integrated into the MDrummer data folder.
1, 2, 3 and 4 below don’t actually ‘import’ (copy or move) samples but point to their locations on your computer.
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 of the source 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 , 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 samples. When saving a Drumset Archive ALL the samples used are stored (copied into) that archive. The archive can be saved to any location on your computer. 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. The archive itself remains intact.
...............................................................................
7/ MSubSampleSynth> Generate.
Generates a subsample library from multiple samples. The wavs are imported (copied) but embedded in a mdSubSampleLib file; you don't see the wavs, just the name of the library file.
8/ Multisample Generator creates samples from longer audio files and saves them to the factory MultiSamples folder.
9/ Installing 'packs' or 'products' involves samples and settings being integrated into the MDrummer data folder.