Max - Controversial automatic temporary buffer mode

Another massive perk of having something like this, is the ability to have multiple processes cohabitating a single patch without having to rename or make everything unique.

For all the testing I’m doing in the thread about time travel I’m having to manage dozens of patches all with slightly different buffer~ sizes or processing chains because if I chuck them all in the same patch, the buffer~s would all be named the same and potentially break things. I could go through and give each version of this a unique name, and make sure all the from/to attributes for each object points to those, but that’s incredibly faffy, and a process I’d have to do for each variation of thing I wanted to test.

So if things followed the ears.stuff~ model, it could be processing chains that would all have unique buffer~s by default and wouldn’t require so much faff for every variation in testing.