[PD] 0 length delay in delwrite~

[Christof Ressi]

The argument for [delwrite~] is the buffer size and *not* the maximum delay time. A buffer size of 0 doesn't make sense, you should set it to the highest block length you're using any of your [delread~] objects. Typing 1.5 will work if everything is at block size 64.

> Gesendet: Samstag, 12. Dezember 2015 um 15:33 Uhr
> Von: "Roman Haefeli" <reduzent at gmail.com>
> An: pd-list at lists.iem.at
> Betreff: Re: [PD] 0 length delay in delwrite~
>
> 
> On Fri, 2015-12-11 at 14:26 -0200, Alexandre Torres Porres wrote:
> > hi, I'm checking that if you put a 0 length delay in delwrite~ you
> > still have some buffer
> > 
> > 
> > what's up with that? and how does it work? how big is it when you
> > don't define it?
> 
> Don't know. I confirm that weirdness happens when setting [delwrite~] to
> 0. In other words: The only value that does not justify using a delay at
> all shows unexpected behavior. I can live with that.
> 
> > I always get a minimum dealy even with order forcing (and different
> > values depending on extended orvanilla), it seems the delay needs to
> > be at least the block size to work properly
> > 
> > 
> > moreover, I can't have an order forcing 
> 
> Order forcing works well for me. Just set the [delwrite~] to 10 (and
> [delread~] to 0) in your patch and the number box shows 0 (this means
> zero delay, right?).
> 
> Roman
> 
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
>