Latest WACUP public preview for x86 & x64 is build #22022 (June 29th 2025) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #22022 (June 29th 2025) (x86 & x64 changelogs)

NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

Recent Posts

Pages: [1] 2 3 ... 10
1
General Discussion / Re: WACUP Modes
« Last post by dro on Yesterday at 12:53:00 PM »
It's got compatibility in the name because that's what I view that exe as being there to help with so the likes of reasonable behaving plug-in installers can work when they find a winamp.exe in the program folder.
2
General Discussion / Re: WACUP Modes
« Last post by Aminifu on Yesterday at 12:41:14 PM »
Ok, so there is no real difference. I have been launching WACUP from a wacup.exe shortcut pinned to my task bar for years.

The recent talk about interactive buttons on the OS toaster and start menu entries caused me to look in my start menu. I guess the entry for the other mode (which launches the winamp.exe file in the WACUP folder) has been there all along.
3
General Discussion / Re: WACUP Modes
« Last post by dro on Yesterday at 12:22:56 PM »
It just determines the default icon / process filename that's used for the x86 loader (wacup.exe vs winamp.exe) & have been around for far too many years since some still want to have their wacup install appear more like winamp. The wacup core is loaded the same irrespective of what loader exe is used as is the ability to override the running process icon via the preferences.
4
General Discussion / WACUP Modes
« Last post by Aminifu on Yesterday at 12:06:28 PM »
Hi dro,

From looking in my start menu, I see there are now 2 ways to launch WACUP. A WACUP (Winamp Compatibility Mode) (32 bit) process and a WACUP (32 bit) process. What is the difference between them? They both appear to look and work the same way on the surface.
5
Skins / Re: [CHANGES MADE] CPro MMD3 won't load
« Last post by Aminifu on July 18, 2025, 12:53:26 AM »
Quote from: dro on July 03, 2025, 08:49:03 AM
It'll be the 2 elements that are bright pink as part of the player control section. ...

That is fixed in build #22186 (x86). Thank you dro.
6
Visualisations / Re: Martins collection of milkdrop presets
« Last post by Nitorami on July 17, 2025, 08:27:33 PM »
My note was informative only, as I had promised to check this out. I did NOT mean to ask you for fixes of sorts. I know your ressources are limited and visualisation is not on your list of top priorities.
Not a big issue, there are now standalone milkdrop visualisers which simply listen at linein:// and can play all milkdrop presets, plus offer a lot more features, e.g. serge000's milkdrop3. And as far as I can tell from my own tests, serge000 has resolved the AMD issue.
7
Preview Build Discussion / Re: 1.99.32.21640 (x86) issue when launching: taking too long to load
« Last post by DJay on July 17, 2025, 12:02:12 PM »
I mentioned dual monitor desktop because I run WACUP on a secondary monitor, and when this problem occurs during startup, I often see a black media library background (!?) on the primary monitor for a moment, and then nothing, because it stops responding. After half a minute, it reappears on the secondary monitor, but often in stages, because, for example, everything appears except the contents of the media library window.
I did a few OS restarts and it seems that when I run WACUP in safe mode, the problem doesn't occur. It takes a bit longer to start, taking ~3 seconds, but it doesn't go to not responding state.
8
Preview Build Discussion / Re: 1.99.32.21640 (x86) issue when launching: taking too long to load
« Last post by dro on July 17, 2025, 11:27:14 AM »
I use a dual monitor setup daily so I'd like to think I'd catch that being a problem & with what the dmp showed the ui aspects hadn't yet been created & is just that something is causing the loading of the needed dll to just take far too long which a first run after an OS restart makes some sense from A/V software needing to update definitions / start scanning vs drive caches still waiting to be built-up. So far not doing the pre-loading of the dll doesn't seem to break things from what I can see with testing but I suspect you're still going to have issues since I can't really determine why the OS call to load the dll was just sitting there & it's just me guessing on a few things for the time being.
9
Visualisations / Re: Martins collection of milkdrop presets
« Last post by dro on July 17, 2025, 12:17:20 AM »
I don't have AMD based gpu hardware to test it on so I don't know why it's broken when as afaict it worked with what I did have years ago. Maybe the AMD / OS drivers have changed much more in that time since I think I'd done those patches on my old Win7 dev machine. Unless I'm provided with a better patch than what I'd attempted (am not expecting that'll happen) I've no plans on looking into it any time soon as I'm not in a position to by buying hardware just for a vis plug-in.
10
Visualisations / Re: Martins collection of milkdrop presets
« Last post by Nitorami on July 16, 2025, 11:58:43 PM »
@DrO for info:
Regarding the compatibility of PS4 presets with AMD video cards, I tried WACUP's milkdrop implementation on my father's AMD Ryzen 3 5300U with Radeon graphics. Unlike winamp, it does not crash or show a black screen, but it neither works as it should, it seems the PS4 shader parts are simply deactivated. So in case of PSVERSION COMP=4 the comp shader is skipped and the output of the warp shader is displayed instead.

Pages: [1] 2 3 ... 10