Max 8.6.3, buffer~, abstractions, arguments, locality

yaniki's icon

yaniki

6月 24 2024 | 8:08 午前

Hello Friends!

I would like to ask if anyone else has experienced similar issues with Max 8.6.3:

I have [buffer~] in abstraction, several instances of which I load into the parent patcher. The name of the buffer is prefixed with "---#0" to make it local in every possible context. I pass the name of the file to be loaded into the buffer via an argument.

So, after installing Max 8.6.3 all the [buffer~]'s seems to be referring to the same ("global"?) data - in each instance, the content of the buffer is the same and changing the content [of the buffer] in one instance results in changing the content in all the others.

Has anyone encountered something similar?

The problem did not occur in earlier versions of Max. I work on MBP M2, Sonoma.

I would be grateful if anyone has any comments ;-)

Ben Bracken's icon

Ben Bracken

6月 24 2024 | 8:29 午後

Changeable arguments, aka poundsign args, aka #0, must be the first part of the symbol. FE: #0_thing works, but thing_#0 does not. I believe that this has always been like this.

yaniki's icon

yaniki

6月 25 2024 | 7:46 午前

Aaaaaaa… caramba!