Here, to prove my point about the transient detection, here's an image. They don't make proper use of two mouse buttons, there are no keyboard shortcuts/macros, the transient detection is simply terrible, and of course, it inserts tiny pauses in between slices as shown above. Also, IMO ReCycle is clunky and awkward and simply poorly programmed. The tempo's are the same, and I've made sure that each slice has an immediate attack and an infinite release (which SHOULD prevent it from fading out, I would think). I haven't changed anything, all I've done is insert the slice markers, but you can clearly hear that it seems that ReCycle has automatically faded each loop out at the end. (BTW, this loop is available in the free loop bundle on Here's the original loop:Īnd here's what it sounds like after I've created all the slices of individual strums/attacks/transients: Otherwise, it seems to me that rex can't really do anything other than modify the attack and release of each slice and doesn't offer any effects beyond a basic compressor and EQ.Īnyway, so here's an audio example to help describe my problem.
Creating glitches is something that results from doing exactly that.
It's basically an audio editor within an audio editor so that you can turn one audio clip into several so that you can later rearrange the slices in any way you choose using whatever tools can read rex files, or even import them into something like Stylus RMX. Doing any post processing is about messing with a chopped up sample in whichever program, doesn't really have anything to do with recycle itself.Įxactly, I believe ReCycle was made specifically for slicing loops (primarily drums, though you *can* do melodic-).
It has some other stuff like effects and whatnot, but its basic principle is to chop loops, so when people see it as a tool for chopping loops, thats exactly what it was meant to do.
0 kommentar(er)
