Latest WACUP public preview for x86 & x64 is build #24626 (July 10th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24626 (July 10th 2026) (x86 & x64 changelogs)

Author Topic: WACUP x86 #24626 update anomaly  (Read 914 times)

Phuntso

  • Sr. Member
  • ****
  • Posts: 25
    • View Profile
WACUP x86 #24626 update anomaly
« on: July 11, 2026, 07:18:57 PM »
I downloaded the recent update and now nothing plays. No online radio. In case of a music playlist, it just fast skips over them one by one. And finally when I tried to play an OGG file the WACUP terminated without an error. And now after the OGG attempt I cannot launch WACUP at all: it terminates after the window appears.

EDIT:
I tried Safe Mode - did nothing.
I tried Crash Collector - it showed the terminal, WACUP continued to malfunction.
Then I ran WACUP again, it finally threw a crash report window and after which WACUP started running normally again.
Now that's odd.
« Last Edit: July 11, 2026, 07:27:32 PM by Phuntso »

Eris Lund

  • The Skin Guy, Official Modern Skin tech support
  • Beta Tester
  • Hero Member
  • *****
  • Posts: 328
    • View Profile
    • Eris Lund's Github
Re: WACUP x86 #24626 update anomaly
« Reply #1 on: July 11, 2026, 08:59:18 PM »
Check the post-release updates in the Preferences -> About | Updates, they might fix the issue.
Maker of Plugins, I suppose.
gen_native:
https://github.com/0x5066/gen_native
vis_sdl2:
https://github.com/0x5066/WinampVis
(I know, creative names)

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 5807
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: WACUP x86 #24626 update anomaly
« Reply #2 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.