Memory not resetting in bufampgate~?

Hello, not sure what the protocol is now for bugs. Github or here?

Anyway…

I think I found an instance in Max where fluid.bufampgate~ is not resetting its internal memory (perhaps).

When I run a slicer on a test case it produces different values to every subsequent run.

Small test patch:

<pre><code>
----------begin_max5_patcher----------
961.3oc0Xs0aaBCE94To9evh2pTZju.DXO0+D6oopJmDmT2BFD1zlspse6yW
fLZG2ZJIqKOfkcrwmuuuyw9b3kKuXl2pr8LoG3KfuAlM6E8HyriYFYV8.y7R
o6WmPk1I5sNKMkITdyq9SEaux9G3q.qnhc.tBndlulATY.IS2bOCrgucKqPu
LPASVlnjGVdBWvVmUJruCb8n45oomMUwyD209T3ar6Z1pGtF6e30kSUqumK1
cWAasxALR.dAbNv8DE.MMD+EPvs0KRTlxEILkEfnFilUppGFZG8mWdgoU2L+
iSXnq.4kJ.EH0FbBCvSyKSj5VgdrUkFFa.ZpIGP5iChPFT6G9OhBVUpTYBu1
LaTelsSy7IlmX+5mCY04zBZJSwJtiInqRXVaucHcXMtwTeOm41YOiqrG31iF
xoLojti0hpunMd.E2q7EaENmJhiWDneh6jHvuWrdRvIrcbF0GNQDzmVfJXOq
Aveiy7rGY+BHKV2JbCGVVwAVzF5vb2nkL0QkcgHIKADfvshmfQ3l5Nlwe4.3
oC0C2eH47SiJ90evAHXiKRZBZ3vmQEYwbP3wgYxfXttkatA3DDsdc0u1veug
rjXqNivtipgGGAblCYK3MtOtoROPhDD2EmA1F7.PEcthWM9tP.rU.0aVADry
eMH9OYG7I14sK7uioSTTU.jzzbI3lDtTwDcvG3wvGPq.iHAGmB2MgXO85DcB
VNi8n8dnE7M6aE6nw3bCsoYEAOtKi5NNdaRF8Co9cmC4xQnotSo+OKGxtj5s
Ik7MKzUHnc32QU5zOtQlUVnK4RK+fa3hM5xuj84KDLBJCE53rvvoNLn97.mO
wIJdvU.UuQD8eZejeiCGq57tIA7.ADyOcdIMH.s+g8rwNyvY3DbHgvFI2cFI
B21XK.9seoBqwZ9i2POtfgpWek6Nng8tgIUbg8iKzXRl6FLypagXz62xwreu
wnxJ1nq22PfSfAXJqdDHFNYH1T+5H1vvWOqT9l7LcVAUBabjsfO2UPM5LMV3
3bBhmNJwvt3QQInAnDjKYykU4kznCl3R+F4pU1zqEWJ3T.mnIPgQ5BDBNX0U
RrynmJIFMnIFctk3SYj93TE+dUEeXn0KyUxNA49RoupGgD6tE.alos246jxn
N3uIwsFOFeF+oykAOJAiLcaHYT9nnoaCQuGWx1usmlm+DqPVsD2doy54gLqt
GM20mKb8cob3UvdhWujpgnE5rYT5TYJKrln29vpDf7RyzdQhRdcfnAsls1lX
kPm7uLm5vkMArKuPOgeCBEmjjB
-----------end_max5_patcher-----------
</code></pre>

I initially thought it was the getattr as the first time I run it, it only spits out a 1, and the second time it spits out the correct number (3), but checking the buffer~ directly, the first time you run it it only produces a buffer with 1 sample in it.

Yep thats what I see. I was actually able to catch it while making CLI tests :slight_smile:

Cheers @jamesbradbury, we’ll take a look. It’s possible that this may have been fixed as a side effect of this commit: https://github.com/flucoma/flucoma-core/commit/4eb7c572b7b2744176273c4be81fa3301bcbb545 (but we’ll check)

Either, with a preference for Github if you’re sure it’s a bug and have code to reproduce (as you are / do here). If this isn’t fixed by the commit from last week, I’ll make a new issue for it.

With the caveat that this is for public code only (toolbox 1). Toolbox2 alpha bugs should be on its given channel here.