So I am curious!

What is your approach when developing a Sample library. Many different ways on specific libraries such as a single instrument or a big bank of sounds but what do you feel comfortable doing?


Do you brainstorm a GUI/Script first?
Think of the library name?
What instrument will I use?
How long should I spend on the project (or on certain parts / GUI / Script / Mixing)?
Hire someone? Get help from a friend?


Personally, I would first brainstorm a few libraries/companies that have been successful with products. What is so unique with the libraries that made everyone use them, flexibility and how easy+simple it is to use. I like asking a few friends what they would love to see in their library collection. (Just the first simple step)


I would love to hear your first step to planning is! Even if you don't ever want to spend time on creating a bank of sounds for yourself/others to use, what would you do first?

 

My first step was always deciding what to sample and then how many takes.
Then what room to use (not many choices here)
And finally when to do it and how (portable recorder or audio interface/microphone configuration/other specifics)

 

Getting good quality samples recorded first with variations etc or whatever u gonna use for say synthesis as this will dictate the nature of the script u need to write.

U could of course be making some kind of virtual synth so u need a load of waveforms or whatever.

The GUI/Script/Name lol can B great but if the samples rubbish then it ain't much good

 

First of all: Whatever instrument or genre it is, make it sound fantastic!
Many potential users will compare your library side-by-side with the best libraries available, so you better have something that will either add to them or supersede them in some way.
That's the only reason that usually makes me wanna buy a sample library.

Take your time to get the concept clear. Don't start sampling and programming before you're there, because proper planning will also influence what you sample, how you sample it, how you post-process and how you'll do the programming.

Also make sure you're not taking redundant or unnecessarily long samples, nobody wants a 10GB sample library that would sound exactly the same if it was only 1GB in size if only recorded, processed and programmed properly.

While recording in 24bit is a *must* IMHO, I'd claim that properly downsampling to 16bit with proper levels and good algorithms will rarely make a sonic difference.
If you really want it big, you're probably better off sampling at a higher rate (above 44kHz) so playback quality will still be OK when using the library in a sampler with sub-par resampling quality settings or even sub-par resampling quality in general.
(This is less of an issue if you sample every semitone and the sampled source is already in perfect tune)

IMHO the GUI supports the function: Ease of use and quick handling without introducing unusual workflows would be my preference. It does not harm if the UI looks nice, but I consider it more important that I can use it easily and efficiently and don't have to ask myself or buddy manual "how the heck do I ...".

 

Some interesting replies guys, keep em coming!

I had a habit of programming before the project planning... It ended terribly...

 

If u have samples & a rough idea PM me & can sort a script out 4 u *yes*

 

That is extremely nice for your offer, at the moment I am having a bit of trouble with creativity and planning at the moment

 

Very few Libs. with a bad GUI are successful.

Something to ponder.

 

I think taking so,ex drum sticks and taking a recorder and banging on stuff with multi layer and round robin would be a cool simple start

 

Just imagine: Brandon's samples, Clandestine's programming, OneReason's GUI + artwork and the work from whom ever feels like adding to it ...
A new Audiosex Sample Library made by members, for members?

 

You know, that'd be an awesome project. I'll have to get my inspiration going again :P