Latest WACUP public preview for x86 & x64 is build #23960 (March 1st 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #23960 (March 1st 2026) (x86 & x64 changelogs)

Author Topic: Audio spectrum display issue  (Read 123 times)

mvsqueens

  • Newbie
  • *
  • Posts: 1
    • View Profile
Audio spectrum display issue
« on: March 13, 2026, 10:25:19 PM »
The display in the top window in WACUP usually displays status, time elasped, and the audio spectrum.  The audio spectrum changes to the moving icon from left to right and back with a trail/tail that I associated with "Loading Audio File ...".  This usually happens while I'm not looking, but about two hours into streaming.  While playing a live audio stream (my primary use of WACUP), I can get the audio spectrum display back by restarting the stream (CTRL-X).  I can't find a menu option to change a setting that would ensure the audio spectrum displays, especially after a "Loading ..." notification. 

My WACUP:
  • Version:  1.99.47.23960
  • Date:      Mar 1, 2026
  • Type:      32-bit native
  • Skin:       Default Classic
Forgot to capture a picture of my problem;  restarted stream before writing this.

The audio spectrum display problem may have been present in the build before my current one, but it most certainly is an issue in this one.

Many thanks.

Mark Victor

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 5645
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: Audio spectrum display issue
« Reply #1 on: March 14, 2026, 10:56:26 AM »
If it's in the buffering state then it means that the vis data vs the playing state has lost sync & it can't match what's playing against the samples that it's expecting to try to render. There is no configuration option available to adjust as it shouldn't be messing up & as you've mentioned streams, I'd need examples of the stream(s) having issues to determine if it's a format specific issue or streaming in general though I've not seen it happen from some recent re-testing but that might be I'm not having issues with getting enough stream data or things just keeping in sync so who knows. Also the output plug-in being used might affect things with notsoyasapi being known to cause a de-sync even with local files.