Cycling 74 » Topic: gen~ dim/buffer bug

gen~ dim/buffer bug

chrstphrjcby — Wed, 09 May 2012 18:39:21 +0000

I’m noticing an interesting phenomenon with dim in gen~; whenever any object is modified in gen~ (I assume this means it’s recompiling), the output of dim (or the dim outlet of buffer) changes to 1. The only way that seems apparent to get it back to the correct value is to cut and paste the gen~ object from the patch, which seems to reset it.

This seems like an initialization but of some kind. I just updated to Max 6.0.5 yesterday; could that have something to do with it?

Re: gen~ dim/buffer bug

chrstphrjcby — Wed, 09 May 2012 19:22:00 +0000

I should add that in this state, peek objects only output zero as well. Again, fixed by the cut-and-paste.

Re: gen~ dim/buffer bug

Graham Wakefield — Tue, 22 May 2012 05:55:54 +0000

This sounds like a bug in how gen~ preserves the buffer symbol associations. I can confirm the behavior when the gen~ patcher contains a buffer of the form [buffer foo bar], the association with the outer [buffer~ bar] appears to be getting lost.

Logged as issue #2964.

Thanks for reporting!

Re: gen~ dim/buffer bug

pregolima — Wed, 11 Jul 2012 17:05:09 +0000

Hi,
I am facing the exact same problem with “buffer” in gen~.
Is there a fix for it?
Thanks!

Re: gen~ dim/buffer bug

Graham Wakefield — Thu, 12 Jul 2012 00:22:53 +0000

The fix will be in the next incremental update of Max — very soon I hope!

Re: gen~ dim/buffer bug

pregolima — Thu, 12 Jul 2012 02:20:21 +0000

Thanks Graham, updates are always wellcome!