Hello,
I started trying the Meldatools and so far I found them quite powerful albeit somewhat confusing...
Is there anyone here that can explain the differences and subtleties between the four options in the Sample Library Analyzer from MDrummer?
Generate components:
In my understanding it creates a component for every sample it found matching the sound type (ie: Bass Drum, Snare Drum...) However, I'm not sure how it works for more complex components like Hats (Open Closed, Pedal...) there some kind of generation happening here I believe. More details on that are welcome.
Generate components from different sources:
I'm in the dark here, It creates new components called Random XXXXX but where does the randomization happen what is this option doing?
Generate complete drumsets:
This I tested and had alternating behaviors, sometime it creates one or more drumsets sometime it does not. I believe it has to do with the number of different samples kind found (ie if its missing hats it can't create a drumset?) or maybe it has to do with the folder structure in the root folder selected in the first panel of the import tool?
Generate complete drumsets from different sources:
This has the most "consistent" behavior for me in the way that it mix/match sample to create complet drumsets. But as far as I saw it only use sample found in the root folder selected in the first panel of the import tool? What are these mentioned "different sources"?
Another thing I noticed. If I import a sample library and it creates components. I want to be able to go in the quick drumset designer and select a component (say bass drum 01) then browse for imported/libraryname/bassdrum 01 for example and then click the right and left arrow to quickly scroll through the available options... But no! It brings me back to the first Analog folder.
Also, the Directory and Name fields for the components are quite revealing and I'm not surprised the quick browsing fail because they are set to Undefined
Any input on that as well?
Thanks for every bit of information you can provide.
Best regards;
MDrummer Import Sample Library - Generate ... from different sources?
-
- KVRer
- 10 posts since 25 Mar, 2009
-
- KVRian
- 975 posts since 10 Jan, 2007 from London
Excellent questions.
I think you're on the right track with the 'other folders' thing. They really are just other sub folders in the directory you point to (but yes, the MD info is unclear).
I tested all this about 3 years ago. From memory I think it works like this:
Point the analyser to folder DRUMS.
Inside DRUMS are sub folders KIT 1 and KIT 2.
With 'different sources' OFF, you'll get drums generated from Kit 1 AND drums generated from Kit 2.
With 'different sources' ON, you'll get drums generated using samples from either or both Kit 1 AND Kit 2.
The arrows should work, should only go back to analogue once you've scrolled through all components (not that you'd want to do that).
Re the 'undefined' in designer:
Components are only defined when there is a drumset loaded that uses them. Bear in mind that you can create a drumset and save it without using 'components' and without saving any of its elements as components.
I think you're on the right track with the 'other folders' thing. They really are just other sub folders in the directory you point to (but yes, the MD info is unclear).
I tested all this about 3 years ago. From memory I think it works like this:
Point the analyser to folder DRUMS.
Inside DRUMS are sub folders KIT 1 and KIT 2.
With 'different sources' OFF, you'll get drums generated from Kit 1 AND drums generated from Kit 2.
With 'different sources' ON, you'll get drums generated using samples from either or both Kit 1 AND Kit 2.
The arrows should work, should only go back to analogue once you've scrolled through all components (not that you'd want to do that).
Re the 'undefined' in designer:
Components are only defined when there is a drumset loaded that uses them. Bear in mind that you can create a drumset and save it without using 'components' and without saving any of its elements as components.
-
- KVRer
- Topic Starter
- 10 posts since 25 Mar, 2009
Thanks it starts to be clearer now.
I believe the tool has been conceived for the sample to be organized in a folders tree where all the sample relevant for one kit are "together". Which is not how I organize my samples (more like one folder for hats, one for kicks, one for snare, etc...)
So that would explain why its only able to generate kit using the "random" option (it can't create a kit using only sample from one folder, it would only found hats or snares...) and also why random had no effect on the components' generation (all the sample relevant for the "randomization" process for said component are already in the same folder so it won't find any compatible sample in other folders)
I'm going to start organizing my sample folders this way and build from there.
Anyway thanks for your input.
Have a nice day.
I believe the tool has been conceived for the sample to be organized in a folders tree where all the sample relevant for one kit are "together". Which is not how I organize my samples (more like one folder for hats, one for kicks, one for snare, etc...)
So that would explain why its only able to generate kit using the "random" option (it can't create a kit using only sample from one folder, it would only found hats or snares...) and also why random had no effect on the components' generation (all the sample relevant for the "randomization" process for said component are already in the same folder so it won't find any compatible sample in other folders)
I'm going to start organizing my sample folders this way and build from there.
Anyway thanks for your input.
Have a nice day.