Messages

1

General Discussion / Re: Radio issue...

« on: Today at 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.

2

General Discussion / Re: WACUP 1.99.54.24960 crash

« on: Today at 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.

3

General Discussion / Re: ver 1.99.54.24960 modern skin MAKI issue

« on: Today at 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).

4

General Discussion / Re: WACUP 1.99.54.24960 crash

« 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.

5

Preview Build Discussion / Re: [Bug] Preferences window is completely missing

« on: August 31, 2026, 10:27:06 PM »

Build 1.99.54.24960 has the fixes for this & a few other prefs window issues reported along with this issue.

6

Preview Build Discussion / Re: High CPU usage

« on: August 31, 2026, 10:25:30 PM »

What wacup version & build type, Windows version & what skin are you using? Additionally is the local library being used & which streaming source are you using (wacup's or a 3rd party). Also to confirm the stream renders ok when it's showing the problem?

The obvious thing would be to see if the 24960 build from earlier today shows any improvement or not. If not then trying to get a couple of process dumps whilst it's in that odd state via task manager & then send them over to me (they compress well but might need to hosted somewhere temporarily if a few have been generated).

It might also be possible to use something like process explorer to see if it's a single thread or if multiple threads in the process are running at full speed (not that the length of time should make a massive difference unless it's maybe not keeping up or it's not able to send it to the icecast instance as fast as wanted & is having to spin).

7

General Discussion / Re: Windows Smart App Control does not allow latest wacup to run

« on: August 28, 2026, 08:55:13 AM »

Code-signing has zero guarantee it'll help & with the way that I'm doing wacup I just am not happy with what is required to attempt to get a code license from having to provide all of my personal information along with the exorbitant cost of keeping it renewed every year (the mess with notepad++'s code license from earlier in the year also imho showed up just how flawed & dodgy the whole code licensing setup is).

As for smart app control itself, it's not smart & is just inconsistent in it's behaviour re: bottom of https://getwacup.com/false_positives.html

8

Visualisations / Re: SmokeEffect

« on: August 26, 2026, 07:55:55 AM »

Do not click configure because your WACUP will crash the software!

This isn't a WACUP issue as it also does it under a winamp 2.9x instance.

If it helps narrow it down: does WACUP produce a crash dump or an entry in Windows Event Viewer (Application log) when you hit Configure? A lot of old Winamp-era vis plugins call into the config dialog with an HWND/API assumption that doesn't quite match how WACUP hosts them (vs original Winamp), so the crash is often specifically in the config path rather than the visualization itself running fine otherwise. If you can grab the exception address/module from the crash (or just enable "keep debug info" if WACUP has that toggle under preferences) and post it here, that's usually enough for someone who knows the plugin API to tell whether it's a WACUP hosting issue or something in the plugin's own config code that never got updated for newer OS versions.

Firstly posting crash dmps onto the public part of the forum is a no-no for a number of reasons. Secondly WACUP's vis handling does things that Winamp didn't to try to better accommodate old plug-ins however a lot of them can & will crash as they either expect to be running in a folder that allows them to save their configuration (aka running as admin which doesn't help this plug-in) or were built in a manner that can conflict with DEP/NX-bit handling since the late XP days (this doesn't seem to be the case here but I'm not going to debug it further than a quick check to see why it might fail & the api handling doesn't seem to be it).

9

General Discussion / Re: Global hotkey for playlist search (J)

« on: August 24, 2026, 03:23:39 PM »

Build type as in the x86 or x64 type of wacup. Though I doubt it matters & assume that you've got different dpi settings between the 2 monitors & it's the caret position that you're referring to which isn't being correctly dpi adjusted.

[edit]
If I'm seeing what I think you're describing then I don't see the issue happen all of the time but it looks like if I change when I tell the OS to not mess with the skinned form of the jtfe window when it comes to DPI scaling to a bit earlier on in the window loading process it seems to resolve the problem I'm seeing.

10

Visualisations / Re: Trying to convert AVS preset to MilkDrop, confusing results

« on: August 23, 2026, 06:30:25 PM »

I've fixed some of the performance issue when trying to enumerate through too many folders with the newer dev build but more needs to be done to improve what's going on so it doesn't cause things to lock-up for a time as can still happen (at least it doesn't get stuck in a perpetual loop as I could quickly replicate).

[edit]
Have made some more changes which should now resolve it crashing when trying to interact with the preset browser whilst it's also trying to scan a folder (especially when it's the appdata one) along with it being much slower than it should do as part of sorting the presets that it's found (e.g. ~8sec to 0.1sec with the change made which leaves me with an ~5sec time to scan all of the appdata folder).

11

Visualisations / Re: Trying to convert AVS preset to MilkDrop, confusing results

« on: August 23, 2026, 05:59:33 PM »

Setting milkdrop to scan the whole of the %appdata% folder really isn't going to go well & that's the only obvious reason I can deem why it caused the crashes that I saw. If it's crashing during the install phase then I don't get crash reports from that. I also have little control if the attempt to re-acquire the needed 5.666 files from one of its installers fails which for the most part is just for the modern skin support now.

12

Visualisations / Re: Trying to convert AVS preset to MilkDrop, confusing results

« on: August 23, 2026, 04:44:34 PM »

That's not the dev build I'm referring to which you get from the beta releases sub-forum. Though why it's throwing a sxs error when I've not seen it from any of my various test installs I don't know as the installer itself doesn't tie into anything that's OS specific (outside of what it's been set to target i.e. Win7 & up) which the one discord report about it was basically lacking anything to try to debug it further.

13

Visualisations / Re: Trying to convert AVS preset to MilkDrop, confusing results

« on: August 23, 2026, 10:17:02 AM »

LigH: As a beta tester you've already got access to the dev build which has the noted vis plug-in handling fix.

sgard: It's a core handling issue where the internal data for the vis handling wasn't being copied correctly causing what is then provided to the vis plug-ins during their render calls to be wrong. Eris has already confirmed the fix with the current dev builds (i.e. what's being worked on after 24784 & which will be part of what is released as a new preview build soonish).

14

General Discussion / Re: Is it possible to preserve play counts while moving music to another drive?

« on: August 20, 2026, 11:06:56 AM »

There isn't a simple means for you to do it & it's something that's been on my todo list for an age. If it's just a drive letter change I might be able to squeeze in something before the next preview build but I cannot guarantee I'll get around to it.

15

General Discussion / Re: Global hotkey for playlist search (J)

« on: August 20, 2026, 11:05:11 AM »

I really don't get what it is that you're trying to describe especially the part about "the cursor is placed between the monitors causing all windows to go invisible". I also need to know what wacup version, build type & skin is being used.