Martin Beck

If I load the attached patch the [mtr] seems to have correct binding to the sliders s1 s2 s3, but I am unable to record anything.

If you remove the [loadbang] save and load the patch again and perform binding by hand (click the message box with the target scripting names) after patch has loaded it works as expected.

mtr_loadmess_problems.maxpat

There seem to be some more problems with other patches containing autopattr and pattrstorage , where even the workaround doesn't help.

If I load the attached patch the [mtr] seems to have correct binding to the sliders s1 s2 s3, but I am unable to record anything.
"bindto" is called via [loadbang].
If you remove the [loadbang] save and load the patch again and perform binding by hand (click the message box with the target scripting names) after patch has loaded it works as expected.

Max 8.1.8 Mac MacOS Catalina

Edit: There seem to be some more problems with other patches containing autopattr and pattrstorage , where even the workaround doesn't help. 

If I load the attached patch the [mtr] seems to have correct binding to the sliders s1 s2 s3, but I am unable to record anything.
"bindto" i

-bug-mtr-bindto-on-patch-startup-causes-problems

Indeed, there is a bug here. A delay after the loadbang can serve as a quick fix, but the terrible thing is that with your original patch, things not only don't bind at loadbang, but also don't bind at all even if you give again the bindto messages later!

Yes, exactly. The only thing to get it working in this state is create a new mtr or change the track count.

don't bind at all even if you give again the bindto messages later!

[Bug] mtr - bindto on patch startup causes problems