Messages

1

Preview Build Discussion / Re: WACUP prevents Windows screen saver from activating

« on: June 27, 2025, 08:42:51 AM »

nice, thanks dro! It's a very useful feature, not annoying at all, it's awesome that we can modify it!

2

Preview Build Discussion / WACUP prevents Windows screen saver from activating

« on: June 27, 2025, 07:48:56 AM »

I did a powercfg /requests test and WACUP.exe came up in the Display test. Can this be disabled in the settings? see attached image below

edit: WACUP.exe needs to be closed for it to disappear. But that's not practical when you have music playing all day

3

Preview Build Discussion / Re: Bug: WACUP keeps handle on folder for recently played file

« on: June 27, 2025, 06:52:50 AM »

It uses a fallback via in_wave as that was needed to allow the x64 build to be able to play MP3 files since it doesn't have a dedicated in_mp3 replacement (lack of tag editing & some steaming features are the obvious things missing in that mode for either build types without an in_mp3).

dro, I have a new theory. I recently downloaded some registry cleanup tools to see what software traces were left behind and to my shock the tool found more than 1000 winamp traces in the registry. When I discovered WACUP, I simply uninstalled Winamp through the basic Win 11 surface and then proceeded to install WACUP over it. I'm aware that WACUP may use shared registry or other traces with Winamp so I didn't dare to clean the registry, but I figured: What if past Winamp traces are messing with WACUP? Also this would explain why so few people report this problem: Most of your users probably don't come straight from brutally outdated Winamp but other more recent software so there is no conflict. Just a theory of course

4

Preview Build Discussion / Re: Bug: WACUP keeps handle on folder for recently played file

« on: June 27, 2025, 06:47:44 AM »

Thanks for looking into this.

I tested with disabling in_mp3.dll and the problem goes away. Enabling it brings the problem back so seems indeed to be the culprit.
Evidently WACUP could play mp3s without it so I keep it disabled for now.

Let me know if you need help testing this as repro is 100% for me.

It worked for me too, initially. Then after a few more days it stopped working. Keep testing.

5

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« on: May 28, 2025, 10:26:51 AM »

dro, I appreciate the effort! And I understand that you have to focus on more popular issues. In the meantime, I will experiment with disabling plug-ins.

My issues started with the second to last update. I'm wondering if there were any plug-ins that were added or enabled with that update... this could be a good lead

6

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« on: May 28, 2025, 06:24:38 AM »

I did a complete reinstall of WACUP. It worked normally after that. Then another win reboot and... I'm back to square one.

unticking in_mp3 didn't help this time either.

7

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« on: May 27, 2025, 06:31:39 AM »

Update: After a complete shutdown of the PC the problem is back the next day.

install.ini file contents

[StartMenu]
Name=WACUP (32-bit)
[sections]
decoderMp3=1
decoderMp4=1
decoderFlac=1
decoderOpus=1
decoderCdda=1
decoderCapture=1
decoderAPE=1
decoderMPC=1
decoderOgg=1
decoderTTA=1
decoderWav=1
decoderWMA=1
decoderWV=1
decoderDSD=1
decoderZIP=1
decoderADLIB=1
decoderASAP=1
decoderQsf=1
decoderSid=1
decoderNCSF=1
decoder2SF=1
decoderGSF=1
decoderHively=1
decoderMidi=1
decoderMod=1
decoderMSX=1
decoderNSF=1
decoderORG=1
decoderPsf=1
decoderPxTone=1
decoderSC68=1
decoderSNSF=1
decoderSPC=1
decoderVGM=1
decoderVGMStream=1
ReplayGain=1
decoderURL=1
decoderAudio=1
centercut=1
enhancer=1
decoderM4v=0
decoderDirectShow=0
decoderNsv=0
winampMp3Encoder=1
encoderAac=1
encoderFlac=1
encoderOgg=1
encoderOpus=1
encoderTTA=1
winampWavEncoder=1
outputNotSoDirect=1
outputWavey=1
outputASIO=1
outputWASAPI=1
outputDisk=1
outputNeo=1
mediaLibraryLocalLibrary=1
mediaLibraryPlaylists=1
mediaLibraryHistory=1
mediaLibraryBookmarks=1
mediaLibraryPodcast=1
mediaLibraryRadio=1
mediaLibraryPortable=1
portableDeviceP4S=1
portableDeviceUsb=1
portableDeviceCreative=1
portableDeviceIPod=1
mediaLibraryExporter=1
FreeformSkins=1
Crystal=1
JTFE=1
Undo=1
PLFR=1
PlaylistExclude=1
Repeater=1
TipTop=1
Yar=1
ClassicArt=1
Lyrics=1
BigClock=1
WaveSeek=1
Thinger=1
GlobalHotkeys=1
Taskbar=1
Windows=1
TRAP=1
YuleLog=1
secGenWC=1
secDspWC=1
secMilk2=0
secMilk2Presets=0
secCSA=0
secGeiss=0
visAVS=0

8

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« on: May 26, 2025, 07:10:17 PM »

dro: Sorry mate I hope I'm not annoying you too much. It was a while back when I first installed wacup, and I may have done a unique install with lots of stuff crossed out, yes... Forgot about this aspect sorry!

in_wave.dll is ticked and enabled

should I reinstall with everything enabled as offered in the installer?
or should I disable "Media Library support"? perhaps?

9

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« on: May 26, 2025, 06:45:58 PM »

dro: you mentioned in_mp3 couple weeks ago when we first tried troubleshooting. I remember it briefly working but after a restart it stopped working. I re-enabled in_mp3. Yesterday, with the newest version I attempted unticking the in_mp3 trick again, but it resulted in a new bug: Doubleclicking an mp3 in Windows enqueued it, but didn't start playback. I had to doubleclick again in wacup to start playback. So I quickly re-ticked in_mp3

10

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« on: May 26, 2025, 06:38:58 PM »

Aminifu It wasn't enabled, but wacup required me to restart when unticking it.

dro: Files are not removed through the playlist, but in Windows Explorer.

Play FileA from FolderA.

Play FileB from FolderB.

Try deleting FolderA → Fails until WACUP is closed. (Deletion is attempted while having FileB play, and also while it's stopped. Only closing or restarting wacup helps


Additionally: FileA can be deleted while running FileB. But empty FolderA can't be deleted unless wacup is closed or restarted.
I run wacup barebone. No visualization, timer, media library or anything fancy running.Even the equalizer window is closed

11

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« on: May 26, 2025, 06:16:27 PM »

Aminifu: I unticked gen_play_remove.dll, restarted wacup played fileA in folderA, then doubleclicked fileB in FolderB and deleted folderA, and it worked! I tested 3 times! I can't currently restart my PC but let's see if this state remains after a restart. Looking good so far! Thank you!

dro: you were always directing me towards plug-ins and you may have been right!

12

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« on: May 26, 2025, 06:04:56 PM »

No, never tried it. I can't locate it in the Plug-in menu... Where is it exactly?

found it. Untick only or delete?

13

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« on: May 26, 2025, 05:46:01 PM »

Thanks for the response dro. I'm using the latest build, and yes, I still have the problem.

You really can't recreate it? This is so weird.

Regarding Media Library

I don't have a Folder Monitor submenu, weird. See attachment below. But I'm sure the folder is not listed in it.

14

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« on: May 26, 2025, 05:04:48 PM »

I just couldn't get used to this problem and I decided to give it another shot and investigate further to help you find a possible fix. I used ProcMon to reveal what is happening exactly on a folder level and used AI to analyze the results. This is what AI came up with. Are these results plausible?

The CreateFile log entry you shared reveals:

WACUP opens the folder with Execute/Traverse (not aggressive, but it keeps the handle).

ShareMode allows deletion (Read, Write), but the folder still locks → Likely a handle leak in WACUP’s directory monitoring.

No CloseFile event → Confirms WACUP isn’t releasing the handle properly.

Steps to reproduce:

Play FileA from FolderA.

Play FileB from FolderB.

Try deleting FolderA → Fails until WACUP is closed.

Your theory:

"WACUP holds a folder handle (for scanning/monitoring) but doesn’t close it, blocking deletion until the app exits."

What the Developer Should Fix
Ensure CloseHandle() is called after folder scans.

Add a timeout to release idle directory handles.

Make folder monitoring optional in settings.

I attached the The ProcMon screenshot below

AI results in more detail:

Breaking Down Your CreateFile Log Entry
Here’s what each field tells us:

Field   / Your Value / What It Means
Desired Access / Execute/Traverse, Synchronize / WACUP is only browsing the folder (not reading/writing files).
ShareMode   / Read, Write  / Other apps can delete/modify files in this folder (so WACUP isn’t locking it).
Options / Directory, Synchronous IO Non-Alert / WACUP opened the folder as a directory (not a file) and waits for responses.

Why the Folder is Locked (Despite These Permissions)

Synchronize Flag

This allows WACUP to hold the folder handle open while it checks for changes (e.g., new files).

Even though ShareMode allows deletion, Windows may still block it if the handle isn’t closed properly.

WACUP’s Behavior

The player likely scans the folder periodically (e.g., for playlist updates) but fails to release the handle afterward.

15

Preview Build Discussion / Re: WACUP is almost perfect, 2 minor issues

« on: April 19, 2025, 01:04:08 PM »

If you're doing it whilst the file info dialog is still open then that is usually going to have the file in an open state because it might be trying to make edits. Tbqh I've still to actually look into this myself so I don't know why it'd be keeping a handle on the file vs how I've tried to code things.

I only opened the file info dialog to provide as much info as possible, but it's the same with or without it, wacup.exe is still using the file or folder.

I appreciate you trying to help, I understand that this is no top issue so I will try to get used to it. Thank you for your time and thanks for your amazing work on wacup, you really dragged winamp into the 21st century!