Conkrete wrote:http://audacity.sourceforge.net/
Cross fade your samples to your hearts content with this FREE software. You can simply export your samples from the editor software and manipulate them with this software then upload them to the MS with the editor software. If that still takes you more than 30 minutes to create a sample bank then you are just slow at making sample banks with the MS. It's that simple. Problem solved?
I've used this method myself to manipulate samples and create banks for the MS so I know it works and can be done quickly. These two programs can run simultaneously on my PC so I see no reason why this should be a difficult task for you...especially with the credentials you claim to have. Now can you please stop posting bullshit?
ADAPT AND MOVE ON.
Nice to know that you post just for the love of it. Let me once again explain what the difficulty is.
I bought the MicroSampler so that I can sample the old, clunky keyboards that are too big/heavy/unreliable to be worth the trouble when I sit in with friends to lend a hand with a live overdub recreation.
If I sample one key from my Elka's leslie'd out, warbly and supercool organ sound, and scale it across the keys, the speed of the vibrato/leslie changes, speeding up and slowing down as move from key to key, in addition to the artifacts caused by what I'm guessing is the pitch/time transposition software. Whatever the cause, it doesn't sound good.
So, seeing as my commitment to excellence knows no bounds, I set out to sample
every single key, so that I might better reproduce the Elka, in a convenient package. Perhaps a little OCD, but certainly within the limits of the hardware.
Now, in order to get this to work, and have a separate sample on each key that plays as long as the key is held down, this is the process involved:
1) record sample into Reaper
2) splice together a loop of not more than 5 seconds, due to MS memory restrictions in a time when storage is practically free (at least 4 g SD cards are $10). by the way, this involves:
1. selecting a 7 or second chunk of the sample
2. splitting the selection in the middle on a zero crossing
3. re-aligning the front part of the sample to become the back part of the sample, and the back to front
4. crossfade
5. test for pops
6. if no pops, extend back of unrendered loop 2 complete waves, so that the sample loops first two completed waved are duplicated on the front and the back of the sample loop
7. render loop
3) drag loop into Korg editor
4) use editor to trim off the first and last waves (as yet, the only way that I have found to reliably eliminate pops on playback)
5) send now functioning loop to microKorg via USB
6) repeat process for next key.
This is a lot of work, whether or not you think I am doing it quickly enough. Also, note
that I have already figured out a workaround.
Note that I am not complaining about anything involving the microSampler itself- not gripes about not enough memory, that the a/d isn't good enough, that the keys are too small, that there are too many submenus. All I am saying is that if the software
that I am running on a dual proc tower that is powerful enough to handle 32+ tracks of 44.1K 24bit audio had a crossfade tool built in, the process would go something like this:
1) Record sample directly into microSampler (because I think the A/D is actually quite good)
2) Trim and crossfade samples in PC based editor
3) Enjoy myself, and tell all my friends what a treat the microSampler is.
Again, as with a few other people who have been kind enough to scold me for asking for some basic, easy, and fairly standard functionality on the editor/librarian software-
What is your point? That a crossfade won't be useful? That Korg doesn't have the technology to write software that crossfades? That you don't want a crossfade tool, because it will make things too easy?