Hey guys . Is anyone using autosampler/decent sampler to either port over hardware sounds or even to sample VSTS to reduce size ? . I watched Marty Wades videos on this subject but no matter what i do i can’t get the sampled sound to sound like what is being sampled. I asked this question on the Facebook page and Marty even replied and we conversed about it and even he was at a loss after suggesting a few options to try. I could understand if big synth sounds made up with multiple vsts and effects didnt turn out quite right …but even just simple sawtooth sounds seem to lose a lot of “body” and add a slight release at the end. ive tried upping the number of samples, different release tail settings etc but the end result always comes back the same… Its very odd. Maybe it’s something simple i’m missing or doing wrong …so hopefully someone might know the answer or can point me in the right direction. I’ve attached a link to the video which i sent Marty which hopefully shows what i mean
I am a bit surprised your question hasn’t solicited more (any?) replies. I guess maybe this feature isn’t used by (as) many people. I am far from an expert on this, basically a newbie, but I have been writing a number of Decent Sampler instruments lately to replicate my hurdy gurdy. It has been far from straightforward and have discovered there are so many “wrinkles” it blows my mind. Anyway, I have discovered that some synths sound radically different at different key velocities. What you are currently doing is capturing (recording) sounds at one velocity. Then when you play the instrument on DS, it’s interpreting the sound through it’s own internal code for the different keyboard velocities you play on the DS instrument. I suspect that just simple autorecording a number of samples doesn’t reproduce the sound that the instrument actually creates at different velocities. The GP documentation alludes to this: “Velocity count - some sounds sound quite different depending on the played velocity, so you can create separate samples for different velocity ranges (e.g. use one sample for velocities between 1 and 10, another sample for velocities between 11 and 20, etc.). The upside is that you get more accurate samples for different velocities. The downside is that you create multiple wave files (in fact, this is why some sample banks are so huge; they have each note sampled at almost every velocity value). Most modern samplers support multiple velocities for the same note.” I haven’t tried this myself, but have seen these velocity layers used in some of the Decent Sampler libraries I’ve looked at using the Files>Developer Tools>Preset Editor (Beta). Or, you can open the preset file using a text editor like Sublime. Unfortunately, at least that’s the way it seems to me, how to use many of these features in DS aren’t in the available documentation. The good news is that you can usually open and see the xml code for free instruments available though the DS Library and figure it out. It’s also often very similar to what you can do with NI Kontakt, which means there might be a YouTube video on the topic for either DS or Kontakt. Anyway, my 2 cents worth based on my limited experience. Good luck!
In Decent Sampler you have a release, this is not in the original.
Try sample again with a much shorter release time.
Or take a look at the preset and adjust the release time used.
First of all, a lot of questions get asked and the bandwidth isn’t always there immediately for answers.
But I’ll speak briefly from the perspective of the developer of that particular tool. We can basically provide mechanism that allows you to automatically create a collection from samples with control over such things as the overall length, the range, the number of samples for the same note with different velocities, etc. And of course with gig performer, you can construct some very interesting sounds to be sampled by interconnecting multiple plugins.
What we can’t really do is tell a user what they need to sample for their particular sounds as it totally depends on the kind of sounds, how they will be triggered, and so forth.
@dhj Thanks. It’s interesting. When I first started messing around with DS and the GP tool for creating a DS preset, it didn’t take long to figure out that it provides just the start of the process 
and it has been a real education. And as you say, the ability to construct interesting sounds from interconnected plugins is unique, as is the XML code generator. I very much appreciate the time and effort you guys put into these things!