line~ bug

Mar 23, 2011 at 7:59pm

line~ bug

Maybe somebody already has posted about this bug, or has an explanation as to why it would be difficult to have perform otherwise. The bug is this: if you send the message “stop” and then some ramp (like “0 100″) to line~ in quick succession (like using a trigger object and have it sequence the messages accordingly, or separating the messages by a comma in a message), the ramp does not end up at the value specified by the ramp as it should. I’ve attached a patch that demonstrates.

Attachments:
  1. linebug.maxpat
#55774
Mar 23, 2011 at 10:31pm

Thanks for the example. While we investigate, you can just get rid of the stop message since it doesn’t do anything in this particular case. When you send the new list it replaces the old one.

#200533

You must be logged in to reply to this topic.