Messages

1

Preview Build Discussion / Re: Audio spectrum display issue

« 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.

2

General Discussion / Re: Double clicking .wav's rapidly enqueue's the wav instead of playing immediately

« on: March 14, 2026, 10:51:01 AM »

I can't access anything from imgur as I'm geo-blocked by them since last year.

As for what's shown in the video, wacup is a different program to winamp so there are differences in behaviour & currently what you want it's command-line handling will not do as it's batching up requests coming in from the multiple spawned instances which was done as it helped with others double-clicking on a large selection where that otherwise would do more like you're wanting but wasn't what they wanted as it then lost files being added.

At this time wacup can't do what you need without either adding in another option to change the behaviour or for me to find a different way to achieve what is the intention of the handling whilst allowing quick additions to work. As for the /clear aspect, it does work but it's covered as part of the batch handling so it cannot do what you're currently wanting & maybe just having that not be handled by it might be the quicker way to get closer to what you're wanting but I won't know until I allocate time to look into it.

3

Preview Build Discussion / Re: [BUG] Waveform Preview No Rendering in new build

« on: March 13, 2026, 02:06:53 PM »

That's good to know that you manged to get things working. Am also wondering if some of the network path handling changes made in the builds from this year could've helped where it was incorrectly failing on trying to access such paths where the status wasn't certain which caused it to generically fail any access attempt when it should've made an attempt (as it now does). That path handling also got an option to allow for it to be disabled via the second options page of the advanced prefs page.

4

Preview Build Discussion / Re: Problem with ATF (Advanced Title Formatting)

« on: March 13, 2026, 01:23:46 PM »

Based on the other reports I've now had about this, the number of playlist items doesn't appear to be the problem & the only thing I can guess since I've yet to see it happen with any of my test installs is that there's a concurrency issue with how the atf based title generation is happening & that's then causing something to go wrong during the processing. I'll try something out for the next build.

5

Wishlist / Feature Requests / Re: Notifications not showing

« on: March 11, 2026, 07:06:27 PM »

That's because the atf value is %playlist_length% (paired with %playlist_position% from the default string on the appearance prefs page). As for that help page, it's incomplete from being a hacked up copy of what winamp used as means to try to work out what I needed to implement & I just don't have it in me at the moment to go through what's not on there vs my changes. The old winamp forums (assuming those are still running) had information on how to get up & running for wasabi / winamp3 skin scripting or any of the skinners still seeing things on here who might have more time to help than I do.

6

General Discussion / Re: Solved an issue with duplicates in playlists

« on: March 11, 2026, 01:32:10 PM »

If you're telling it to just parse a folder from an entry in a playlist file then wacup is going to do that for _anything_ that it supports. If the playlist being loaded is also within the folder itself then it's going to be counted (it probably shouldn't per the other thread where you'd posted about this but it's how wacup is currently coded - what winamp does is unrelated as these are different programs) as part of the folder enumeration.

If the existing playlist file you were using was in a folder one level up from what's wanting to be enumerated then it shouldn't have been a problem as long as what's in that playlist file is done as an absolute file path (e.g. c:\my\music & _not_ music). As you've effectively created a batch script that is just doing what wacup is doing when given a path.

cd /d "C:\Program Files (x86)\WACUP"
start wacup.exe "O:\Annet\Hacking\Musikk.m3u8"

As for your batch script, the part above could probably just be start "C:\Program Files (x86)\WACUP\wacup.exe" "O:\Annet\Hacking\Musikk.m3u8" as changing the directory shouldn't be needed as long as the complete exe path works.

7

Wishlist / Feature Requests / Re: Notifications not showing

« on: March 11, 2026, 08:46:25 AM »

That's almost completely down to how the skin notifier has been coded & I don't have any plans to mess around with such things (you can always try to modify the skin's maki scripts or find someone who'll do it for you).

There is an option iirc on the appearance prefs page that can try to override the songticker text atf string but it can often not work well with modern skins as it's a big hack which'd be the simple way to try to have the track total show (otherwise it's another modify the skin situation).

8

Skins / Re: Big Bento Modern skin crashing

« on: March 02, 2026, 02:50:31 PM »

The 23960 build which went up yesterday has the potential fix for this issue.

9

Visualisations / Re: Trying to compare AVS versions: visbot archive seems messed up

« on: March 01, 2026, 08:42:28 PM »

I don't know as that'd involve having to look at source code that I don't like looking at nor do I remember how well AVS followed the settings location api that winamp 2.9x introduced (via the IPC_GET* SendMessage stuff). I think it does but there's no guarantee if you're using external solutions that they properly implement the support for it. If you're not using wacup for avs then you really need to be trying to ask those providing the host implementation that you're having issues with as me guessing isn't helpful for either of us.

10

Resolved Issues / Re: MMD3 script error on launch

« on: March 01, 2026, 08:33:22 PM »

Build 23960 has the change that afaict resolves this problem.

11

Resolved Issues / Re: MMD3 script error on launch

« on: March 01, 2026, 04:29:16 PM »

The problem is due to a set of changes I made which consolidated all of the zip extraction handling into a single implementation but there's a problem with how the information about the items that need to go into sub-folders vs when the new sub-folder to use is reported by the archive library which is causing some of the skins to fail to extract as it needs the sub-folder the exist before trying to save out the files but isn't getting notified at the expected time. Will get it fixed for the next build that I'm trying to get finished off asap.

12

Visualisations / Re: Trying to compare AVS versions: visbot archive seems messed up

« on: February 25, 2026, 07:46:04 PM »

2.81<letter> builds were the VC6 compiles which can & do have issues after Windows XP but was the last to seemingly render all of the presets in the expected manner.

2.82 was a re-compile using a newer compiler (VS2008 iirc) as part of trying to avoid DEP/NX related issues which was needed for Vista+ to work. It however breaks some presets & couldn't avoid the ape sub plug-ins that it uses from failing.

2.83 was only officially provided with winamp as the localised version of the plug-in & was rolled back to 2.82 since it broke a bunch of presets based on the crap I got at the time about it. That's why winamp ended up installing 2.81d or 2.82 depending on the OS.

chavs was an unrelated update by justin along with my other attempt at a 2.9 at the time he also released a version causing 2 to have the 2.9 moniker.

The versioning in the dlls themselves were often missing or broken depending on how / where / what has hacked at it to create it. So if that 2.83 is even valid is imho potentially questionable as it'd require musicbee stubbing out winamp 5.5+ localisation api.

There's also the attempt by grandchild to make a new contained version of AVS along with merging / re-creating the ape sub plug-ins. Though I've no idea what's going on with that nowadays as when I last looked it couldn't be built with the MSVC compiler & I just don't have the time / interest to screw around with visualisations as it doesn't interest me.

tl;dr: AVS is & has always been a mess & just use the version of the plug-in that works for you.

13

Preview Build Discussion / Re: Missing devices

« on: February 25, 2026, 04:40:16 PM »

Using the checkbox in the list.

14

Preview Build Discussion / Re: Missing devices

« on: February 23, 2026, 10:58:17 AM »

The ml_pmp/pmp_* plug-in from 5.666 is installed (if selected as part of the install process) but it's not enabled by default because it's either not stable or that most don't needed it. Preferences -> Plug-ins -> Media Library -> finding ml_pmp & checking it in the list will enable it (best to allow it to restart wacup) but if it crashes there's nothing I can do about it & it's been talked about before about having a replacement but tbqh it's not something I have as a priority.

15

General Discussion / Re: Question here.

« on: February 18, 2026, 10:31:33 PM »

I'll need to see a copy of the playlists.xml file from your wacup settings folder (preferences > advanced > diagnostics > settings locations tab will provide the folder path you need to search within). I still can't replicate this issue & am now wondering if the file requested might be the problem.