build a simple version of your patch from scratch in max6 (hover, some named bpatchers) and try to reproduce the problem. this way you might find out if it’s a general max6 problem or some strangeness in your patch. try to isolate the prob in a simple patch, then you can send it to cycling support if it turns out to be a buG
I guess I should have mentioned that I did that. I loaded a bpatcher with one of the example patchers, named it and made 3 copies. It affected that one too so it’s not specific to my (more complicated) patch.
I’ll give it till the end of the day and see if anyone else replies then just send it directly. Thanks for responding.