Messages

1

Preview Build Discussion / Re: CD related feedback

« on: September 05, 2026, 09:35:05 PM »

I've not actively tested cd playback nor the views in a while so it's very likely from other core changes made since I did that things may have regressed / broken. Problems with artwork was also reported but I've still to get a drive hooked back up in my machine to do any testing of the handling.

As for comparing to 5.666, none of the cd or media library handling relates to it & hasn't used any 5.666 plug-ins to do it for long time now (since the x64 build appeared) so problems with any of this are all down to my code alone.

The enter / double-click handling has some control options on the media library root prefs page so that might get it to how you need as I can't remember what I set the default to be (there's things that I default differently compared to what winamp did as that's what I prefer most of the time).

2

Preview Build Discussion / Re: Online radio streams not playing in 1.99.54.24960 (worked before)

« on: September 05, 2026, 06:18:37 PM »

The only thing I've been able to replicate is that some icecast urls are being provided as 'http' but they're only going to respond to a 'https' connection & I've provided that as a post-release update which better deals with that situation (though the icecast instance providing the wrong url despite accessing it directly over an https connection is a bug with icecast imho).

I still cannot replicate any of the provided urls failing to play when in_url is present be it on Win10 or Win11 (which is where I happened upon by chance the 'broken' icecast url). Without clarification of what the status of in_url in the install is (which I ask for a reason to try to save wasting more of everyone's time), there's nothing else I can do & won't be for at least a week (maybe more) due to irl commitments.

3

Preview Build Discussion / Re: Online radio streams not playing in 1.99.54.24960 (worked before)

« on: September 05, 2026, 02:07:07 PM »

wd9895: The station list is updated daily against what I'm able to obtain from a number of sources so unless they're all messing up then that shouldn't be the problem. Examples would be helpful of ones that aren't behaving so I can inspect them.

vikingt: With what's shown it really shouldn't be trying to use the directshow decoder for url playback & would explain why nothing is happening. You need to check that wacup's in_url plug-in is present & enabled & loaded which can be done by going to preferences -> plug-ins -> input -> look in the list for in_url / streaming url processor. If it's not there then you'll need to re-run the installer & hopefully that should correct what is most likely the OS / 'smart app control' (since you've mentioned Win11) messing around with dll loading when there's no reason for it to do so.

4

General Discussion / Re: ver 1.99.54.24960 modern skin MAKI issue

« on: September 05, 2026, 10:43:12 AM »

I've got a simplish fix for you so the skin can work with 24960 by extracting the skin into a 'Quadelic' folder (a .wal file is just a .zip archive) within the wacup skins folder, then open the 'xml\configuration.xml' file within the 'Quadelic' folder & change the <elements/> to be </elements> & save it. Then select the folder extracted version of the skin (it should show with a folder icon next to its name in the skins menu) & that should then load correctly.


The problem is the / in the end elements part is invalid & what I now use for xml parsing doesn't like it but it's also possible that what had been used in earlier builds has been tightening up xml validation so might be why you had to go back a few builds to get it to work again (I've not tried the older builds to see what they're doing but it's a reasonable assumption with the changes that libexpat have kept making & which led me to want to drop it over all of it's security related churn). I still need to code in something that can handle this problem since it'll be expected for such skins to still be able to be loaded though imho the skin should never have been able to be loaded due to the error in the xml but that's another thing against libexpat being a lax parser.

5

General Discussion / Re: ver 1.99.54.24960 modern skin MAKI issue

« on: September 05, 2026, 10:09:53 AM »

If going back to 24496 works then it's not just due to the xml parser change. I know there were some reports of some of the transparent skins not working correctly (not that modern skins ever work 100% under wacup due to how it's gotten the gen_ff plug-in to work outside of winamp) but I wasn't aware of there also being xml parsing issues. Have got the skin & will hopefully get it resolved for the next preview build as the error is coming from one of the skin's xml files not having the expected xml headers so I need to adjust my handling to deal with that.

6

Preview Build Discussion / Re: Online radio streams not playing in 1.99.54.24960 (worked before)

« on: September 05, 2026, 10:03:44 AM »

All of them appear to play ok for me from a quick test. If you go to Preferences -> About|Updates -> About tab -> what is shown as the active input & output plug-in at the bottom of that prefs page when you're trying to play these streams? Also is the version info block on that prefs page populating correctly?

7

General Discussion / Re: Radio issue...

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

8

General Discussion / Re: WACUP 1.99.54.24960 crash

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

9

General Discussion / Re: ver 1.99.54.24960 modern skin MAKI issue

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

10

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.

11

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.

12

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

13

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

14

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

15

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.