[record~]

[porres]

resizing the array

• if you change the array size, record~ shouldn't know it until you "reset" it, this is happening only if you increase the array size for something bigger than firstly initiated. For instance, if you increase from 1 second to 10 seconds, record~ won't know that until you send it "reset". On the other hand, if you decrease from 10 to 1, it somehow knows and you don't need to reset (but you should have)...

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

            sync = (t_float)(phase - startsamp)/(t_float)range;

so (t_float)range is what we could change for a value that only changes if you do the reset!

[porres]

[record~] is not redrawing automatically!

[porres]

closing this as a new issue will better describe this I guess, see #503