Re: [sc-users] CutBuf1 and CutBUf2 behavior

[nick collins <nikolaicollinsky@xxxxxxxxxxx>]

there might be something odd to do with your afile.aif- it works fine for me when I use my own soundfiles. 

but I suspect you're just talking about the natural difference between CutBuf1 and CutBuf2 however- the former jumps around the buffer without any worry over discontinuities, but is constantly playing back. The latter envelopes each cut as an individual Synth grain. So the first can have click artefacts and the second enveloping artefacts. You can mess with the SynthDef in the CutBuf2 class to change the enveloping or you might get what you want via the current existing options for that class (<x-tad-smaller>dutycycle, atkprop, relprop, curve)</x-tad-smaller>  

cheers
N

On 25 Sep 2005, at 13:04, ekko wrote:

> (
> var clock, file, cutter;
>
> clock = ExternalClock(TempoClock(2.3)).play;
>
> Routine.run({
> file = BBCutBuffer("afile.aif", 8);
> s.sync;
> cutter  = BBCut2(CutBuf1(file),
> WarpCutProc1.new).play(clock);
> })
> )
> I get a constant playback.
> Whereas with this : 
> (
> var clock, file, cutter;
>
> clock = ExternalClock(TempoClock(2.3)).play;
>
> Routine.run({
> file = BBCutBuffer("afile.aif", 8);
> s.sync;
> cutter  = BBCut2(CutBuf2(file),
> WarpCutProc1.new).play(clock);
> })
> )