Messages

1

Preview Build Discussion / Re: bugs in version 1.99.45.23528

« on: Yesterday at 08:18:32 AM »

That's not how it's working for any of my test setups so what is it about yours that is consistently causing the default behaviour to break...

Make a portable test install via the installer option to do that which won't touch the existing install & see if that also is broken for you or not.

2

General Discussion / Re: WMA breaks WACUP 1.99.52.24626 (x64)

« on: July 16, 2026, 06:00:26 PM »

The problem is within the in_what (directshow decoder) plug-in but is possibly tied to a change in the core so it'll need a new build instead of just a post-release update from what I can see at the moment. It keeps crashing for you on loading with the file(s) in the main playlist as it's trying to generate a waveform seeker preview when started which is then hitting the problem with how the internal player is being destroyed. It's not necessarily a new issue as I saw some of this when I was making the plug-in but the x64 build is more prone to it afaict.

3

General Discussion / Re: WMA breaks WACUP 1.99.52.24626 (x64)

« on: July 15, 2026, 07:02:26 PM »

It's not something I've tried in an age so it regressing isn't too surprising with some of the other changes that have been made to avoid other crashes affecting the recent builds. Though I've just re-checked a few example files & those played ok in the build.

You'll need to run it via the crash report collector mode (it'll be a shortcut in the start menu or by manually running wacup.exe /procdump or by going to preferences -> advanced -> error reporting & following the steps at the bottom of the prefs page) to try to generate a process dmp file when trying to replicate the issue in that mode (the event viewer log doesn't give me anything I can actually work with to debug the issue).

Once it's crashed, you'll then need to run wacup so its crash reporter can collect & submit the files - reply back to say it's been done so I can then hopefully match up the crash report from that time (I'll check back on this thread tomorrow as my time's up for today). I also don't see anything obvious from the summary log I get of the few x64 crash reports I've not looked at from today which leaves me to assume wacup's crash reporter isn't able to be triggered by the issue which prevents it from auto-submitting anything to the server (unless internet access for the program is being blocked). It might also be helpful to pm me a copy of a small file that's failing for you so I can also check that out in case it's something to do with the metadata handling for it.

4

Preview Build Discussion / Re: Album Art --> Reading --> Custom (ATF)

« on: July 13, 2026, 11:26:34 PM »

There's no specific documentation as it's just using the atf parser so is mostly down to the user to enter what's needed against what atf allows.

I can't however think of how you'd do it in such a conditional manner & I don't remember how the OS wildcard matching works but I don't think it supports multiple comparators.

I'd probably have to either add a specific *cover|front*.<image> mode or mess around with how the field works to allow for multiple values to compare so the field would be something like *cover*.<image>;*front*.<image> so it's not specifically hard coded for it & is more flexible if other things are needed (just makes lookup potentially even slower).

5

General Discussion / Re: m4a Track Number Issue

« on: July 11, 2026, 10:29:51 PM »

There is no sorting of things based on the metadata during drag+drop actions (has been requested along with deduplication if there's also playlist files in the selection) & it's primarily done based on the order that the OS provides the files depending on how its been selected or sometimes based on the file creation date (more of a thing from old fat32 formatted drives).

Other than having premade playlist files (imho the best way to ensure a known order) & adding them it seems like it's just handling them in the order the OS is giving as I don't know if you're doing it from a selection within the folder or the folder itself for the drag+drop action.

6

Preview Build Discussion / Re: WACUP x86 #24626 update anomaly

« on: July 11, 2026, 10:23:37 PM »

Without the post release updates applied & if you're using the notsoyasapi output plug-in then it has a bug which broke playback with that output plug-in.

Hence the post release update being provided for it which if a crash occurs should've triggered a prompt to install them or it might've detected the output plug-in & reverted things back to the default notsodirect output plug-in depending on what the crash details indicated.

I can't check until tomorrow now if there were an crash reports making it to the site server to see if the ogg crash was caught in some manner to resolve it.

7

General Discussion / Re: Disable creating Start menu items every time

« on: July 10, 2026, 02:06:32 PM »

I'll be clear on this, WACUP is not Winamp so I will do things differently to it based on what I feel needs to be done with it. If you (or anyone else reading this) are not happy with that then you are more than welcome to uninstall it & use something else that better suits your needs. Additionally if you've made a donation then let me know the details & I'll do what I can to get it refunded so you're not out of pocket.


There are a bunch of options to control how wacup will do update checks so you can always just disable all of that & stick on whatever version you've got installed. That is from preferences -> about|updates -> updates tab (with a never option also being added for the next interim build to the post-release updates dropdown at the bottom) or by going to preferences -> general -> internet | online & turning the option off - it still allows you to play streams but it won't then do any update checks, etc.

As I've already tried to explain it's not my fault that the OS has a shitty requirement to do something that I also don't like related to a mode that otherwise I find is beneficial for getting post-release updates installed sooner. I also made changes with the 24616 build that recently went up which tries to auto-hide the shortcut when the fallback handling (as described previously) has been triggered.

So I've done what I can & if you don't like that then there's nothing else I can do & yes you should just uninstall it & move on.

8

Preview Build Discussion / Re: [Bug] Drone_v11 - Colors Messed Up & Borders Keeps Disappearing

« on: July 05, 2026, 09:26:35 PM »

Both problems are due to my attempt to get 5.666's gen_ff plug-in working outside of winamp & there's still a bunch of things I've to figure out when it comes to resolving such compatibility issues especially with the window frames disappearing which can happen with any of the winamp3 / modern style skins though I've only tended to see it happen when resizing the windows. I don't have a timescale for fixing these types of issues.

9

Preview Build Discussion / Re: Problems with Jump to File

« on: July 05, 2026, 09:19:31 PM »

For those following along, there's now post-release updates for the jtfe & in_wave plug-ins with build 24568 which fixes the 2 aspects behind the issue reported.

The main problem was with how the search control dealt with the enter / return key action when the search box was focused due to an old core bug related to keyboard navigation in dialog windows that had already been resolved a while back but the jtfe plug-in hadn't been updated to avoid having to do some of the manual reprocessing it was doing to workaround that issue. It meant it was causing duplicate quick stop+play actions which could cause either a main UI thread deadlock or it hitting a timeout within in_wave's playback stopping handling. tl;dr: having less code fixed the problem.

10

Preview Build Discussion / Re: Issue with Classic Skin Seeking Bar!

« on: July 03, 2026, 05:49:22 PM »

This should now be fixed for the next build now I've found out about a flag in the bitmap header that I should've been checking which seems to be the best way to determine if a bitmap file contains valid alpha channel data or if it's just a 32-bit bitmap with junk alpha channel data (i.e. one that should've been saved as a 24-bit image to save space & avoid any confusion over the format of the data).

11

Preview Build Discussion / Re: Issue with Classic Skin Seeking Bar!

« on: July 03, 2026, 03:53:42 PM »

What skin is this? As most likely it's related to the changes made around the end of last year / start of this that allowed for more faux transparency for the likes of the seekbar element & a few other places for classic skins. Those changes likely aren't handling something that the image files for this skin are doing vs what I've already tried to put in place (e.g. some old gimp created ones) so until I can try things out with a copy of the skin there's little I can do to resolve this.

12

Preview Build Discussion / Re: Problem with tag PUBLISHER in MP4 Files

« on: July 03, 2026, 12:06:10 PM »

This is a regression as part of moving from taglib1 to taglib2 where publisher isn't something that it knows how to handle. It should now be resolved for the next build though I might provide it as a post-release update for the current 24568 preview build.

13

Preview Build Discussion / Re: Problems with Jump to File

« on: July 03, 2026, 10:29:44 AM »

Have you applied the post-release updates to 24568? And if the process enters a hung state that requires you to force kill it, you need to get a process dmp via task manager, compress it & send it to me as I otherwise cannot replicate & so cannot attempt to fix.

14

Resolved Issues / Re: [FIXED] Track Number in Windows 10 explorer is blanked visually when playing MP3

« on: June 30, 2026, 10:24:14 PM »

The v1.99.51.24568 preview build has the fix for this issue.

15

Resolved Issues / Re: [FIXED] Certain local mp3 files will not play in x86 1.99.51.24568

« on: June 30, 2026, 10:21:30 PM »

Thanks for confirming its ok now.