[x] [2684][x64] VST: Plugin UI doesn't refresh properly (framerate drop)

[Znevna]

But v4 does not have VST support at all.

I know, I've only tested with different sound output options in AIMP without any plugins, since WASAPI Exclusive Event is the most affected I wanted to see when it started. I'll come back with findings.

[Artem]

errors are present in both Wasapi Exclusive Event and in Wasapi Exclusive Push

I've tested the VB Audio, it seems the errors related to non-standard buffer size.
AIMP forced the Device to use big buffer (200 msec) instead of default one (in my case it is 10 msec).
Too small buffer may lead to performance issues and high cpu loading.

[Artem]

So, there are no real error in output. Anyway, I want to ask you about initial issue, does frames are still drop in VST UI using 2685 build?

[Znevna]

So, there are no real error in output. Anyway, I want to ask you about initial issue, does frames are still drop in VST UI using 2685 build?

The real error would be that "WASAPI Exclusive (Event)" as output does not work at all with VB-Audio in 2685 and it works with 4.70.2254, I have not tested other builds with "WASAPI Exclusive (Event)" as output device and VB-Audio, yet, but this deserves another topic.

The initial issue about the regression introduced in 2683 seems fixed to my tired eyes, thank you!

[Artem]

it works with 4.70.2254

I've checked 4.70 and seems it has a bug, v4.70 always use minimal supported buffer size instead of required (wrong condition in the code).
It seems VB-Audio does not allow to use custom buffer size (but it does not reported about that), so what why buffers are ignored.

[Artem]

The real error would be that "WASAPI Exclusive (Event)" as output does not work at all with VB-Audio in 2685 and it works with 4.70.2254, I have not tested other builds with "WASAPI Exclusive (Event)" as output device and VB-Audio, yet, but this deserves another topic.

I'll add option to allow device to choose preffered buffer size by itself, but I the option will be added to next version of app, not to v5.40