Recent Posts

51

Skins / Re: Winamp Community Skin Pack

« Last post by Pawel on September 04, 2026, 05:44:15 PM »

It's been a while... Does no one really have any suggestions?
Is everyone relying on my imperfect choice?
Come on... There must be plenty to choose from

-Pawel

52

General Discussion / Re: Radio issue...

« Last post by dro on September 04, 2026, 10:15:22 AM »

WACUP isn't a fork to clarify that point. What version & build type are you using? My initial thought is whether the stream url you tried to access is even a valid stream (they can & will just go offline) or has something blocked wacup from connecting which would make anything fail (one way to see if that is the case is going to Preferences -> About|Updates -> About tab & seeing if it can see the current builds available block). It would be useful to know what the url trying to be played is (e.g. from the alt+3 or edit playlist entry dialog) to see if it's even a valid url anymore.

53

General Discussion / Re: WACUP 1.99.54.24960 crash

« Last post by dro on September 04, 2026, 10:04:06 AM »

If the output plug-in change isn't helping then it's likely something else that I'm not seeing / not aware off due to a lack of crash reports. The 24960 build has also had some post-release updates made available since yesterday (3rd) which can be obtained by going to Preferences -> About|Updates -> About tab -> follow the instructions on the button shown to get them though whether it'll help or not I don't know.

54

General Discussion / Re: ver 1.99.54.24960 modern skin MAKI issue

« Last post by dro on September 04, 2026, 10:01:39 AM »

Can you attach a copy of the skin as I don't have a deviantart account. Without knowing what version you were previously using & not being able to currently try the skin I'm going to assume it might be related to the current 24960 build changing from using the expat xml parser to the pugixml one & that it might not be doing something like expat did. The skin loading error is a gen_ff triggered messagebox & such skins can complete loading if there's some issues but things can then be unresponsive (it's like loading a web page & bits of the javascript are missing). The only fix I can suggest is going back to the prior build that was working for you (old downloads are linked back to on the preview download pages).

55

General Discussion / ver 1.99.54.24960 modern skin MAKI issue

« Last post by petormeat on September 04, 2026, 08:29:07 AM »

I updated my wacup as soon as I was notified of an update being possible. I usually use this modern skin that has transparency options and a specific menu window to select its color themes, this window is now not accesible, the transparency is gone and this shows up when using this skin (ignore that null pop-up at the beginning, it's always said that but the skin worked completely fine before, I am referring to the black and red error). Would like to know if anything is possible to fix this.

link to skin: https://www.deviantart.com/takanory/art/Quadelic-36391651

56

General Discussion / Radio issue...

« Last post by DatBoi302 on September 04, 2026, 12:54:27 AM »

I hate to come here and complain about such an awesome fork, especially given how little information I have to offer, but I am at a loss for what to do at this point, and audio related code/files are not my specialty.

I've been enjoying using the WACUP radio stations, all good. Well 2 days ago, I went to switch channels, and the channel just hung saying connecting... connecting... and never connected. I spent some time doing the normal stuff, restarting, switching internet settings around, nothing. Fast forward to today and I'm in my registry messing with DCOM permission entries just on the vague chance that they might have correlated with the timeline of each reconnect I attempted (they don't, I'm just losing my mind).

So basically, I have no clue what to do, or what could be wrong. I did touch a single thing other than switch the station, and that permanently bricked me radio....
Surely I could just re-install WACUP, hopefully it won't be destructive, and maybe that will fix it, but idk.

If anyone has any suggestions, please let me know.

- Thanks

57

Resolved Issues / Re: Big Clock Playlist Elaspsed and Remaining times are incorrect - build 1.99.53.24

« Last post by vikingt on September 03, 2026, 06:50:05 AM »

Yes, it's work fine, thank you!

58

General Discussion / Re: WACUP 1.99.54.24960 crash

« Last post by Nukesforbreakfast on September 01, 2026, 06:42:55 PM »

I'm using the x64 build. I tried switching from notsodirect to notsoyasapi and the behavior was the same. I did uninstall via the installer and selected remove profile info, but when I reinstalled a non-portable install it launched remembering the playlist + current song + current song time. I'll try again and see if I missed something, and I'll try a portable install to see if that changes behavior. Thanks!

59

Preview Build Discussion / Re: High CPU usage

« Last post by kobber on September 01, 2026, 09:34:30 AM »

Thanx for the answer. I will update to last build and take a look at its behavior

60

General Discussion / Re: WACUP 1.99.54.24960 crash

« Last post by dro on September 01, 2026, 08:20:06 AM »

Is it the x86 or x64 build type? Also what version of Windows are you using & does making a portable test install via the installer modes make any difference to how it behaves? Otherwise the simple option is to go to preferences -> plug-ins -> output -> select notsoyasapi from the dropdown if notsodirect is the selected one & if notsoyasapi is the selected on then change the selection to be notsodirect.

If the action to restart or manually run via the procdump mode isn't working at all then that makes me assume the OS is getting in the way of things or procdump can't be obtained or there's a dependency loading issue which is causing the failure (something I'm not seeing).

I don't know what clean install instructions you were trying to follow but if the uninstaller is used then it prompts whether to keep the settings folder or not otherwise it'll do what it can to remove the whole program folder (assuming this wasn't a portable install anyway) & will indicate if there was anything left (not that it should typically relate to settings persisting). Am also assuming it's wacup's resume mode being used & not from a 3rd party plug-in which can & often will use the OS registry so isn't something that the uninstall knows about.