bug in seq~
It’s just that the "add" message is documented strangely(it takes a list of messages not just one symbol or value). A little while ago someone else ran into this, solution is as follows(posted by RabidRaja a while back) :
"It’s like… weird or something(< -that's my very professional way of putting it)... apparently, you need a list of messages after the start-of-event-time, not just one single symbol or value. Try using [loadmess add 1.0 my bang] and then under the seq~ object put [route my] to filter the bangs into the counter."
copied from this thread:
(I guess it’s not documented strangely, if you look at the reference page(available from link at top of help-file) it actually shows that a list is required after the start of event-time and after any ‘optional’ end of event-time).
Anyways, hope that helps.
I completely understand what you’re saying(and the frustration), but just to clarify, the reference docs describe the input as this:
optional end time(float)
That last word, "list" describing the format of the "message" does NOT refer to the whole message but is actually referring to the very last element of the general "add" message.
But you make a very good point about it behaving differently in 4.6. Perhaps you might want to email it directly as a bug report if you would prefer it handled urgently.
Best of luck.
Actually, I see what you’re saying, [list] in brackets as opposed to each element’s format being in parentheses should be referring to the whole "add" message.
…and either way, it did behave differently in 4.6.
OK, Mattias, all taken care of… the docs will be edited for next version and I’ve emailed support about the bug(which they will get to as soon as possible). Thanks for reporting this!
21 jul 2008 kl. 23.27 skrev Karaokaze:
> OK, Mattias, all taken care of… the docs will be edited for next
> version and I’ve emailed support about the bug(which they will get
> to as soon as possible). Thanks for reporting this!
Forums > MaxMSP