Latest WACUP public preview for x86 & x64 is build #21136 (March 9th 2025) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #21254 (March 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.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Cruelboypurple

Pages: [1]
1
Thanks for the headsup, I'll be more mindful about the reports in the future then.

As for the Ajaxamp plugin disabling did not do anything and the issue persisted.

However changing the output plugin did resolve the issue and I have not been able to replicate it since.

So it seems to have been an issue with directsound itself, thank you for your help so far

2
I was able to follow the procdump instructions and could repeat the crash, I'm unsure if it worked but even so I'm leaving the dmp file and zip the last crash generated.

I uploaded the DMP file to Mediafire as the file is too lager to be attached here.

DMP file: (link + attachment removed)

3
I am experiencing the same exact issue, it seems to happen when you handle the playlist in any way and you don't give it time to "buffer" in a way.

For example if I start playing a track and immediatly start click another part of the track WACUP will crash, if I give it a couple of seconds while it plays the track or do it while the track is paused it will not.

This crash also seems to just close the program without the usual message of it sending a crash report to the wacup website so it's likely the reason why you don't see the report, it has been happening a lot and most of those times it never showed the crash report message.

4
You were right, the specific files seem to be scrobbling fine now, my WACUP didn't tell me a new version came out the day I posted so I didn't realise it was already fixed.

I didn't think it was lenght related as it did scrobble a file that over an hour long without issues but all other files seem fine now.

Thank you for your hard work!

5
I have noticed that the native scrobbler just fails to scrobble certain songs.

It will show up as scrobbling now on the last.fm website when playing the track but will never actually scrobble once the song is done.

This only happens with certain songs on some albums, there's no special characters or emojis on any of the songs and the rest of the songs on the album will scrobble normally.

I attempted to scrobble the songs multiple times to see if it was a momentary issue or just an issue with last.fm's servers but every single time every song would scrobble fine except those specific ones.

This is an issue as the built in scrobbler is overall better than the old desktop scrobbler since the old desktop scrobbler would fail to scrobble any song that had any special characters in it like emojis while the built it does it just fine.

If needed I can provide the files I am playing or the whole album to see if this error is repeatable for others.

Thank you for the hard work with WACUP so far been using it for years at this point.

Pages: [1]