Latest WACUP public preview for x86 & x64 is build #24360 (April 20th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24360 (April 20th 2026) (x86 & x64 changelogs)

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mkpetrov

Pages: [1]
1
General Discussion / Re: Auto update broken?
« on: April 26, 2025, 03:42:48 PM »
Weird, it pops up once daily when set to prompt at startup.

2
General Discussion / Auto update broken?
« on: April 26, 2025, 07:41:20 AM »
I'm getting this error on two different PCs with version .20202

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

4
Quote
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>

5
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:

6
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.

7
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.

Pages: [1]