AIMP Forum
AIMP for PC => Ошибки и замечания / Bugs => Topic started by: rado84 on January 31, 2026, 20:47:26
-
Here are the few bugs I found when I tested the player. But first: system info cuz you'll probably need it.
OS: Arch Linux x86_64
Host: Z790 Pro RS
Shell: bash 5.3.9
Resolution: 1920x1080
DE: Cinnamon 6.6.6
Theme: Valso-theme-v2.5-Glass [GTK3]
CPU: 12th Gen Intel i7-12700F (Turbo: 4.5 GHz)
GPU: NVIDIA GeForce RTX 3070 Ti 8 GiB
Memory: 3754MiB / 64126MiB
1. There's no icon of the program displayed on the panel. It should appear where the yellow circle in the screenshot is. Without that icon the program is just a phantom window floating somewhere and there's no way to find AIMP later, if you open something else over the program.
2. The program is missing in the ALT+TAB dialog, which is probably due to the missing icon in the panel.
3. By default the tray icon should be enabled and let the user decide whether they want to disable it or not.
4. Audio: there's some kind of crackling even when "AO: Default" is used.
4a. The player seems to be unable to work properly with ALSA, only with "AO: PulseAudio" and even then there's a lot of crackling + with PulseAudio the player crashes too often, thus forgetting the settings the user has made.
4b. Something (IDK what) seems to be adding additional volume bc at 4% setting the volume levels are insane - as if I'm at a concert, not at home. I tried all DSP settings I could think of but I couldn't bring AIMP's volume to the same or similar levels as those of Audacious.
5. Equalizer presets seem to be... "hardcoded", for the lack of a better word. Deleting them one by one only removes them from the presets list in the presets dialog, but not from the ini file. I had to resort to an old linux trick: editing the file with my presets and then making it immutable in order to prevent the player from rewriting it at startup.
Personally, I think it would save us and you a lot of trouble, if you just write a dotnet version of the player. There's dotnet for linux and it can handle all the paths and libraries translation. We can then start the player with the command (or a script with that command) "dotnet AIMP.exe" or "dotnet AIMP.dll" (depending on whether or not there's an AIMP.dll lib). The program Pinta is started the same way and it works as good as if it were native for linux. The other thing that's better about the dotnet version is that there won't be any need to distribute the files in /usr, /etc and so on + there won't be any need for .so files. All the files can be in the same dir, like this:
[rado@arch]: /B/PROGRAMS/MULTIMEDIA/AIMP/AIMP-6.00-3032>$ ls
Help/
Icons/
Langs/
Libs/
Plugins/
Skins/
System/
AIMP*
AIMPac*
AIMPac.dbgsym
AIMPate*
AIMPate.dbgsym
AIMP.dbgsym
AIMP.ini
AIMP.url
CrashReporter*
history.txt
libFLAC.so
libLAME.so
libMAC.so
libsoxrate.so
libwavpack.so
license.txt
start.sh*
With this, the program can be started from anywhere using the start.sh script which is what I'm doing at the moment.
In principle I'm all for a native linux version but I think in this case a dotnet version would be a lot better: easier to launch, easier to use, no need to maintain two different versions, if a bug appears, you fix it for the Windows version and with that it's fixed for us as well.
-
The latest nightly version is today's build 3033. You can get the package here — https://disk.yandex.com/d/ClIiI_mP79J43w/v6.00%20Alpha
Also it is better to split bugs into the separate topics. That's useful for developer. (I don't know why there is no English version of the "Bugs" section rules tbh)
3. It is a suggestion. It should be posted as a separate topic in this section — https://www.aimp.ru/forum/index.php?board=7.0
-
There's no icon of the program displayed on the panel. It should appear where the yellow circle in the screenshot is. Without that icon the program is just a phantom window floating somewhere and there's no way to find AIMP later, if you open something else over the program.
Do you use official package to install? Or you've installed it from AUR?
3. By default the tray icon should be enabled and let the user decide whether they want to disable it or not.
By default, the icon displays only if app has been minimized to tray.
Audio: there's some kind of crackling even when "AO: Default" is used.
Please, use ALSA-based output instead. AO is terrible. I will remove it before the beta (it has easier interface, so I have used it for simpler start due a porting)
Audio: there's some kind of crackling even when "AO: Default" is used.
4a. The player seems to be unable to work properly with ALSA, only with "AO: PulseAudio" and even then there's a lot of crackling + with PulseAudio the player crashes too often, thus forgetting the settings the user has made.
May be, something goes wrong on ALSA output setup. I've no idea, you should check your linux settings.
5. Equalizer presets seem to be... "hardcoded", for the lack of a better word. Deleting them one by one only removes them from the presets list in the presets dialog, but not from the ini file.
Yes, this is correct behavior. In this way, you always can resets your library to default settings.
if you just write a dotnet version of the player.
No, I will not. If you want something like that, I suggest you to use wine-based version of player.
-
4a. The player seems to be unable to work properly with ALSA, only with "AO: PulseAudio" and even then there's a lot of crackling + with PulseAudio the player crashes too often, thus forgetting the settings the user has made.
ALSA works perfectly with Pipewire+EasyEffects on my Manjaro. Afaik most of the distros have switched from PulseAudio to Pipewire.
-
Do you use official package to install? Or you've installed it from AUR?
No, the .deb file from the yandex link adem posted.
-
Also it is better to split bugs into the separate topics. That's useful for developer.
I'll know that for the next time I have to post bugs on this forum. But in the past some devs have been whining to me for "spamming" them with separate topics about bugs, so I started putting them together in a single topic.
-
But in the past some devs have been whining to me for "spamming" them with separate topics about bugs, so I started putting them together in a single topic.
In our forum, It's the opposite. Some issues requires for discussion, some not. So, separate topics for each bug is more user-friendly that one big topic.