Skip to content
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

Using setloop for full buffer duration reports error #66

Open
rconstanzo opened this issue Apr 29, 2018 · 0 comments
Open

Using setloop for full buffer duration reports error #66

rconstanzo opened this issue Apr 29, 2018 · 0 comments

Comments

@rconstanzo
Copy link
Owner

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 a setloop 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:

<pre><code>
----------begin_max5_patcher----------
499.3ocuUtsbZCCDF9Z6mBM5ldCvXK7Abm9lzoSGgYATpsjGI4DxjI8YuRqL
TR4Pnj.9B4YW9k1c+z5kWhinyUa.Ck7Ux2IQQuDGEgt7NhFrins7M0MbCJiV
qZaAokNJ7aVXiE8+swiGSVpUsj0fFHB6WLjZkpYqPYeqp21.V7XRF7ZrO2.3
92SmPtUV5fyNtsdsPt5mZn1Fx1z7YSRFQpv0TVo+EKYRB4GC6Qr.OW07GFWQ
8tdMN1uL5BKzVvX3qfCJTCXaTpNRdk6YRU0wKvcYtFLNbwsBkburmkN0mvkU
90jgkco9gTIbx1m6fv9ozcheCvXmFX4o9vTffJMACOicbdUdC40GAWUo2abU
g3pp3bzp3lQqqiULDPyxt2rJkgeKN6rvJ+V.qhD2y4g0MrtmV79kc10T1R3I
2dOnp+EW2x+M4o0bK7HnOdcyt751HVI4t4zDZivXu5a+xrKXxB6SjCy6WtDz
+EDmqM3+.GKaTbqmFy4xUmfFouGMXSCyYCuNEMR2mFn.2Uf7e++XLHd+uEQF
UutdaRGlZ69TeWXV.FqPhCG1SCKn4nWBWZbJtSwI+NEmrqJNgqKdWmqyyLHF
Cgq28Ak1aVNBMExf4TzTCOJ1pOG8v0tdHqqApWGZM2TjQCaUs.zxdA1xE6i7
qw+AlFfO7.
-----------end_max5_patcher-----------
</code></pre>

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant