January 4, 2007

Audio Damage Replicant Now Available!

by Chris Randall
 

Not much more to say than that. The product page is here. Get some.
 
 
 

30 comments:

Page 1 of 3
 
 

 
Jan.04.2007 @ 5:40 PM
brandon daniel
Wow, it's really kicking my ass, in a good way.
 
 

 
Jan.04.2007 @ 6:10 PM
brandon daniel
Just a few minutes of fussing yields so much fun:

link [www.fdiskc.com]">link [www.fdiskc.com]

That's just a cheesy break loop and a demo of D16's Drumazon, loop dry alone at first, then with Rep, then D16 dry on top, then with it's own Rep.

Any hints on dealing with clicking on the steps, (feel free to tell me to just RTFM)?

 
 

 
Jan.04.2007 @ 6:43 PM
Chris Randall
Well, we put as much smoothing as we could stand without making it too spongy.

The main thing to remember is that it chops in straight time, so if you've got a loop that has a little swing in it, the divisions aren't going to be in the right spot. That's what causes the clickies.

-CR

 
 

 
Jan.04.2007 @ 7:09 PM
aKido
just bought it and already had lots of fun with it. great job!

whats next?

 
 

 
Jan.04.2007 @ 7:13 PM
filarion
very nice, gotta love 128th slicing in send mode.. and works nicely with the remote zero too obviously.. any particular reason you didn't put the actual note divisions as parameter readout on it though?

apart from that it's a nasty little bugger - in a good way. begs for some nice Macro controls in Live.. I'll have a lot of fun with it during the next gigs for sure.

 
 

 
Jan.04.2007 @ 8:54 PM
frugalpole
curious if the swing was left out, or difficult to program, or just not useful.

i don't do much w/ swing -- i'm just curious.

 
 

 
Jan.04.2007 @ 9:01 PM
Chris Randall
I'm not entirely sure if it's possible to do a looper with swing. How would every other repeat be shorter? It would sound more like a pooper than a looper.

I mean, we could fire the event at the correct divisions for a particular flavor of swing, but if it fired on a swung step, it would be short, and out of time after one repeat. If it was fired on a normal step, it would be long, and be out of time after one beat. This sort of thing definitely goes in the "far more trouble than it's worth" file. My brain hurts just thinking about it.

-CR

 
 

 
Jan.04.2007 @ 10:38 PM
Adam Schabtach
As CR said, the clicking and lack of swing is pretty much a fundamental limitation of doing beat slicing in real time. The slicer has no way of knowing how far the beats are rushin' or draggin' [name the ancient piece of hardware I'm alluding to, and for bonus points tell what year it was introduced] relative to straight time, so it can't adjust its slicing correspondingly. I suppose it might be possible to introduce a 1/16th (or whatever) lookahead period, and attempt to compensate within that frame, but that would introduce so much latency that nobody would be happy with how it worked. And, if you've ever worked with Recycle or Cubase's hit-point detection, you know that automatic slicing is far from perfect even when not done in real time, so I doubt trying to do it on the fly would produce results any more pleasing than simply cutting on straight intervals.

One could also allow the user to nudge the divisions to line up with their material, but the complexity that would add to both the user interface and the signal processing is definitely not something we would have attempted on the first incarnation of a product like this one.

--Adam

 
 

 
Jan.04.2007 @ 10:45 PM
Wade Alin
russian dragon.

W

 
 

 
Jan.04.2007 @ 10:49 PM
aKido
not criticism, i love your new plug, and all the others, they get used a lot up here...but a sort of attack knob would ve been cool :)
 
 

 
Page 1 of 3
 
 

Comment:

 

Sorry, commenting is closed for this blog entry.