-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[record~] #170
Labels
Comments
Closed
Closed
[record~] is not redrawing automatically! |
closing this as a new issue will better describe this I guess, see #503 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
resizing the array
but then, now that you've increased it and reset it, you can go back and increase from 1 sec to 10 sec that it'll know without needing to reset
not that i like having to reset it, but this is how it works in max, and maybe it's good cause it makes this reset message more useful. Now, I guess we could make it so that it doesn't need reset, but we shouldn't because of the compatibility issue. One way or another, I guess we can't have different behaviour in our object as it is... so we might as well make it require the reset message!
and how does it or should it affect sync? say you go from 10 sec array to 1 sec, then your sync output should go from 0 to 0.1 - but as things are right now in cyclone, since it knows where the end is, it goes from 0 to 1...
here's how we calculate sync by the way
so (t_float)range is what we could change for a value that only changes if you do the reset!
The text was updated successfully, but these errors were encountered: