Latest WACUP public preview for x86 & x64 is build #22022 (June 29th 2025) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #22022 (June 29th 2025) (x86 & x64 changelogs)


NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

Recent Posts

Pages: [1] 2 3 ... 10
1
I was wondering if it had something to do with dual monitor desktop, but the problem occurs when running on both primary and secondary.
2
Preview Build Discussion / Re: apply ATF formatting to Stream
« Last post by fchud on Today at 11:00:55 AM »
awesome!
thanx.
3
email or forum pm.
4
It's showing as being stuck in an OS api call used to pre-load a supporting dll the wacup core needs though I'm not sure if I still need to be doing that any more or not for which I'll have to do some testing to see if it can be dropped now. I don't however see why the OS api call is just sitting there other than maybe it's something with an a/v scan check or something else which isn't showing up in the dmp callstack info.
5
Unfortunately, the problem returned right after updating to 22022. I have a ProcDump dump, I will send you the file via PM.
6
I have uninstalled Wacup a couple of times now and re-installed it, and it seems like it's not sending crash reports despite the check mark. What can I do to send a crash report so that you can work out what is occurring?
7
Being able to setup a list of inclusion paths to only scrobble files from would be great instead of scrobbling everything. Like the old audioscrobbler plugin for Winamp 5.56.
Thank you.
8
Preview Build Discussion / Re: apply ATF formatting to Stream
« Last post by dro on July 12, 2025, 04:52:16 PM »
I need to properly look into it but it's likely I've not hooked up stream title updates to trigger an atf update for main playlist items & it's instead just using what the stream is providing as part of the "i've got a new title string to show" message. The custom atf option for the song ticker working is useful to know as that at least indicates that the plug-in doing the streaming is able to provide what's wanted but not good that you've had to do that when it should be just pulling in what's been generated for the main playlist item. Will look to improve things for the next build (no eta).

[edit]
I've now got a fix in place for the next build. It was already meant to be trying to do what was expected but I'd put in a validation check ages ago for some local file issues which was incorrectly being applied to stream updates which prevented the new atf based string for the stream being applied. That also updates the song ticker but you can keep using the custom atf for it if that's simpler when the fixed build is provided.
9
It was reported via email last week & is fixed internally with it being an unintended side-effect of a change to deal with taskbar updates causing things to hang / crash in the prior builds.
10
Not sure if anyone else has experienced this:

When playing any playlist by double clicking the .m3u in Windows Explorer, the files will play fine, but when playing from file 1 to file 2, the taskbar will not update. It still displays file 1 but is playing file 2.

Going from file 2 to file 3 will update the taskbar correctly.
The correct name shows in the player window.
If I manually select next track (file 1 to file 2), the taskbar does update correctly.

Checking the playlist, all looks ok - tracks listed 1 through x. Files are also named correctly in Explorer.

Preview v1.99.34.22022 32bit on Windows 10 21H2
Pages: [1] 2 3 ... 10