Messages

1

Preview Build Discussion / Re: bugs in version 1.99.45.23528

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

If the portable install works & the other when updated to use the same version doesn't then it's most likely an odd config problem since the skin shouldn't matter especially if set to a classic one. Other than bundling up the broken installs main set of config files so I can have a look at them I'd rename the winamp.ini to something else & then run it again to see what that does (it'll reset most settings & window positions but is the simplest way to see if it's likely the main config file at fault).

2

Preview Build Discussion / Re: WACUP x86 #24626 update anomaly

« on: Yesterday at 06:29:39 PM »

Really this should have been it's own thread as what was reported was to do with a different output plug-in.

There aren't any post release updates related to the notsodirect output plug-in with the build shown. I could also do with knowing the build type & what skin is being used. As under classic skins it may give a reason for the failure in the main window song ticker text. I'd also recheck what the output plug-in prefs page is showing as selected to be used from the dropdown & that there's no errors mentioned. Also if you're trying to use a specific output device or what's set as the OS default device.

3

Wishlist / Feature Requests / Re: [CHANGES MADE] Play Tracking Preference Not Saving

« on: August 10, 2026, 08:23:16 AM »

Thank for confirming the sort of workaround works & should save you having to reset it every time.

4

Wishlist / Feature Requests / Re: Play Tracking Preference Not Saving

« on: August 09, 2026, 10:02:10 AM »

The preview box showing text is wrong so that's now fixed for the next build. Otherwise the action is working correctly against what I'd tried to do vs the original behaviour so it'll leave what's in the file as was last set when playback stops instead of clearing it (maybe that needs to be a dedicated mode possibly via another options from the dropdown assuming it actually makes sense to implement that).

A space character not being maintained is due to the handling stripping off whitespace characters when the formatting strings are processed. The simplest way to ensure you will have a space / effectively empty output no matter is to use $char(32) as the formatting string. You could also use $crlf() which just outputs a linebreak & should still do the same as the $char mode.

Also I've only checked this against the current (as of this reply) 1.99.53.24784 build.

5

Resolved Issues / Re: Jump to file with space in filename fails

« on: August 04, 2026, 04:36:55 PM »

I've uploaded a post-release update for the jtfe plug-in (can be accessed via preferences -> about|updates -> about tab or the OS toast that might appear) which should now do like with 24626 & earlier with spaces in the search whilst keeping the internal processing optimisation that inadvertently broke things.

6

Resolved Issues / Re: [FIXED] v1.99.53.24778 installation crash

« on: August 04, 2026, 02:01:23 PM »

Thanks for the confirmation that it's back to working ok again for you (I assume it'll help for the others though I've not had confirmation from them yet). Was an oversight as part of some changes made to reduce the code size of a few of the dlls whilst also reducing the code complexity with loading things but it didn't behave correctly during some new / incomplete updates. Main thing is that it's now been resolved.

7

Resolved Issues / Re: Jump to file with space in filename fails

« on: August 03, 2026, 09:45:56 PM »

I made an optimisation that isn't behaving correctly which I hadn't noticed as I'd only been doing single word searches & none of the beta testers had mentioned it being an issue vs the other changes made to the jtfe plug-in to resolve other ui hang / crash related problems. Will try to have a look into it tomorrow or Wednesday & put up a post-release update to fix it once I'm in a position to debug it (is too late now).

8

Resolved Issues / Re: v1.99.53.24778 installation crasg

« on: August 03, 2026, 08:27:20 PM »

1.99.53.24784 is now up which should resolve the problem with the installer crashing.

9

Resolved Issues / Re: v1.99.53.24778 installation crasg

« on: August 03, 2026, 11:49:15 AM »

I've tentatively already figured out the cause before I had to go out this morning but I need to do a bit more testing along the with checking out a few other things raised before I put up what should be a fixed installer later today.

10

Resolved Issues / Re: v1.99.53.24778 installation crasg

« on: August 03, 2026, 08:26:26 AM »

It's not something I've seen so I'll have to see if I can replicate the installer crashing later today as you're now the second person that's let me know something isn't right.

11

General Discussion / Re: Enhancer DSP

« on: August 01, 2026, 07:16:31 AM »

I really hope you've not installed the old version of the wrapper when it's been included as part of wacup for some time.

There's no means to get it to scale due to how the original enhancer plug-in works.

12

Wishlist / Feature Requests / Re: Return the Playlist to last first Instance

« on: July 31, 2026, 04:54:19 PM »

How exactly are you opening a second instance? As I don't recognise using shift to do anything like that.

The default wacup behaviour is to not run multiple instances (unless you've disabled the option in the preferences) with the Ctrl+Alt+N action from an existing wacup instance being the way to trigger a new instance. That Ctrl+Alt+N action will prompt you to make a copy of the settings folder from the original instance being used to avoid the problems that can occur with multiple instances vs using a single settings folder. Alternatively you can use the command-line options (wacup.exe /?) to make different instances use specific config folders.

I don't see there being anything for me to do when there's already things in place to avoid the data corruption that multiple instances can cause using the formally provided means to achieve it.

13

General Discussion / Re: No Sound

« on: July 30, 2026, 02:51:26 PM »

If you're not going to answer everything that I'm asking then I cannot help you.

14

General Discussion / Re: No Sound

« on: July 30, 2026, 11:13:49 AM »

Both will be enabled as that means they're able to be used but what's selected in the dropdown at the top or which shows '(active)' before the plug-in's description is the one that'll be trying to be used. I'm going to have to assume that what I suggested didn't make any difference, correct? If so try using the notsoyasapi plug-in if notsodirect doesn't work for you. Though I could really do with clarification of what the player is actually showing or doing when you're trying to play things (assuming that it's still even trying to play files in the correct location & that they've not been moved or aren't from something like a network share that's not connected or the permissions to access it haven't been changed, etc).

15

General Discussion / Re: Bookmarks breaks with very long station metatext

« on: July 30, 2026, 11:09:52 AM »

Streams really shouldn't be providing titles with line-breaks in them but that's something I can look to add a check for when a bookmark is added to strip them out from the title string. With the example stream I'm currently seeing that it's 'title' string is a load of effective stream parameters (from their side) & that it can be quite long which gets close to a compatibility length limit which I'll have to look at modifying.

[edit]
I've now fixed the handling to strip line-breaks along with fixing the title string truncation issue for that stream which shouldn't have been happening so wasn't quite as I initially thought was going on.