Support |
Rainer, Yeah that's a little glitchy bug/feture I use pretty frequently with the DD20. Changing time on it does NOT change pitch when you turn the knob but rather the device starts cutting off and throwing away some audio information (not from the beginning point of the loop but from the point of the loop that is playing or about to play). Then when you turn the time value back to the full length (or beyond the point where the loop was initially set and created) it seems to insert bit's of left-over scrambled audio data from the buffer. I have not tried your specific scenario (perhaps I will have to do so sometime soon, heheh). But it seems like what you are saying confirms that even if you trim off some part of a loop by turning the knob to a shorter time, when you turn it back to a much longer one it reintroduces some pieces of audio that had been trimmed off. I have only experimented with wobbling the time knob back and forth rhythmically trying to introduce glitchy noises. If I figure out anything more about what it's doing I will share my thoughts on it. The DD20 is really an underrated device IMHO. It will do a lot of clever things many people would never expect. And, like I've said many times before, if you own more than one . . . the internal clock in them is amazingly accurate and consistent. Just set 2 side by side with the same millisecond value dialed in on both and play something into both at the same time. It will take 15-20 minutes before you can detect any drift between the 2. To me that is nothing short of amazing. I owned 3 at one point and am now back down to just one. Despite all the rack gear I own, I still find the little sucker amazingly handy. Sleep well my German friend. Ted On Sep 28, 2009, at 5:47 PM, Rainer Straschill wrote: > Has anyone done a throughout analysis how the Boss DD20 handles its > delay memory when first reducing, then again increasing delay time? > (Ted, I'm looking in your general virtual direction here ;). > > The reason I'm asking. Just encountered some interesting behaviour > (and no, haven't tried to reproduce it, this is my last msg before > going to bed...): > > Played the guitar into the DD20 - mode "smooth" from a memory slot, > preset to 23sec., reduced to a few seconds ("two bars") by taptempo > (via external FS), feedback about 60%. > I played some with that setting, then ended by tapping in a shorter > delay time (370ms) for that "unrounded multiply", had that fade out, > turned the delay off (left FS), set feedback to 100% and turned the > delay time back up to 23s with the depressed delay time knob ("time > advance"). > > During the turning up, I heard some of the DD20-glitching, then after > I had brought up the delay time again and released the time knob, the > last version of the delay contents before I did the shortening to > 370ms became audible - it seemed that the part of the delay content > that was "multiplied away" had stayed in memory and thus got included > again after I turned the delay time back up. > > Sooo...is this a known effect/feature? Can one make use of that in a > predictable manner (or, even better, in a non-predictable one)? > > Rainer