nothing has changed on the PD side, so this cant break midi/sound.
I couldn’t find all the patches you mention on PatchStorage, but I note a couple of things in two within the description.
(note: I did not attempt to run, as I dont have time debug individual patches, and all patches I have installed work ok)
a) one seems to mention its using pd-extended, from a ‘shared directory’, if it is referring to this via a relative path this will break if you put in a subdirectory … but could be fixed by editing patch or moving/copying pd-extended.
b) another patch, seem to mention dont rename it, again moving the patch into a subdirectory may break it.
again id assume this can be fixed by editing the patch.
generally… for determine the cause of issues i would say, if you have a problematic patch on 2.2TB, you should
a) install the official release 2.1, does the problem still exist? … if it does its a patch issue.
b) try the patch in the /usbdrive/Patches directory (not a subdirectory) if it works there, and not in a sub-directory, then it has hard coded paths, contact the patch creator to see if they can remove.
I think for patch development we should strive for:
a) self contained externals… to prevent versioning, and other dependencies
b) patch to be ‘location independent’ , not only is this important for renaming, sub directories, but also the patch might be run from the sdcard rather than the usbdrive.
c) id recommend patch developers dont pack every external into a patch directory, rather pack only the externals they use… its easy enough to get this list, just open the patch without any externals… and the console will list all the missing ones.
also, I think there is an open question, about if pd-extended should perhaps be included as part of the ‘OS’, so that individual patches do not have to ship it, they can just rely on it being present… then patches can just ship other extras they need.