Messages

1

Preview Build Discussion / Re: bugs in version 1.99.45.23528

« on: Yesterday at 06:43:38 PM »

#1, I can't replicate it not updating so is that with the lyrics plug-in wacup provides (if so what skin is being used) or is it one of the 3rd party plug-ins? If it's the one provided with wacup have you changed it to show what's selected in the playlist as that's the only way I can get it to seem like it's not behaving vs forgetting something was selected at the time.

As for the quality of the lyrics there's little I can do with my solution when there's barely any free options available to try to obtain such information online (assuming that it's also not incorrect within the file(s) being accessed as using the local copy is prioritised where possible).

#2, I can replicate but only on the first action after loading that playlist & I still need to look into what's going on to cause it.

[edit] The sorting issue is due to a workaround in place to deal with interacting with the classic skin playlist editor buttons which puts it into a wrong state when the double-click is attempted whereby it doesn't try to determine the item that's being interacted with. It's also possible to trigger playback of the current item when double-clicking in some of the dead space within the playlist window so both of those issues should now be fixed for what'll become the next preview build.

2

Wishlist / Feature Requests / Re: Remember file name and type

« on: Yesterday at 03:22:43 PM »

I thought I'd added it to that but seems not with the filename so that'll need to be added in a later build.

The filter selection is coded to be remembered but it looks like when I changed to use m3u8 as the default instead of m3u years back now I messed up the checking to avoid it saving out non-default values which broke it for remembering m3u as the filter selection (m3u8 & pls are being remembered correctly from my re-testing).

3

General Discussion / Re: Editing a playlist entry

« on: Yesterday at 09:30:03 AM »

Thank you for confirming. I've had a quick look & it seems that a workaround to resolve a WINE related issue when the size of the list contents changes is being incorrectly applied which is causing it to scroll back to the first item of the list. Will look to get that fixed for the next build as it's able to affect any of the list instances be it library playlists or the local library views for example.

4

General Discussion / Re: Editing a playlist entry

« on: January 20, 2026, 10:28:21 PM »

To confirm this is happening in the child playlist within playlist root view? Also which specific action are you using within the playlist view?

5

General Discussion / Re: How can I view the recently played/history ?

« on: January 20, 2026, 10:24:36 PM »

You or the skin has managed to collapse the media library navigation tree so it's not visible leaving the last shown media library view that was selected.

Move the mouse over the vertical bar to the left of the name column & that should change to a left-right mouse cursor along with the line changing colour which can be dragged to the right by clicking & moving the mouse.

Then you can select the history node which should show what's been played subject to how that mode is configured & if what's played meets those settings.

6

Preview Build Discussion / Re: Small Mouse Cursor in v1_99_45_23528_x64

« on: January 20, 2026, 07:25:09 PM »

Oh that. I vaguely remember some reports about it but never really got to the bottom of it other than it seemingly being related to how winamp registered itself for file associations (not something wacup does in its preview state) which could for some installs then conflict with the OLE handling that is needed on my side to allow for some of the external drag+drop handling to work correctly. It however shouldn't have affected things when just starting the wacup process & is a shame I didn't know about it beforehand as it might've been possible to capture more of the wacup instance within that state vs what I had in place when it was last reported but if wacup is loading ok now then I'm not going to worry as much about it.


With the cursor handling, I've had a quick play around after fixing the non-skinned issue I saw as mentioned in the prior reply & if I change how the cursors are loaded it's possible to have the OS scale it up based on the screen dpi settings which might be enough for what's wanted.

The only obvious downside is that the scaling applied can be a bit crude making the cursors look a bit blocky depending on the size it's starting out with to begin with but that might not be an issue depending on the screen & how good the user's eyes are.

I'm still debating if I turn this change into something that can be controlled via the preferences (e.g. turning the use skinned cursors checkbox into a drop-down so it can be off, as-is, OS scaled) but that might not be needed so will need to see what it's like in use for others. Alternatively I might have to look at trying to scale the cursor image elements myself using a different solution & then passing that onto the OS to use but that also might not be needed.

7

Preview Build Discussion / Re: Small Mouse Cursor in v1_99_45_23528_x64

« on: January 20, 2026, 02:59:00 PM »

I've not looked into what can be done to try to scale the cursors that the skins are providing with most being in the 32x32px range iirc. Turning off the option to use the skin cursors (prefs -> skins -> classic skins) would make it use the OS default cursor (though it looks like the skinned listview header controls aren't following that setting) or it'd involve manually making a skin folder & putting up-scaled cursor ico files into it if still wanting to have it use the default skinned cursors otherwise there's nothing else I can suggest at the moment.

What I am a bit bemused by is the comment about having a winamp install also messing up with wacup present. There shouldn't be any interactions going on between them especially with the x64 build of wacup unless using the same program folder install name had been used causing it to point to the same settings folder (which the wacup installer avoids doing by default nowadays & wasn't something the x64 install did anyway to avoid problems with mixing unrelated x64 & x86 exe / dlls within the same folder).

8

General Discussion / Re: 3DAmp

« on: January 18, 2026, 02:25:10 PM »

It tries to provide as much of winamp's documented api where it makes sense &/or is needed for plug-ins & external tools to work. There's also things like the default taskbar text referring to winamp even though it isn't using it to run nowadays for helping maintain compatibility for things scraping that for what's playing.

The x64 build isn't as compatible with it just offering up what it needs without a lot of the plug-in compatibility baggage but the basics that most external tools use is still responded to.

I don't have any current plans to provide the wacup specific api as it's mainly aimed at my internal needs nor is it stable vs the winamp compatibility being there for those that need it (sans plug-in support with x64 which I might not support 3rd parties as it just keeps things a lot cleaner unlike the hacks, etc the x86 build has to implement).

9

Wishlist / Feature Requests / Re: Remember file name and type

« on: January 18, 2026, 02:16:38 PM »

That should already be happening. From what specific UI action is it not doing that?

10

Skins / Re: Big Bento Modern skin crashing

« on: January 17, 2026, 10:14:45 AM »

What options are greyed out? As the image above is the same as the one from the first post.

[edit]
I've been trying to replicate this & the nearest I can get to what might be happening involves disabling the initialisation in that script file & then some of the other methods in the script when triggered will then fail. I can't be certain if that's what your failures to load are or not but it's the only thing I can vaguely find but still suspect it's a bad modern skin settings file.

11

Skins / Re: Big Bento Modern skin crashing

« on: January 16, 2026, 07:22:49 PM »

Can you try running the crash report collector option from WACUP's start-menu folder or run wacup.exe /procdump manually from a command-prompt within the WACUP program folder so it can try to collect a crash report as I'm not seeing anything around the time of these posts that relates to a modern skin failure. Though I've feeling it won't collect anything & this is more likely just the modern skin engine plug-in screwing up & not continuing if no windows, etc appear after it occurs.

If it is able to collect something in that mode (there'll have been a command-line window appear which goes away when a crash happens that it can deal with) then you'll need to try to run it normally again & hopefully that'll then auto-submit to the site server what's been collected before it then tries to run & likely fail again as you're seeing.

After that then you'll need to try doing the wacup.exe /RESETMODERNSKINPOS command-line option.

12

Skins / Re: Big Bento Modern skin crashing

« on: January 16, 2026, 06:10:05 PM »

What WACUP version are you using (am not seeing any obvious modern related loading crash reports again the current 1.99.45.23528 build)? Clicking on the guru error shown should usually allow wacup to continue running without crashing.

Also have you attempted to use the wacup.exe /RESETMODERNSKINPOS command-line option to reset the modern skin settings configuration file back to a default state to see if that might help (as the re-used gen_ff plug-in from the 5.666 installer is buggy & sometimes it'll just screw up its settings or will for some skins trigger weird scripting issues on loading).

13

Preview Build Discussion / Re: Fixed Columns in Internet Radio section

« on: January 15, 2026, 04:13:04 PM »

It's not ok as you're telling me it's behaving in a manner that is at complete odds with how it's been coded & with what I'm seeing in my testing. Please send me a pm with a copy of your winamp.ini & gen_ml.ini files after having tried to set the columns & closing wacup.

14

Preview Build Discussion / Re: Fixed Columns in Internet Radio section

« on: January 15, 2026, 03:30:12 PM »

I cannot replicate it resizing the columns within the internet radio back to showing if I've sized them to effectively not appear & had checked that it would save them as zero width before I'd made my reply. If something like the Ctrl+Shift+Numpad Plus action is done to trigger a resize based on the column contents then it's going to show the columns again as that's expected per how the listview is done in other parts of Windows.

If it's not saving their width when you're closing wacup or even just switching to another view & back again (does that behave for you or does it also break?) then my assumption would be something is either preventing the config from being updated or it's not being read back in on loading or something is triggering the column resize action (it's not something I've coded it to do as that would annoy me & is why all of the views be it this or local library, bookmarks, etc will attempt to maintain the last set width) which again I cannot currently replicate with 23528 in either of different x86 & x64 installs.

15

Preview Build Discussion / Re: Channel mixer ? Stereo Upmix ?

« on: January 15, 2026, 03:20:52 PM »

It's mainly for adjusting the channels being output so stereo to 5.1 for stereo input or a different way to do stereo to mono if the input plug-in being used doesn't natively support that playback mode. That's all subject to having the needed output device being compatible & the OS vs the output plug-in that's selected via it also supporting it. For some it's not needed if everything is already configured on the hardware / audio driver / OS side but for others it's needed to get what's expected.

If it's actively in use then the input & output levels on that prefs page should be indicating what's being received along with what's being output but that requires the Not So Neo output plug-in to be set as the active output plug-in via the dropdown at the top of the prefs -> plug-ins -> output page. I probably should do something to better indicate that it's not the active output plug-in when viewing that prefs page to avoid that potential confusion otherwise it may or may not be required in use.