GOOD NEWS!
The latency report war against your AG and the Steinberg AG (Asio Guard) is over when using the VST3 AGridder plugin instead of the VST2 one.
I've tried everything with VST2 AG version.
Disabling the individual Asio Guard setting finally did not correctly report new latencies to Cubase either.
Completely disabling Asio Guard in Cubase helped, but this is a no go option for big projects.
This is broken from the AG 1.1 beta 4 I used a lot without this issue.
The enforcing latency trick indeed re-syncs everything but, at the "building" stage, it has to be done at each AG/Hosted plugin insertion.
So I tried to insert VST3 AG plugin instead of VST2, saving each chain preset from VST2s and reloading it in each new VST3s.
And Voilà...
You can insert/delete AG plugin, change hosted ones and every thing remains in sync with Asio Guard enabled everywhere.
I don't know why but I was exclusively using the VST2... until now.
SAD NEWS!
Because paradise is not that easy to reach, VST3 gives me a strange hosted plugin GUI size detection issue.
Please, watch my video showing VST2 vs VST3 opening the hosted plugin GUI.
VST3 needs 2 attempts.
This a blank Cubase project (1.2 beta 3. DAW W10 / Server W7)
Hallo Andreas,
GOOD NEWS! The latency report war against your AG and the Steinberg AG (Asio Guard) is over when using the VST3 AGridder plugin instead of the VST2 one.
I've tried everything with VST2 AG version. Disabling the individual Asio Guard setting finally did not correctly report new latencies to Cubase either. Completely disabling Asio Guard in Cubase helped, but this is a no go option for big projects. This is broken from the AG 1.1 beta 4 I used a lot without this issue.
The enforcing latency trick indeed re-syncs everything but, at the "building" stage, it has to be done at each AG/Hosted plugin insertion.
So I tried to insert VST3 AG plugin instead of VST2, saving each chain preset from VST2s and reloading it in each new VST3s.
And Voilà...
You can insert/delete AG plugin, change hosted ones and every thing remains in sync with Asio Guard enabled everywhere.
I don't know why but I was exclusively using the VST2... until now.
SAD NEWS! Because paradise is not that easy to reach, VST3 gives me a strange hosted plugin GUI size detection issue.
Please, watch my video showing VST2 vs VST3 opening the hosted plugin GUI.
VST3 needs 2 attempts. This a blank Cubase project (1.2 beta 3. DAW W10 / Server W7)
https://user-images.githubusercontent.com/65025818/117688270-ea6c5880-b1b8-11eb-9c0b-de90ba7a5dd8.mp4
Cheers.
Igor.
Originally posted by @igbro in https://github.com/apohl79/audiogridder/discussions/524#discussioncomment-719285
-- Just want to add... On server side, plugins are all VST2's...