You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Comments:
It appears to be some kind of rounding thing and/or the amount of actual available buffer space is smaller than what is listed because (as seen in the example code) setloop 59999.99 throws an error but setloop 59999.9 does not.
Also, possibly related, but I have a bit of code from old [karma~] patches that have this workaround for getting weird 'default maximum' size messages coming out of the list outlet. I don't remember the tested I did to get this, but there's a [route 59999.980469] in the code to filter out that value.
The text was updated successfully, but these errors were encountered:
If you send a
setloop
message with the full duration of the [buffer~] you get a (yellow) error message.Steps to reproduce:
Create a [buffer~]/[karma~] combo with a buffer size of
60000
. Send asetloop 60000
message to [karma~].Actual results:
You get this message:
karma~: loop maximum cannot be greater than available buffer~ size, setting to buffer~ size
Expected results:
Setting [buffer~] to the size.
Example code:
Comments:
It appears to be some kind of rounding thing and/or the amount of actual available buffer space is smaller than what is listed because (as seen in the example code)
setloop 59999.99
throws an error butsetloop 59999.9
does not.Also, possibly related, but I have a bit of code from old [karma~] patches that have this workaround for getting weird 'default maximum' size messages coming out of the list outlet. I don't remember the tested I did to get this, but there's a
[route 59999.980469]
in the code to filter out that value.The text was updated successfully, but these errors were encountered: