Denis

I recently moved to Max 7 with patches I did under Max 6 using various [vst~]. I was very confused and faced various crashes until I discovered that under Max 7, [vst~] is automatically given a scripting name. This caused me problems with [pattrstorage] systems, in which I didn't want to include [vst~] . I used other ways to recall [vst~] presets.

If I delete the scripting name, it comes back the next time I load the patch.

Is there a specific reason for a [vst~] to force it to have a scripting name?

Is there a way NOT to have a scripting name for a [vst~] ?

so I wouldn't have to explicitly exclude it from the pattrstorage system.

Hello,
I recently moved to Max 7 with patches I did under Max 6 using various [vst~]. I was very confused and faced various crashes until I discovered that under Max 7, [vst~] is automatically given a scripting name. This caused me problems with [pattrstorage] systems, in which I didn't want to include [vst~] . I used other ways to recall [vst~] presets.
If I delete the scripting name, it comes back the next time I load the patch.

Is there a specific reason for a [vst~] to force it to have a scripting name?
Is there a way NOT to have a scripting name for a [vst~] ?
so I wouldn't have to explicitly exclude it from the pattrstorage system.
Thank you!


Max 7 vst~ scripting name