This is very helpful, thank you. I use an MPC and have access to the hardware and software autosampler - but your explanation of the workflow is superb.
@@IanDixonTDLI’ve bought an Arturia Microfreak and love the raw sounds. I am going to sample some of the oscillators and bring them into the Modwave and MPC.
Thanks Ian That's a pretty good solution using the MPC I have a Cubase template - and then use Wavelab to add loop points and trim excess. If the samples are named correctly in the folder - I can simply drop them into the Korg sample utility - and it maps then automatically. ( you might have covered this already in your video ) I use a Wavestate and Modwave live And can use the 4gB's of memory in each synth to cover everything. Which means I don't have to stress about my laptop crashing or getting confused. I've sampled all of my cool VSTi's from U-he, Steinberg, Synapse, N.I., Steinberg etc Cherry-Audio VSTi's work particularly well - especially the GX-80 These sound epic live and have greater control within the Korgs with their real-time modulation options.
@@IanDixonTDL Wavelab has a function called loop tweaker. If you're bringing in samples that have previously been looped - it has a few tools that help find those probable loop point sections. And if you're creating your own loops - it has a few cross fading tools that let you quickly create suitable loops. Much easier and quicker than the Korg Loop Finder. Additionally it also has a Tone Uniformizer for when things get really difficult. However, this works best as an experimental looper - often creating unexpected yet sonically rewarding results.
Hi Ian, great vid, but as a player for a loooong time i kinda need to ask what might be a completely needless question, but why sample in the first place? if you are a studio player just play the source the only reason i can think of is you want to sample the sounds to your wavestate and take one synth out on the road, is there any other reasons I;m missing? Cheers Dave
Many reasons, you could sample a old mono synth to make it midi and poly etc. But with the Wavestate you can use the samples in the wave sequences so opens up a world of sound.
This is very helpful, thank you. I use an MPC and have access to the hardware and software autosampler - but your explanation of the workflow is superb.
Great, glad it helps. What are you saming first?
@@IanDixonTDLI’ve bought an Arturia Microfreak and love the raw sounds. I am going to sample some of the oscillators and bring them into the Modwave and MPC.
Thanks Ian
That's a pretty good solution using the MPC
I have a Cubase template - and then use Wavelab to add loop points and trim excess.
If the samples are named correctly in the folder - I can simply drop them into the Korg sample utility - and it maps then automatically. ( you might have covered this already in your video )
I use a Wavestate and Modwave live
And can use the 4gB's of memory in each synth to cover everything.
Which means I don't have to stress about my laptop crashing or getting confused.
I've sampled all of my cool VSTi's from U-he, Steinberg, Synapse, N.I., Steinberg etc
Cherry-Audio VSTi's work particularly well - especially the GX-80
These sound epic live and have greater control within the Korgs with their real-time modulation
options.
I use Cubase so it will be worth me checking sampling with that. Do you find Wavelab better for adding loops than Korg Sample Builder?
@@IanDixonTDL Wavelab has a function called loop tweaker. If you're bringing in samples that have previously been looped - it has a few tools that help find those probable loop point sections. And if you're creating your own loops - it has a few cross fading tools that let you quickly create suitable loops.
Much easier and quicker than the Korg Loop Finder.
Additionally it also has a Tone Uniformizer for when things get really difficult. However, this works best as an experimental looper - often creating unexpected yet sonically rewarding results.
Thanks for this tutorial. Very helpful. In my opinion Korg should update Sampler Builder. Crossfade will be nice and snap to zero crossing.
Agreed! That would make importing way quicker.
👍👍👍
Hi Ian, great vid, but as a player for a loooong time i kinda need to ask what might be a completely needless question, but why sample in the first place? if you are a studio player just play the source the only reason i can think of is you want to sample the sounds to your wavestate and take one synth out on the road, is there any other reasons I;m missing?
Cheers
Dave
Many reasons, you could sample a old mono synth to make it midi and poly etc. But with the Wavestate you can use the samples in the wave sequences so opens up a world of sound.
@ cheers Ian, I didn’t think of it like that, maybe I need to spend a bit more time on the wavestate.