[bug] delay~

Sep 7, 2009 at 7:32pm

[bug] delay~

delay apparently waits a vector or two to update its time.

OSX 10.4.11 latest max

– Pasted Max Patch, click to expand. –
#45370
Sep 9, 2009 at 3:01am

Matthew Aidekman wrote on Mon, 07 September 2009 13:32delay apparently waits a vector or two to update its time.

I think the issue here is actually the fact that delay~ ramps between delay times – but it’s not so clearly documented. The ramp message can be used to set the ramp time. So if you look a the following and click the message box, perhaps you’ll get what you were expecting.

Regards,

Alex

– Pasted Max Patch, click to expand. –
#163533
Sep 9, 2009 at 3:47am

NEVER ONCE DID I SEE THAT IN 7(ish) YEARS OF MAXING?! DOH!

someone needs to start a list of commonly overlooked messages. I could be wrong but it seems like there are fewer messages documented in max5. That could also be because it’s more organized!

anyway THANK YOU!

#163534
Sep 9, 2009 at 1:20pm
Matthew Aidekman wrote on Tue, 08 September 2009 21:47
NEVER ONCE DID I SEE THAT IN 7(ish) YEARS OF MAXING?! DOH!

on Max4, ALT + right-click will bring this menu Wink

Ciao
_y

#163536
Sep 9, 2009 at 1:49pm
RabidRaja wrote on Wed, 09 September 2009 08:03
ya, it’s probably a difficult task to decide what messages should be covered in the help-file

that is not difficult, an optimal helpfile would cover them all.

i dont really mind to open a pdf for max and an html for jitter
but it would be even better if you could have the reference right
inside max.

#163537
Sep 10, 2009 at 8:58am

is it not “unnecessary time and file-space to give examples
of even the least used messages”
in a maxmsp type combined
help and reference document, it is unnecessary time to have
helpfiles here and reference there.

you could even script the required messageboxes automatically
if you dont want to patch it by hand (at least for inlet 1) so
it is not even work to create such helpfiles.

the [vst~] helpfile is a good example for a helpfile where all
messages to the object are right in the help.
so if you want to know everything about it, you do not need
to open the reference and then try the stuff you read in the
reference yourself (or add new messages to the helpfile)

and well, i am aware of the improved reference in max5. but
this doesnt mean it could still be better. i am not sure why
you call it a complaint when i am making a suggestion.

and the command menu of the objects, no thank you.
i rather trust the good old pdf reference of my max 4 when i
want to know about all messages it can receive.

btw, the worst system i have ever seen was the nato reference,
which came as textfiles, in a form which made it almost impossible
to open it in maxmsp. i still have a little .help
patch somewhere which launched the
s reference via
loadbang and then closed itself as a workaround so that i could
open the reference text file (typed to maxmsp app) via alt-click
onto the object.
Smile

-110

#163539
Sep 10, 2009 at 2:50pm

I didn’t mean to insight a riot. What I meant was that the reference pages in max 5 seemed to be only 99.5% of messages. It *feels* as if there are occasionally ones omitted from the reference pages as well. but that feeling might be due to the cleanliness of the format.

next time I come across one, I’ll let you know.

as for including every message in the help file, maybe an auto generated reference maxpat but actually including every messages working example has got to be tough.

#163540
Sep 14, 2009 at 2:55pm
Matthew Aidekman wrote on Thu, 10 September 2009 16:50
I didn’t mean to insight a riot. What I meant was that the reference pages in max 5 seemed to be only 99.5% of messages. It *feels* as if there are occasionally ones omitted from the reference pages as well. but that feeling might be due to the cleanliness of the format.

next time I come across one, I’ll let you know.

as for including every message in the help file, maybe an auto generated reference maxpat but actually including every messages working example has got to be tough.

As the documentation is partially automatically generated undocumented messages are only the one we want to hide. Good hunting Wink

#163541
Sep 14, 2009 at 2:57pm
Roman Thilenius wrote on Wed, 09 September 2009 15:49
that is not difficult, an optimal helpfile would cover them all.

I would really hate that, the help files contains the *essential* messages, the reference covers everything.

Quote:
i dont really mind to open a pdf for max and an html for jitter
but it would be even better if you could have the reference right
inside max.

It’s time to update to Max 5 Wink

#163542

You must be logged in to reply to this topic.