Some bugs I encountered with the latest builds.

[mkpetrov]

Hi.
A few weeks ago I retired my Winamp and switched to WACUP as my main player.

In some aspects it is already more stable than Winamp (Like adding/playing a huge playlist in queue, which takes much time on winamp even on modern PCs) and stable enough for everyday usage.

What I encountered that still needs to be fixed:
-Global hotkeys randomly stop responding to "next song" hotkey and I have to restart WACUP for it to resume normal operation. Haven't had that happening in Winamp.
-Opening multiple files from folder only leads to 1/2/3 files being played and not all of the files selected.
-Clicking "Explore item(s) in folder opens the folder, but without the song selected.
-On two underpowered laptops, manually skipping to next song leads to crash if I skip 3-4 songs. Doesn't seem to occur on my everyday PC.
I'm using the latest preview build in portable mode on all PCs and they all run Windows 11. The first 3 bugs I can only confirm are present on my everyday PC, haven't tested on the laptops.

[mkpetrov]

On "Next song" issue I discovered It's not a problem related to Global hotkeys - Just tried clicking the next button in WACUP and It didn't work either, despite Queue having multiple items in it.

[dro]

If the next button / hotkey isn't working then something is blocking the action from being run which shouldn't be happening & implies to me that either the skin being used is broken (possible if it's a modern/winamp3 style of skin) or that a plug-in is breaking things. What skin are you using & also have you installed any 3rd party plug-ins &/or enabled the built-in streaming mode that WACUP includes?

-Opening multiple files from folder only leads to 1/2/3 files being played and not all of the files selected.

Could probably do with a short video showing this issue then trying to get you to further describe what's going on please.

-Clicking "Explore item(s) in folder opens the folder, but without the song selected.

Which part of the program are you triggering that action? Also are the files actually there or are they missing? Though if it's opening the folder then that probably means the files are there (as there's a change for the next build to deal with opening a folder with passed in missing files) & it might be a Win11ism screwing with the api that's used &/or the OS api isn't working & wacup is reverting to its fallback handling to open the parent folder which via that mode cannot select the files.

-On two underpowered laptops, manually skipping to next song leads to crash if I skip 3-4 songs. Doesn't seem to occur on my everyday PC.

Are those generating crash reports? If they are then I could do with an example copy via pm please. As wacup will try to auto-upload copies to the site server but I don't really have context on who a crash report relates to so for this it'd be easier if it has created some to get a copy. Preferences -> Advanced -> Error Reporting -> that has a link to open into the wacup crash reports folder if there were any generated.

-dro

[mkpetrov]

Are those generating crash reports? If they are then I could do with an example copy via pm please. As wacup will try to auto-upload copies to the site server but I don't really have context on who a crash report relates to so for this it'd be easier if it has created some to get a copy. Preferences -> Advanced -> Error Reporting -> that has a link to open into the wacup crash reports folder if there were any generated.

-dro

No crash-reports, unfortunately, it just  hangs for a second or two and then closes.

If the next button / hotkey isn't working then something is blocking the action from being run which shouldn't be happening & implies to me that either the skin being used is broken (possible if it's a modern/winamp3 style of skin) or that a plug-in is breaking things. What skin are you using & also have you installed any 3rd party plug-ins &/or enabled the built-in streaming mode that WACUP includes?

Just discovered this was my fault - I've just forgotten to enable "repeat".

Which part of the program are you triggering that action? Also are the files actually there or are they missing? Though if it's opening the folder then that probably means the files are there (as there's a change for the next build to deal with opening a folder with passed in missing files) & it might be a Win11ism screwing with the api that's used &/or the OS api isn't working & wacup is reverting to its fallback handling to open the parent folder which via that mode cannot select the files.

Yes, the files are there, just not selected. I made videos with that problem and the problem with opening multiple files from folder:

[dro]

No crash-reports, unfortunately, it just  hangs for a second or two and then closes.

If you go to preferences -> advanced -> error reporting -> follow the procdump related instructions or you can run wacup.exe /procdump from the command-line within the WACUP program folder to do the same which'll then try to capture what might be going on when the currently unhandled close happens. If it does fail under it, the next time you run wacup it'll then auto-submit the crash report but it'll be helpful in this instance if you can also manually pm me a copy of the first one that is created.

Just discovered this was my fault - I've just forgotten to enable "repeat".

Oh so it was just getting to the end of the playlist then yes that's correct behaviour if repeat is off.

Yes, the files are there, just not selected. I made videos with that problem and the problem with opening multiple files from folder:

That looks like it's how Win11 might be handling things against the OS api call with the second video & I don't see anything obvious from a quick search of the api I'm using that'd explain it not pre-selecting the files. For that I don't have a suggestion on anything else to try out at this time.

With the first of the videos, multiple selections from explorer are a mess across all of the Windows versions that WACUP is supported to run under & also likely relates to the lack of OS file association integration. From my notes, a selection of between 10 & 15 items is the maximum before the OS typically expects a shell extension to be provided even though it could just call WACUP with a multiple list of those files as it does for smaller selections. The newer the OS the lower the limit seems to have become.

I don't remember if there was a registry setting that could be used to change that OS behaviour or not. So this is working in an expected broken manner as the handling currently is solely relying on the OS / Explorer providing the full list of the files & I don't have any direct control over that. Tbh it might be a bit of a handling change but drag+drop is going to be more reliable to do things.

-dro

[mkpetrov]

No crash-reports, unfortunately, it just  hangs for a second or two and then closes.

If you go to preferences -> advanced -> error reporting -> follow the procdump related instructions or you can run wacup.exe /procdump from the command-line within the WACUP program folder to do the same which'll then try to capture what might be going on when the currently unhandled close happens. If it does fail under it, the next time you run wacup it'll then auto-submit the crash report but it'll be helpful in this instance if you can also manually pm me a copy of the first one that is created.

Yes, that worked, here's the report it created: <link removed>

[dro]

That crash report seems to be a loading failure due to the stereo tool dsp plug-in possibly trying to use a CPU instruction that doesn't exist (e.g. AVX2) though what it actually was I can't easily determine at the moment. It also seems to be an older version of that plug-in vs what's currently offered though I don't know if that's going to be part of the issue or not & from prior experience the stereo tool dsp is really not friendly when it comes to resource usage & only seems to have gotten worse with time.

Either way you could either try updating the stereo tool plug-in or the simpler option in trying to run wacup with it disabled & then trying the procdump related mode again to see what that might capture.

-dro

[mkpetrov]

Just tried with Stereo tool disabled, but it's happening again. Here's the new report, it's a lot smaller this time:

[dro]

That one is failing whilst trying to load the Big Bento Modern Windows 10 Edition skin which is just something that can happen with those skins & the re-used plug-in from 5.666 that WACUP tries to support to allow for modern/winamp3 style skins to work under it.

It seems like its having an issue doing something with determining font information for a string in this instance & I've seen other crash reports like it but isn't something I've seen myself nor have anything obvious I can do to try to patch around the plug-in.

If it keeps failing on loading with that skin set under the procdump mode then you're going to have to switch to a classic/2.x style of skin though I'm now wondering if it might just be that the setup doesn't like modern skins as can happen for some even though anything modern should be more than capable of running them when a PIII @500Mhz or so was more than capable.

-dro