Latest WACUP public preview for x86 & x64 is build #24496 (May 8th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24496 (May 8th 2026) (x86 & x64 changelogs)

Recent Posts

Pages: 1 ... 7 8 [9] 10
81
I run both WinAmp 5.666 and the latest WACUP on my main library system under Win 11.  I run just WACUP as my player on 5 other Win 10/11 systems.

I still use WinAmp for maintaining my library meta data and artwork management. I've used it for so long and I am very familiar with the interface I saw no reason to move away from it.

WACUP I use as a pure player.  It runs smoother than WinAmp and handles my large libraries much better especially over network connections. WACUP I find is less buggy than Winamp and getting better on a regular basis. I usually update immediately as updates become available. (I have 5 redundant setups if something goes awry.)
82
I use the skin Modern Winamp and the Video Windows is not on the same screen than the "main" winamp windows (don't know if it's important)

The only "tune" is  a gen_ml.ini files from Winamp / Plugin  to WACUP / Plugi0n in order to have Smart Views.

I linked a screen shoot of the Video Préférences as requested...
83
It can also be installed as a portable install to make it simpler to try it out without touching anything else that's present on the system.
84
Not having had it reported to me as not working the newest build wouldn't have made any difference as nothing had been done about it. I'll need a screenshot of the video page of the preferences window done as an attachment here along with what skin is being used.
85
Hi !

Not a big problem now but... I discovered this fabulous music player with de 1 99 47 version. Everything was ok for me (x86 version).

I didn't update as soon as possible, but I did a few weeks ago and got this problem : Video windows do not close after the end of the play... (All options OK, On/OFF same problem, so i came back to 1 99 47..)

Today I try today's new update : Same problem... So back to 1 99 47 (windows close again)...

For your information... Thanks.
86
Well, for my use the 32bit version works fine (only the 32bit version supports modern skins).  When I upgraded my PC from Windows 7 to Windows 10 back in 2019, I never reinstalled Winamp and just installed WACUP on it.  There are features I use in WACUP that are built into it that Winamp required particular plugins that are no longer around (the HTTP Post stuff).

Anyway, the best advice I have is probably to just try it.  The 32bit version is the one I would try first and make sure if you do install it, to place it into its own program directory like "C:\Program Files (x86)\WACUP" and NOT on top of your Winamp installation so that it remains untouched.   That way you can play with it and not muck up Winamp.


87
I'm a user of the original Winamp from back in the 2000s era and I still use the original installers that I have backed up on my PC's. I can't bring myself to switch to any other media players. I'm just curious as to the progress that this project is making - is it time that I switch over to WACUP or should I just stick with what works and keep using the OG original Winamp? Just looking to hear some people's opinions. Thank you
88
You can use the email from the site homepage (if it's a smallish file) or pm a link if uploading it. Compressing any dmp file collected is needed as they compress quite well. Also the build has been updated so it'd be better to try to replicate with that vs the now prior one.
89
Changing the output plugin doesn't really help.
Strangely, running in procdump mode doesn't immediately crash anything when I play a song. It only happens outside of that mode. it also shows an empty crash.log file sometimes when I attempt to run it in that mode. Where do I sent the process dump Task manager produces?
90
Other than running it always with the crash report collector mode (start menu shortcut or manually running the /procdump command-line mode or trying to get a process dump from task manager if it manages to stay running long enough) until I've got a crash report to work with the only obvious thing would be trying a different output plug-in (e.g. if it's set to use notsodirect try using notsoyasapi & vice versa depending on what's already set to be used).
Pages: 1 ... 7 8 [9] 10