Messages

16

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.

17

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.

18

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.

19

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

20

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.

21

General Discussion / Re: Frequent crashes during song change using NotSoDirect plugin

« on: July 29, 2026, 05:08:31 PM »

I've had a small amount of time to look into this & I've intermittently managed to replicate it but I can't yet tell why the dmp vs what I've also managed to see is happening. I'll try out a few things for the next release but currently I don't know if it'll receive a fix for this or not.

22

General Discussion / Re: No Sound

« on: July 29, 2026, 05:06:42 PM »

Is this with the x86 or x64 build of wacup ? Also just to be certain this is with 1.99.52.24626 with the post-release updates applied (so nothing is still showing as pending when going to preferences -> about|updates -> about tab) ?

I'd also suggest going to preferences -> plug-ins -> output & double-checking what plug-in is showing as the active one in the dropdown at the top of that page. it should be the notsodirect plug-in for most installs though no sound was an issue with the initial 24626 build without the post-release updates if notsoyasapi had been set as the active output plug-in.

If notsodirect is selected, go to preferences -> plug-ins -> output -> directsound & make sure that its set to an appropriate output device in the top dropdown (primary should be it but you can alternatively tell it what output device to specifically try to use).

If notsoyasapi is selected, like with the notsodirect option to check that it's set to an appropriate output device you can go to preferences -> plug-ins -> output -> wasapi to do the same from it's output device dropdown at the top of that preference page.

23

Preview Build Discussion / Re: Qwerky behavior with playlist+album art resizing

« on: July 27, 2026, 12:40:25 PM »

I wasn't having a go about reporting it as I'd rather know than not since it's just me trying to make wacup. I was just trying to say without rambling that late in the night for me that because it's coming from a plug-in that I don't have the source code for when it does weird things more often than not there's little I can actually do to try to workaround it's problems. As what you've reported has to be down to the plug-in deeming that the ui element had the mouse focus but didn't see it being taken by something else causing it to then react in the manner it did when going back over it which is something I've seen in other win32 coding but so far I'm still not seeing it happen with the steps given.

24

Preview Build Discussion / Re: Qwerky behavior with playlist+album art resizing

« on: July 26, 2026, 10:34:00 PM »

I can't replicate it from trying to follow the steps mentioned & you've said playlist view when local library view is what I assume you meant based on what the image shows. If it is consistently happening for you then it's not something I can easily fix (especially not if I can't replicate it so far) as that part of the ui is handled by the re-used gen_ff (modern skin engine) plug-in dll from the winamp 5.666 installer.

25

Wishlist / Feature Requests / Re: DSEE HX or such and Gracenote for winamp?

« on: July 24, 2026, 05:23:50 PM »

no

26

Wishlist / Feature Requests / Re: Add a custom location to the "Send to"

« on: July 24, 2026, 12:27:31 AM »

That can already be done if the gen_yar plug-in that ships with wacup has been installed & has been enabled. That way it can be used in either the x86 or x64 builds unlike such plug-ins which are limited to x86 only. gen_yar isn't enabled by default but can be by going to preferences -> plug-ins -> general -> find gen_yar in the list, check the item to enable it & if needed restart wacup to get it fully loaded. Then there'll be a copy files option in the send-to menu along with one towards the bottom of the main right-click menu.

27

General Discussion / Re: Preferences search box

« on: July 22, 2026, 08:04:27 PM »

https://getwacup.com/community/index.php?topic=602.0 & https://getwacup.com/community/index.php?topic=2058.0 are the prior threads I can quickly find on here about this same request. It's also been asked on discord a number of times & I just don't know of a way to do it that doesn't involve a load of extra code & data overhead & which also isn't a complete pain to try to keep updated especially if it's got to somehow deal with 3rd party plug-ins when I've got no control or means to know what a prefs page might even show since some are dynamically created or the prefs page isn't created unless it's actually needing to be shown (so pre-parsing everything isn't an option with how any of it currently works).

I do try to group things where it makes sense based on the overall association of settings but that often doesn't seem to match up to what others are expecting things to be named which just exacerbates the problem. I also agree that there's too many options & as much as I want to I also don't see how I can cull some (or as many as possible) without it causing complaints so I'm somewhat screwed however I view it when it comes to how to do such a request. I've also asked for suggestions on how it could be implemented without it sucking & nothing ever comes from those requests so I've not done anything towards it.

28

Resolved Issues / Re: bugs in version 1.99.45.23528

« on: July 17, 2026, 08:18:32 AM »

That's not how it's working for any of my test setups so what is it about yours that is consistently causing the default behaviour to break...

Make a portable test install via the installer option to do that which won't touch the existing install & see if that also is broken for you or not.

29

General Discussion / Re: WMA breaks WACUP 1.99.52.24626 (x64)

« on: July 16, 2026, 06:00:26 PM »

The problem is within the in_what (directshow decoder) plug-in but is possibly tied to a change in the core so it'll need a new build instead of just a post-release update from what I can see at the moment. It keeps crashing for you on loading with the file(s) in the main playlist as it's trying to generate a waveform seeker preview when started which is then hitting the problem with how the internal player is being destroyed. It's not necessarily a new issue as I saw some of this when I was making the plug-in but the x64 build is more prone to it afaict.

30

General Discussion / Re: WMA breaks WACUP 1.99.52.24626 (x64)

« on: July 15, 2026, 07:02:26 PM »

It's not something I've tried in an age so it regressing isn't too surprising with some of the other changes that have been made to avoid other crashes affecting the recent builds. Though I've just re-checked a few example files & those played ok in the build.

You'll need to run it via the crash report collector mode (it'll be a shortcut in the start menu or by manually running wacup.exe /procdump or by going to preferences -> advanced -> error reporting & following the steps at the bottom of the prefs page) to try to generate a process dmp file when trying to replicate the issue in that mode (the event viewer log doesn't give me anything I can actually work with to debug the issue).

Once it's crashed, you'll then need to run wacup so its crash reporter can collect & submit the files - reply back to say it's been done so I can then hopefully match up the crash report from that time (I'll check back on this thread tomorrow as my time's up for today). I also don't see anything obvious from the summary log I get of the few x64 crash reports I've not looked at from today which leaves me to assume wacup's crash reporter isn't able to be triggered by the issue which prevents it from auto-submitting anything to the server (unless internet access for the program is being blocked). It might also be helpful to pm me a copy of a small file that's failing for you so I can also check that out in case it's something to do with the metadata handling for it.