@sean_ae @Kama11 makes sense, thanks! so it sounds like you’re not locked into a strict A branch / B branch thing and rather just letting each slot pair switch back and forth as needed, independent of what the other slot pairs are doing in that channel?

@sean_ae @Kama11 OH also, kinda related- I’ve been curious if you have changemode enabled on your global pattrstorage. the way I have mine set up now, all the patchers need to get reloaded in the next branch even when the patches don’t change, which feels pretty unnecessary. seems like for changemode 1 to be possible, each A/B slot pair needs to work independently rather than a strict A branch / B branch kinda thing. seems like a PITA though so was curious if you’ve explored this!

@sean_ae @Kama11 brilliant, thanks!

@sean_ae @Kama11 so if you’ve got a patch with some autopopulated umenu’s, you wanna avoid letting the umenu populate itself via its attributes and instead just populate manually on load via messages and loadbangs etc? so as to be able to get a defer/deferlow in there

@sean_ae hey sean! i was curious what your thoughts are on .maxproj “projects” in max, if you’d be willing to share. are they useful to you for your style of system or do you prefer regular patches for everything? cheers!

@sean_ae Minneapolis needs you!!