The Cherry Audio memorymode unify preset library doesn't seem to work with the updated memorymode plugin. I started going through each preset and replacing the instrument with memorymode and then manually selecting the right instrument, but this seems pretty tedious. Is there a fast/easy way to re-link the preset library with the correct plugin? Or is there an updated version of unify presets for Cherry Audio memorymode?
And turns out on OS X M1 platform, the VST plugins won't load (not sure why). Ended up using a sed script to bulk modify these:
for f in *.unify; do LC_ALL=C sed -I "" -e 's/name="Memorymode" format="VST"/name="Memorymode" format="VST3"/g' "$f" LC_ALL=C sed -I "" -e 's/file="\/Library\/Audio\/Plug-Ins\/VST\/Memorymode.vst"/file="\/Library\/Audio\/Plug-Ins\/VST3\/Memorymode.vst3"/g' "$f" done
Now looks like none of the presets within the plugins load properly. Not sure if there's an easy way to relink these.
There are two problems with your approach:
- You're trying to force Unify to load the VST3 version of plug-ins, instead of VST (VST 2.x). This may work, but will break all the patches, because the state-data that Unify stores for each plug-in is format-specific. State blobs saved from a VST2 plug-in will absolutely NOT load into even the VST3 version of the "same" plug-in.
- You're basically editing the .unify files as though they were ordinary text files, but this will only work if you don't add or subtract characters, because there's a binary header with a byte count.
For details about the .unify file format, see https://pluginguru.net/unify/manual/doku.php?id=patch-structure. I've also just emailed you directly, and we can discuss further by email.
Oh sweet! That manual is useful. Let me take a look at this tonight after work and when the kids let me have my quiet time. That would make it easier to convert the unify files from VST to VST3.
