Messages

1

General Discussion / Re: I need some help with WACUP

« on: May 08, 2026, 10:39:41 AM »

Thank you for your reply, these options did the trick for my preferred behavior, and as for the audio files and icons association I used FileTypesMan by Nir Sofer (maybe someone finds it helpful).

2

General Discussion / I need some help with WACUP

« on: May 08, 2026, 09:01:36 AM »

So I noticed I had an installation of Winamp in C:\Program Files (x86)\Winamp
Don't know where that is from as I don't remember installing it... so I uninstalled it and with it all my previously customized WACUP behavior is gone:
1. File Type Associations for audio files and playlists with the selected icons (old Winamp icons)
2. Enqueue files (associated audio files and playlists) when double-clicking them in Windows Explorer, now it just starts a new playlist

I tried reinstalling the latest WACUP and there is no "File Types" under General options.
How can I recover from this?

3

Resolved Issues / Re: Volume Control?

« on: April 04, 2026, 09:46:35 AM »

Thank you very much for your solution, YES - Shift worked for my situation, volume increased/decreased by 1%

4

Resolved Issues / Volume Control?

« on: April 03, 2026, 08:42:07 PM »

Is there a way/setting in WACUP that can control volume increment by 1%?
Right now I am using the latest beta release 1.99.47.23960 32-bit with Big Bento Redux Wacupified skin, and the volume is increased/decreased by 3% using the mouse scroll wheel. Is this a WACUP behavior or skin behavior?
PS: I don't have any other 3rd party audio plugins in WACUP nor installed in Windows that can alter WACUP audio/volume settings.

5

Preview Build Discussion / Re: Crashing issues

« on: March 14, 2025, 08:59:00 AM »

sorry for my mistake, thanks for your reply, I deactivated that option - no issues so far.

6

Preview Build Discussion / Crashing issues

« on: March 13, 2025, 09:13:11 PM »

I can't use WACUP v1.99.27.21136 (32-bit native) - it randomly crashes after some time

wacup.exe experienced an access violation (0xc0000005) possibly in propsys.dll at 13/3/2025 15:25:04 after running for 9:35
Read from location 0x000000F0 caused an access violation.

I've attached the generated crash report.