I will stick to my method. But hey, I even took the effort and prepared samples of both waystallowwaters wrote:I agree, but I would say try reverberating the sample, then reverse it.
But as I said, I'm sorry if I offended You in any way. My way would have came out the exact same as yours (I do this all the time), I think I just communicated how to go about it very poorly, as is my custom.roon wrote:I will stick to my method. But hey, I even took the effort and prepared samples of both waystallowwaters wrote:I agree, but I would say try reverberating the sample, then reverse it.
And to straighten up any missunderstandings - I didn't mean to affront you in any way or something - if I did I'm honestly sorry for that, it was not my purpose. It's just that I love to learn new things and I love sampling, so I thought I'll ilustrate both methods with samples
So, anyways! Samples!
Since I do not have a microphone I did used a speech sample from random song.
Here's the dry one. First one is 'forward' sample (your way) and the secound one is reversed one (my way). Both are dry.
Here's the reverberated one. Exactly like the dry one, first sample is 'forward' (your way), next one is reversed (my way). Sorry for the huge verb, by the way. It came out to big :/
Finally, the end product. Since I just reversed the file without any alteration to the playback order, this time first sample is done with my way, and your's the second.
As you can see, my method (the one shown on the video) reversed reverb giving this sweeping sound, yet leaving the words understandable (well, kinda but again - way to big reverb blurs everything :/), while your method just made the sample play backwards.
I hope this makes that problem solved
ah my mistake - for some reasoni imagined you sequencing in a daw. you could still have two instances of the sample and alternately trigger them, but then that takes up more momory and such. have you solved the problem yet? madtheory's reply is probably the rout i would go if i had the same issue with a drone.colmon wrote:that's all well and good for crossfading drones in a daw, but i don't see how it's relevant to a hardware sampler
just wondering if anybody has any tried and tested techniques for creating looped drones in a sampler, whether it be using the samplers in-built crossfade algos or whatever
if anyone is triggering multiple looped samples live, it helps to make the loop size for all of them identical or even multiples of the original loop size(in samples). before i was adjusting the loop regions based on where the sample started and where one beat over the segment that i planned to loop started, but the loops kept drifting. i thought this would be sufficient for keeping them in time, but decided to try making one loop (starting with a kick), and then using that number (151239 @ 140bpm) as the loop size for the rest of my samples, calculating when i wanted a looped segment twice that size or half etc. i would then record a new segment @ 140 bpm (synced to a digital clock) and then enable looping, entering 151239 as the loops size. i thought i would have to adjust sample start times, but the loops turned out super tight without that! as a bonus, i also accientally figured out that even though the akai s2000 doesn't have a loop-> retriger option like the s5000, you can trick the s2000 into continuously looping if you pull the midi cable out your keyboard wile holding the key down. then when you plug the calbe back in, it's still looping until you hit the key. you can then trigger another sample and do the same thing and now you have two going! it's probably not the best thing for it, but hey: it works!
