Messages

1

Preview Build Discussion / Re: [CHANGES MADE] High CPU usage when streaming to an Icecast server using dsp_wc

« on: Today at 01:24:01 PM »

As a follow-up to this it's been found the plug-in in build 25130 isn't correctly processing title updates in SCv1/Icecast mode due to the changes that were made to try to resolve the high cpu issue (some appear but it can build-up a list of pending title updates) which can still cause some cpu load issues. The complete fix needed to get titles working & keeping the cpu load down requires a new build (out later this month) instead of being able to be done via the post-release updates.

2

Preview Build Discussion / Re: Icons.....not changing?

« on: Yesterday at 02:39:47 PM »

If that or any other player better suits your needs then you should just use that. I'm not too bothered about implementing file association management into wacup as that's not something I need & I'm fine if that irks others which is why it's noted there's no file association options during install, etc.

I've not removed it & since wacup hasn't relied on the winamp core to load / run for a long time now it's not comparable to what what winamp had offered with its icon packs which was only happening from me hacking things in with my jtfe plug-in against what the winamp core & it's file association prefs page. There's nothing to stop you / others manually editing the OS file association details in the registry to achieve the same effect of per-file icons.

It's however something that I'm aware I've got to consider having when I finally do get around to implementing things but I've no near term goals to do that & there's things about the old style of icon packs that I never liked which I'd likely do differently anyway. I will move this into the wishlist sub-forum in the next few days.

3

Preview Build Discussion / Re: in_url claims unknown URL schemes ahead of third-party input plugins

« on: Yesterday at 12:14:17 PM »

in_url wasn't meant to be taking anything that's not a [http|https]:// like url but an internal api change some time back meant it was taking anything that's :// without knowing it.

Due to the order in which the input plug-ins are loaded (there are no options to control this nor will changing the filenames help) & thus queried it means the wacup plug-ins are usually processed before any 3rd party plug-ins & in this case in_url was incorrectly claiming things preventing any other plug-ins yet to be queried as part of the "find the plug-in to use" loop. This is the inherent downside of winamp's isourfile(..) method being a first match gets it which is why I generally try to avoid using that method when it comes to wacup's implementation of the plug-in handling but for url like options it's basically the only way to do things.

I've now got things changed in in_url for the next build so it'll limit what it's trying to claim to just [http|https]://.

For aiding in debugging, prefs -> about|updates -> about tab has a box at the bottom which will show what the active input & output plug-in are to know what is trying to be used though the alt+3 dialog for url like options is also a way to figure it out.

4

Preview Build Discussion / Re: [BUG] ATF: can't $replace with empty string anymore

« on: Yesterday at 09:59:52 AM »

That's useful to know the $cut from the end of the string changes from the prior build that ironically introduced this $replace problem helps.

5

Preview Build Discussion / Re: [FIXED] Problems with Jump to File

« on: Yesterday at 09:58:48 AM »

I've added a workaround when using a modern skin for the next build but I'm not happy with the change as it shouldn't be needed & I'm not finding an obvious reason why the keyboard navigation isn't working correctly in that mode (this might be why I'd had the code in before which led to the initial set of issues in the thread) vs it behaving when running as a classic skin.

6

Preview Build Discussion / Re: [FIXED] Problems with Jump to File

« on: October 15, 2026, 11:47:23 PM »

It seems to be happening only when using a modern skin that's preventing the keyboard navigation from working even though it's meant to be flagging things in a manner to do it (e.g. tabbing between the controls isn't working though switching to a classic skin is then behaving). Will add it to the list of things I need to fix before the next build goes up.

7

Preview Build Discussion / Re: Icons.....not changing?

« on: October 15, 2026, 11:16:32 PM »

wacup currently has no means to use the old winamp icon packs so there's no means to change what's being used from within it.

8

Preview Build Discussion / Re: [FIXED] Problems with Jump to File

« on: October 15, 2026, 01:54:22 PM »

Attach the image please as I cannot see anything from imgur (am geoblocked since September 2025) also you need to confirm what version & build type of wacup you're using along with the OS being used.

9

Preview Build Discussion / Re: [BUG] ATF: can't $replace with empty string anymore

« on: October 15, 2026, 01:34:09 PM »

Changed more of the internal ATF handling to avoid working out the length of strings when it's already been determined for a small performance improvement especially when doing 1000's of ATF calls

That's the reason for it not behaving correctly with build 25130 which was not intentional & will require a new build to resolve it.

I might also see about adding an extra parameter or a case insensitive version of $replace as it caught me out initially that the string I was testing with didn't match exactly.

[edit]
Have added an optional fourth parameter to what'll be part of the next build which is set to 1 (e.g. $replace(%title%,String,,1)) will treat string & String as the same. If not set or not what's expected then it'll keep doing it all as case-sensitive comparisons.

10

Wishlist / Feature Requests / Re: [CHANGES MADE] Lyrics Plugin Text Alignment

« on: October 09, 2026, 08:45:30 AM »

You're welcome.

11

Preview Build Discussion / Re: [Bug] Drone_v11 - Playlist Selection UI Broken In Build #25130 (Worked Before)

« on: October 07, 2026, 11:25:07 AM »

I think I've got it fixed for the next build. There's something odd about the drone skin vs lyricsplugin which is affecting the normal timing of things happening (based on what the other skins are doing whilst debugging this) that causes the bitmap used as part of the drawing of the main playlist window to not be available during the initial drawing.

That causes it to end up in a weird state where the drawing mostly works but the colours basically doesn't as it falls back to working with a default monochrome bitmap that the OS creates for the drawing surface. So that's why no selection is showing up or even the expected colours from what I was seeing & it comes down to a 1 line fix to filter out the painting when in that invalid state which at least for what I'm seeing under testing is now getting it to load correctly with the plug-in.

12

Preview Build Discussion / Re: [Bug] Drone_v11 - Playlist Selection UI Broken In Build #25130 (Worked Before)

« on: October 07, 2026, 08:25:32 AM »

The portable install mode won't load 3rd party plug-ins by default as a lot of them aren't going to be truly portable (lyricsplugin is one of those by using the registry from what I remember). If you go to Preferences -> Advanced -> Portable Mode -> there's an option to allow 3rd party plug-ins to be loaded in portable mode for those happy with things no longer being guaranteed to be portable.

lyricsplugin is also throwing an expired site certificate everytime it loads which is annoying (not the first time the plug-in &/or it's site have gone weird in the time I've been doing wacup & was why I needed to make my own even if it's not feature comparable to what want as it avoids the whole embedded IE browser webcontrol mess that lyricsplugin relies upon to still work for now).

I can replicate it breaking things when the drone skin is the one set to be loaded on start-up & lyricsplugin is enabled. If I start with a different skin or change from drone to any other skin I've got to test with & then back to it in the same instance it then behaves. Though why if it's the one that's been loaded & trying to reload it without changing to another skin doesn't update things is also weird which I'll try to look into hopefully later today.

13

Wishlist / Feature Requests / Re: [CHANGES MADE] Lyrics Plugin Text Alignment

« on: October 07, 2026, 08:08:39 AM »

I've attached what the prefs page should look like with a red box around the button that'll become enabled if it's seeing that there are applicable post-release updates for the installed build.

14

Preview Build Discussion / Re: [Bug] Drone_v11 - Playlist Selection UI Broken In Build #25130 (Worked Before)

« on: October 06, 2026, 05:39:10 PM »

It's the same as I've already got which I'd expected so wtf is going on that is causing it to break for you when I cannot replicate it on anything I've tried nor can I see anything with the code changes that I'd made between the builds that would relate to skinning as it's a standard part of the code used for all of the skin types trying to be used. Does making a test portable install & using the skin in it also break?

15

Wishlist / Feature Requests / Re: Lyrics Plugin Text Alignment

« on: October 06, 2026, 01:55:46 PM »

Assuming build 25130 is being used if you go to preferences -> about | updates -> about tab -> follow the instructions to get the post-release updates & then there should be a new text alignment block on the lyrics window right-click menu to change how it's rendered.