1
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.
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.
2
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.
3
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.
4
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.
5
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.
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.
6
Preview Build Discussion / Re: Missing devices
« on: February 25, 2026, 04:40:16 PM »
Using the checkbox in the list.
7
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.
8
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.
9
Preview Build Discussion / Re: bugs in version 1.99.45.23528
« on: February 17, 2026, 01:53:36 PM »
It's also a comparatively old version of WINE at this point (with 11 having just come out) so it could also be related to that. The always on top under Windows is determined by the main window & then any child windows associated to it will follow that but turning it off is down to the OS window manager to then re-adjust things as I don't do anything specific with the child windows. Under WINE the window handling doesn't always seem to match what Windows is doing (e.g. tooltips & their z-order / focus issues) so as I can't see it not behaving as I'd expected under Windows I'm going to have to agree that this is most likely a WINE / DE specific issue.
10
General Discussion / Re: Question here.
« on: February 17, 2026, 01:48:12 PM »
What WACUP version & build type? Also where specifically in the UI are you triggering a playlist rename to occur? As seeing such characters would imply a bad string conversion happening (with the OS trying to represent string data with a wrong assumption) but I'm not seeing such a problem from a quick re-test with the current build when renaming in the places I can think off (i.e. the media library navigation tree node & within the library playlists root view).
11
General Discussion / Re: Repeated Artist Names
« on: February 13, 2026, 08:15:12 AM »
I need the library.idx file as well.
12
Preview Build Discussion / Re: Problem with ATF (Advanced Title Formatting)
« on: February 11, 2026, 08:41:01 PM »
It's not an issue I've seen & there's nothing obvious I can see which would be causing the formatting string to the altered especially not for it to be clipped unless there's some 3rd party plug-in or quirk in the timing of the atf processing that's somehow modifying it (not that it should vs the working copy it uses to avoid such issues). What build were you using prior to the January one which was behaving?
13
Wishlist / Feature Requests / Re: Opening a new instance.
« on: February 11, 2026, 07:27:32 PM »
You'd have to go back to a build that doesn't have the problem (I don't know what that'd be as fixing the issue instead of trawling back through old code commits was a better use of my limited time at the weekend). The spawning a new process shortcut from the current instance or using the /new command-line action when also relying on the use of another provided settings folder copy for it to use is what's triggering the problem to occur so for that I don't have any nice workaround unless you make another unrelated install & then mess around with trying to copy the existing second instance's settings folder into that or just doing it all from scratch with 2 different installs.
14
General Discussion / Re: How to install the Last.fm scrobbler plug-in?
« on: February 11, 2026, 07:09:20 PM »
The nature of the share doesn't matter as it just has to be via an un-mapped location & the file metadata has to have also been cached within the local library db which is why I'd asked in both of the replies I've made about this problem for it to be checked.
15
General Discussion / Re: How to install the Last.fm scrobbler plug-in?
« on: February 11, 2026, 05:19:07 PM »
That looks like an un-mapped network share from the path shown so I've got to assume you're having the issue I described. Looking for that file in the local library part of the media library window & there not being a length shown would confirm if that's the cause. It requires a new build to get the needed fix (not yet ready as a new preview build) & a refresh of the metadata in the local library after the newer build has been installed.