Drum samples CD directory structure

[Farview]

Say someone was putting out a CD of single drum hits in wav format for use with aptrigga, sound replacer, etc... and each drum was sampled with 4 different levels (types) of processing. Which would be a better file system layout:

Root -> type of drum -> specific drum -> type of processing ----> samples
------ (kick, tom, etc) -- (24' tama ) --- (EQ'd, compressed, etc..)

or

Root -> type of processing ---> type of drum --> specific drum -> samples
------(EQ'd, compressed, etc..) (kick, tom, etc) -- (24' tama )

There is no way around having dozens of folders and sub-folders, which would be more convienient?

 

[ThaArtist]

I really dont know so please excuse my post if you find it irrelevant but I am having the same problem with my samples, sounds, and packs. I can't figure out if I should just leave them in their "packs" or discect them and assemble them by instrument cause I have SOOO many I get lost! But I just don't know whats the best directory structure so I'm also curious what any or everyones reply will be.

I'd say go with the first one because from my own experience I want to be able to find the instrument I want first and then see what I have to deal with. So if I'm looking for a snare drum that sounds a specific way I was to simply go into a snares folder right away. And then further chooose my options...

I guess this is just like all other things, we have to debate which option outweighs the other options based on which users would prefer.

Or simply finding out who your users are, if you have a targeted audience and you know that will be your main audience then I'd arrange it for whats most helpful & useful for a person that does "whatever they do" in their specific field of interest.

But this is complicated. Its almost like creating a marketing plan. haha.

 

[ocnor]

The first way sounds the most logical to me.

 

[Ford Van]

#1 works for me. Far more logical.

Are these going to be random multi-samples?

 

[Dogman]

I'd say first, as people probably want to choose by drum first, then find the processing. Going by processing would seem a bit slower, to me.

 

[Farview]

#1 works for me. Far more logical.

Are these going to be random multi-samples?

The program playing them back will determine if they are random or not. There are multiple velocity layers with multiple hits. The snares will have 4 different types of hits as well, (center, off center, rimshot, sidestick) all with multi-layers with multi-samples.

 

[Ford Van]

Ok, multi-layer multi-samples. I get it.

Not sure how you would address the next thing I am going to say.

Sometimes, when I am in speedy pursuit of a kick drum sound, I of course need to try SEVERAL kick drums to find the one that I think will fit my production that best.

It seems like it might be cool to have an additional folder that is just ONE sample of the drum/processing that a guy could go through to sort of preview, in an overall way what each drum/processing applied would sound like. Don't need multi-layers or multi-samples of any of the different drums, just a sample of each kick, snare, tom, etc....

You get what I mean?

 

[Farview]

That's a really good idea. It will also cut down on the time it takes to find samples for apps that don't take advantage of the multi-sampling.

 

[Ford Van]

Heh...this just probably ADDS to the complexity of putting together a folder structure. Sorry.

 

[Dogman]

I'd say first, as people probably want to choose by drum first, then find the processing. Going by processing would seem a bit slower, to me.

Hey, thanks for the Neg rep Ed.

 

[Ford Van]

Hey, thanks for the Neg rep Ed.

Actually, it was a mistake. Sorry.

 

[Farview]

Heh...this just probably ADDS to the complexity of putting together a folder structure. Sorry.

Not at all. In the directory up from the samples, I will just take one copy of each set and put them in there with the names corresponding to the folders they are found in.

 

[Ford Van]

Not at all. In the directory up from the samples, I will just take one copy of each set and put them in there with the names corresponding to the folders they are found in.

Sweet! That would certainly make putting together kit's in FruityLoops a lot faster for sure.

 

[gullfo]

could include XML with metadata... that would make searching and sorting fairly easy even just using a browser... someone could then listen to the sample to determine if it was the right one before importing it into their sampler or whathaveyou...

 

[Dogman]

Actually, it was a mistake. Sorry.

For real? If so, then I appologize....

 

[Farview]

could include XML with metadata... that would make searching and sorting fairly easy even just using a browser... someone could then listen to the sample to determine if it was the right one before importing it into their sampler or whathaveyou...

I'll have to look into this. Thanks.

 

[Ford Van]

For real? If so, then I appologize....

My fault entirely. I need to pay attention to what I am clicking on in the future.

 

[Farview]

could include XML with metadata... that would make searching and sorting fairly easy even just using a browser... someone could then listen to the sample to determine if it was the right one before importing it into their sampler or whathaveyou...

How would you make that work with multi-samples? Each snare drum will have 48 samples (different velocities, different types of hits) There are bunches of individual wavs that are (for the most part) the same. They are meant to be a set of wavs per drum instead of one wav per drum. The toms and the kicks only have 15 samples each (multisamples, different velocities)