Saving and Exposing persistant automation parameters in PD patches

[gllmAR]

From my understanding, currently, in PlugData versions 0.91 and 0.92, automation parameters are stored within the session of the host DAW.

This works well for situations where a user creates a patch for a specific session and sets up automation parameters. As long as the user remains within that session, the exposed parameters are retained and can be shared across different patches opened by the same PlugData instance. Copy-pasting the effect to another track also preserves the instance automation parameters.

However, when starting a new session, creating a new instance of PlugData, and loading a patch, the user has to manually recreate the automation parameters to expose them to the DAW for automation. This limitation complicates the process of sharing patches that behave like standard plugins.

Could there be a way to expose parameters directly inside the patch itself, so they persist across sessions without manual recreation?

It would be ideal if this method of exposing parameters is also compatible with the HEAVY compiler, where the @hv_param string of a [receive] object is parsed and converted into a plugin parameter during compilation.

for example

r threshold @hv_param 0 100 60

This would become the threshold parameter in the compiled object.

reference https://github.com/Wasted-Audio/hvcc/blob/develop/docs/02.getting_started.md

This improvement would greatly streamline the process of sharing patches, especially in a class environment.