AIMP Forum
AIMP for Windows => Ошибки и замечания / Bugs => Topic started by: Znevna on June 23, 2025, 09:09:00
-
Hello, 2682->2683 introduces some issues with the UI of some VST plugins (can be easily spotted in Waves VU Meter Stereo, VUMT Deluxe, Stereo Tool..) it looks like the refresh rate drops for those windows (I don't know what actually happens, but this is the effect).
Went back to 2682, they work fine.
Thank you!
-
Try on 2684 build
-
Can't download that build, redirects to main page.
-
Please, try now
-
It seems better, but still not like 2682. Most noticeable on Stereo Tool (9.92) Input & Output waveform display, that's the most dynamic of them all.
-
Is VST or DSP version of Stereo Tool you using?
-
VST.
We can't run DSP plugins in x64 afaik.
-
What sound output settings you using?
-
WASAPI / 48 kHz / 32bit Float.
I did some tests, it does seem to be output related, I've tried switching to DirectSound / 44.1 kHz and it made things better, I also switched the default format in Windows to 44.1 kHz so that WASAPI can run at 44.1 kHz too and it also made things better (no matter if the file currently played is 48 kHz or 44.1 kHz).
WASAPI Exclusive (Event) is the worst.
Hope this helps.
-
I think, it depended from device's buffer
-
Unfortunately, I failed to reproduce an issue with the plugin using 2684 build: https://disk.yandex.ru/i/3vieyMILzJc6wg
What is buffer capacity in your case?
-
I have uploaded here 3 short videos and extracted frames from build 2682, 2683 and 2684 https://disk.yandex.ru/d/sYzOjmV8v7JHfg
In the frames folder, frames 8-11 from 2682 are missing in 2683 and even from 2684. It's not that noticeable in 2684 but it's still not as fluid as 2682.
And here is 2684 with WASAPI Exclusive (Event) https://disk.yandex.ru/i/KA-19Nxbq3Mtcg but this is not a regression from 2682, it works pretty much the same in 2682.
-
Please, try this build: https://disk.yandex.ru/d/XrDgh-yfYQX_TQ
-
Maybe it's placebo effect that it looks ok to me, but ...
I did some tests with Voicemeeter which can be used completely virtual without any output selected (internal clock sync) to rule out sketchy windows soundcard drivers.
With it, Wasapi Exclusive Event does not work at all in 2685 (screenshot attached), and errors are present in both Wasapi Exclusive Event and in Wasapi Exclusive Push.
I've tested version 4.70.2254 and it works without issues with Wasapi Exclusive Event. But a lot has changed since that version.
This does seem to be Sound Engine related, I will try to test more versions since 4.70.2254 to see if any version 5 works ok, can I keep posting in this topic what I find?
Thank you!
-
I've tested version 4.70.2254 and it works without issues with Wasapi Exclusive Event
But v4 does not have VST support at all.
This does seem to be Sound Engine related
We've a lot of changes made in v5.30 (for multiple DSP and VST support) and v5.40 (Cross-platform and silence removing related)
-
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.
-
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.
-
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?
-
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!
-
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.
-
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