Hello,
I've used [delread~] and [delwrite~] in the past with no problem, but I've always wondered what the [delay~] object does. It supposedly takes an argument in its right inlet that determines the delay in samples, but it doesn't actually seem to do this. If it receives a 0, there's no delay, but if it receives any other value, it seems to create the same delay (less than a second), regardless of what that value is. [z~] seems to do what [delay~] should, but I'm wondering why the latter exists.

(I just found this and the person was simply told to use the above mentioned objects: http://forum.pdpatchrepo.info/topic/2955/delay-does-not-work/2 )

Thanks in advance!

@whale-av I think what needs to be done is what Fred proposed: improve the help file. But changing the object is a no-no, it must be compatible with Max, that's the sole purpose of its existence! It may confuse a beginner or two, but I mean... they will soon find about [z~] or rather [delwrite~] and that's that. Meanwhile someone looking to import a patch from Max can be guaranteed it will be reproduced flawlessly in Pd.

So you know, even if a Max object would be broken in some way (which is not the case here), then the cyclone library must copy its "brokeness" to the uttermost detail!

EDIT: something just crossed my mind: maybe I am misunderstanding what you meant by "hammered". If you meant better explained, then we are actually both talking about the same thing and I apologize for the message. If you meant modified as to fit how the other objects in Pd work, then my answer above stands

@gsagostinho No, I was not suggesting that the object should be changed, just that the fact that the creation argument "IS" the maximum delay should be OBVIOUS as it is currently obviously NOT....... and that the right inlet takes the "customers requirement".
David.

So yeah, just ignore my last message. Sorry, I am obviously not a native speaker as you must have noticed a quadrillion times in this forum.

I'm a native speaker, and I wasn't sure what "hammered" meant either...

@s.elliot.perez Yes, sorry, sloppy posting!
"Your help file is better, but maybe the creation argument purpose needs to be "hammered home", as it is not consistent with most other objects." would have been much better...
David.

Ah, I would have said "driven home", but maybe some people say "hammer home". shrugs And yes, even after reading electrickery's file, I actually still didn't understand the importance of the argument and was confused as to why it was working until I read whale-av's comment.

Thank you for your comments. I will look at the [delay~] help patch again.

As I found out several times, the objects in Max5 and cyclone do not appear to be very consistently designed, and there is not much you can do to fix this in the help patches. But for [delay~] this should be possible.

Greetings,

Fred Jan

Great, Fred, thanks again!

Here the latest delay~-help.pd help patch.

If there are more remarks on cyclone help-patches, I would happy to consider them. After all, Pure Data is a community driven project!

Greetings,

Fred Jan

@electrickery Hello Fred,
Sorry to trouble you, but here is your help patch with 20 seconds of delay:
Delay-Help_20secs.pd
Is the 10 second theoretical limit because that would be the limit for this object in Max?
David.

@whale-av; Hi David,

No there is no real limit in the code, other than what Pd is allowed to claim from the OS. And twenty seconds works for me with your patch, but it strains my attention span . 20 seconds is very long in 'click-and response-time'.

Greetings,

Fred Jan