Hi Gilberto, Alexandre,

Thank you for the report.

The issue is probably caused by a bad help patch. [delay~] has two arguments, a delay buffer size and the actual delay. The right inlet can be used to change the actual delay time.

If no arguments are used, the maximum delay is 512 samples. If you specify 44100 as single argument, than this is the maximum buffer size.

With two arguments, like [delay~ 441000 44100], you have a ten seconds delay buffer, and the actual default delay is one second.

The object seems to works as described in the Max 5 documentation, but the help patch is wrong. I'll fix that.

Greetings,

Fred Jan

On 2015-06-24 04:39 PM, Gilberto Agostinho via Pd-list wrote:

Hi Alexandre,

Since you are interested in doing some maintenance in the cyclone library, I would like to report a possible bug found by an user in the forum and then confirmed by me. Apparently there are some problems with the object [delay~] and I am not sure they are present in Max 5 (I can check at my school if you want to). The problem is actually two bugs: first, the argument is completely ignored (so no delay is applied when I try [delay 44100]). The second problem is about the range of the values accepted by [delay~] via its rightmost inlet: it clips any input into values between 0 and 44100, so it's not possible to have a delay longer than 1 second.

Here is the forum thread where this was reported: http://forum.pdpatchrepo.info/topic/9371/what-does-delay-do/2

Cheers, Gilberto

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list