[x] [2555] aimp_5.30.2555 has click on timeline issue

[jimdunn]

Hi, after installing aimp_5.30.2555 I noticed, when a song starts playing, if I click the "time line" the waveform goes to nothing (just a line) and sound pauses on that note, then when I try to exit, it appears to go away, but it still in memory and must be killed before the "note" stops playing.

[Artem]

Unfortunately, I cannot reproduce that on my side. Can you record a small video that illustrates the issue?

[jimdunn]

Ok, here's a video... the "mess up" is during the 5th time playing "Sample-2.mp3" -- notice I finally click a spot that freaks it out, then I exit, but have to kill from memory to stop the tone.

[Soolo]

Please try to reproduce an issue on this build:
https://disk.yandex.ru/d/ClIiI_mP79J43w/v5.30/aimp_5.30.2555_w64_debug_fmm.exe
https://disk.yandex.ru/d/ClIiI_mP79J43w/v5.30/aimp_5.30.2555_w32_debug_fmm.exe
if app will hang - run this tool:
https://disk.yandex.ru/d/ClIiI_mP79J43w/madTraceProcess64.exe
https://disk.yandex.ru/d/ClIiI_mP79J43w/madTraceProcess32.exe
it should generate extended report about the issue

[Artem]

What plugins you've installed in AIMP?

[jimdunn]

I have no plugins at all.  I will try your DEBUG... oops... I do the "portable"... do you have a debug portable zip?

[Artem]

I have no plugins at all.  I will try your DEBUG... oops... I do the "portable"... do you have a debug portable zip?

You can select portable mode during installation. I've not built zip for debug, sorry

[jimdunn]

Ok, I was able to repeat the issue (took 11 tries).  Here are the mad files.  #1 was taken while the aimp gui was still open but hung and the repeating note was playing... #2 was taken after closing the aimp gui but still had the aimp.exe in memory, and the repeating note playing.

[Artem]

Попробуйте эту сборку: https://disk.yandex.ru/d/690u6gMZTMtQqA

[jimdunn]

SUCCESS!!  I tried it 50 times, no problems!!!!!

[Artem]

Thanks for testing!

[Artem]

Please, try this build:
https://disk.yandex.ru/d/4AWvgexfTUD2Xw
Is the issue happens using this build?

[STG1234]

Please, try this build:
https://disk.yandex.ru/d/4AWvgexfTUD2Xw
Is the issue happens using this build?

Greetings.
I'm currently using version 5.30.2563, and this problem still persists. Clicking anywhere on the seekbar can still cause the issue of playback being disabled all together, and not being able to open another file, until we end the process using task manager.
now, I wanted to try the build that you had linked in your last post, but apparently the file is not available anymore?
anyway, I wanted to give a bit more context and explanation regarding this issue, when it happens, and how I somehow managed to prevent it.

1 - This problem happens ONLY upon left-clicking on the waveform seekbar in the main window (same with holding and releasing the key on the seekbar). Meaning, using the Mouse Wheel on the seekbar to go forwards/backwards in the track by 5 seconds or more, or using the seekbar on the mini-player in any way doesn't cause any problems.
2 - If we use the Mouse Wheel or the mini-player to go forward/backward just once and at any point, the problem is automatically resolved and cannot be replicated again until we open a new file. For a while, I've been using this method to prevent this issue from happening. I use the mouse wheel a little and then click on the seekbar, so the bug doesn't occur.
3 - This bug doesn't happen to all tracks. While unfortunately, most tracks are affected, (based on the origin of the track and not the quality) some tracks/groups of tracks remain immune to this bug. Like, I have a FLAC quality of a Bury The Light downloaded from somewhere, and no matter how many times I try, this bug simply cannot be replicated on this file. or, this bug just doesn't happen to sound files that I have ripped from YouTube using YTDLnis (128kbps). Or, the official OST of some games that I have are totally fine and remain unaffected (320kbps), while OST of some other games are entirely affected (320kbps). Sounds that I have recorded and exported using Audacity are also affected. Some albums are entirely affected and some are not.
4 - Moving affected files from an HDD to a SSD has no effect on this bug. It still happens on a SSD.

In advance, I must say, I'm very grateful for all the hard work you have put into developing this awesome music player. Thank you.