Recent Posts

1

Preview Build Discussion / Re: Skin defect since about 3 updates ago

« Last post by Phuntso on Yesterday at 10:28:47 AM »

I read your part about applying skin to a fresh build and you couldn't reproduce it, so I thought, what if a skin setting is not read correctly and needs to be written in a new way by the application. I toggled random skin Config options and relaunched WACUP - the playlist shows correctly again. Easy fix, haha.

And your last text block about the whole window frame going blank, yes, that's an issue too I've observed for a long time, just never bothered to report.

There's one more issue that appeared with a recent update, but I ain't reporting it yet, unless I see it happen one more time.

2

Preview Build Discussion / Re: Skin defect since about 3 updates ago

« Last post by dro on May 17, 2026, 06:49:34 PM »

This is the never ending trouble with trying to get the gen_ff plug-in running outside of a program it was never intended for & there's things that just aren't right with my compatibility layer which aren't going to be resolved without attempting to make my own plug-in (which'll instead bring a whole different range of problems as any new code base would have).

I've tried with the v1.0 & v1.1 copy of the skin that I could find & I've not been able to replicate the playlist editor display issue exactly as shown when using them as part of an install that hasn't previously seen these skins.

The tooltip window I can see where it's not painting the whole area when the 'alternate tooltips' skin specific option is enabled. Without looking into it further that's most likely something wrong with the region implementation or something else vs what the skin is trying to do which just doesn't work well with my compatibility layer. 5.666 doesn't seem to show an issue but then it's tooltips also don't appear to scale with the skin so it might be something else going on which until I can bring myself to throw an unknown amount of time at this there's nothing I can suggest other than turning off that skin specific option so the basic tooltip style is used.

One odd thing I am however noticing from this skin is the tooltip showing appears to trigger the whole window frame on some of the windows to randomly go blank but the inner contents aren't affected (unlike your reported playlist editor window in the screenshot). That makes me think it's more likely something to do with the region painting which I've still got some other skins where the handling isn't right & I've got to assume this is the case again not that I've touched the code in a while to avoid causing regressions.

3

Preview Build Discussion / Skin defect since about 3 updates ago

« Last post by Phuntso on May 15, 2026, 04:35:41 PM »

Currently on 1.99.50.24496 (x86).  I'm using the Drone v1.1 skin. See the attached image. The skin has lost ability to show playlist items with transparent background and the ability to highlight the currently selected item as it still could before some few updates ago. Now it just shows items in a black box. I also noticed that the button tooltips render incorrectly: half is correct, second half is default system tooltip without the skin color theme.

4

Preview Build Discussion / Re: Build #24496 (May 8th 2026) - Library issue

« Last post by wd9895 on May 15, 2026, 03:08:07 PM »

Thank you.
Option found. Never knew this option before, thanks.

5

Preview Build Discussion / Re: Build #24496 (May 8th 2026) - Library issue

« Last post by ww on May 15, 2026, 11:05:58 AM »

Maybe you could check under Preferences-Media Library-Local Library-View Filters ...

There is an option related to Albumartist tag handling incl. some explanation.

WW

6

Preview Build Discussion / Re: Build #24496 (May 8th 2026) - Library issue

« Last post by wd9895 on May 15, 2026, 07:35:23 AM »

Hi Dro,

sorry but herewith your find some data.

Album view in library view. Column "Artist" shows correct name.
Mysterious to me is the separation in two album. Root cause is the information in "Album Artist". If I correct this manually the two albums become one.

A comparision of the file metadata show the differences and the impact on the doubling of the album.

7

Preview Build Discussion / Re: Build #24496 (May 8th 2026) - Library issue

« Last post by dro on May 14, 2026, 05:35:40 PM »

Comparing to winamp at this point isn't helpful when they use completely different solutions especially when it comes to MP3 (you've not noted what these files were). Plus I moved to using taglib2 from taglib1 recently so maybe that has changed something which I've not seen. So without seeing the raw metadata from the file &/or an example copy showing the issue I can't say why it's seemingly wrong vs your expectations.

8

Preview Build Discussion / Build #24496 (May 8th 2026) - Library issue

« Last post by wd9895 on May 14, 2026, 04:43:52 PM »

Build #24496 (May 8th 2026)

There seems to be a library issue. Artist and Album Artist are mixed up.

Exanple:
I have a ripped CD from George Benson. The songs are stored in one folder and should appear as one collection from song 1 to 10.
But it appear in 2 CDs with same album name "20/20".

The issue was the one CD carried "George Benson", the other "Benson, George" but not in Artist name but in Album Artist. But the column in the library is just "Artist".

After manual correction of "Album Artist" the CDs appeare as one.

I have several issues found in my database which do not appear under original Winamp release as the column "Artist" reads right field from metadata correctly.

I hope to have described the issue properly enough for your debugging.

9

Preview Build Discussion / Re: Issues with build #24496 (May 8th 2026)

« Last post by dro on May 13, 2026, 08:47:59 AM »

The plug-in is a mess from assuming that what it was forked from actually worked but pull mode has never worked for me & there's no debugging modes with the plug-in. I do not like shipping such code when it's mostly never going to be used vs bloating the code base along with most of the time being a pain to figure out what should even be done for that side of things. All I know is that I managed to briefly try the plug-in with its default config yesterday & it worked without issue & having not intentionally messed with the plug-in in months I don't have a solution for why it's buggered & if it's going back to 20202 then that's a few years back. So until I can actually look at what code changed back then there's nothing I can do & no point you spending more time on it.

10

Preview Build Discussion / Re: Issues with build #24496 (May 8th 2026)

« Last post by Alex/AT on May 13, 2026, 07:05:25 AM »

Some more information: push mode seems to work sometimes, but it needs few WACUP restarts to happen so.
If pull mode is used (pull never works), and then changed to push and back instead, push also never works.
If push is working after WACUP restart, it continues working until closed. Changing to pull once fails it until next working restart.
So it seems to be a matter of some timing issue / deadlock / stale lock / handle loss happening somewhere at initialization or close to it.