|
|
May 9, 2012 at 6:39pm
gen~ dim/buffer bug
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?
|
|
|
May 9, 2012 at 7:22pm
I should add that in this state, peek objects only output zero as well. Again, fixed by the cut-and-paste.
|
|
|
May 22, 2012 at 5:55am
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!
|
|
|
Jul 11, 2012 at 5:05pm
Hi,
I am facing the exact same problem with “buffer” in gen~.
Is there a fix for it?
Thanks!
|
|
|
Jul 12, 2012 at 12:22am
The fix will be in the next incremental update of Max — very soon I hope!
|
|
|
Jul 12, 2012 at 2:20am
Thanks Graham, updates are always wellcome!
|
