I would like to see a clear specification on whether automation is automatically adjusted by the host if the plugin has latency.

[lewloiwc]

In conclusion, "If a plug-in has latency, it is the responsibility of the plug-in, not the host, to adjust the automation timing to account for the latency." I would like to see a statement to the effect that.
By clearly stating the specification, we want to avoid having different automation timings for different hosts.

To give an example, the automation timing of a CLAP with latency is different between Bitwig and REAPER.
REAPER "adjusts automation" for CLAPs that have latency, while a plug-in that adjusts automation timing on its own would be off. Furthermore, "Adjust automation" is on by default and cannot be turned off. https://forum.cockos.com/showthread.php?t=287191
To fix this, I asked for an option to turn off "Adjust automation" and it was implemented, but in hindsight, I did the wrong thing.
What was really needed was "There is no "Adjust automation" preference in CLAP, because it is the plugin's responsibility to adjust the timing of the automation in the first place." This was the case.
Now there is an option to turn off "Adjust automation" which works just like Bitwig, but it is not the default setting.
So we have to write something like this in the plugin manual.
"REAPER has different automation timing than other hosts, so please change the setting manually." And.
Currently this is still a manageable number, but I have a feeling that in the future when more hosts support CLAP and their implementation is random this will get out of control.

Translated with www.DeepL.com/Translator (free version)