Messages

1

Preview Build Discussion / Re: Issues opening multiple files?

« on: January 08, 2025, 11:49:13 PM »

...Forgot to check here for a few days. To respond to your points though...

It however doesn't seem to account for how you've described things as seemingly starting all of those instances at the same time instead of it being a gradual cascade from the first to last instance.

Yeah, I tried it again just to be sure and indeed they seem to open all at once. Though, paying closer attention now, I'm noticing it's not EXACTLY one instance per song. It's multiple instances, each with a seemingly arbitrary queue of like two or three of the songs that were on the folder I clicked "play all" in.

One thing you could try out is seeing in Task Manager's details view & sorting by exe name if any werfault instances (windows error reporting handling) are appearing at around the same time as you're triggering trying to get the files into WACUP.

I left that open on the side while doing the "play all" thing, ordered by ascending process name just to have W ones at the very top, and I didn't seem to notice anything like that at all. Just the like 6 or 7 or however many WACUP instances were popping up all at once.

I also could do with knowing what skin you're using & if you're using a modern style skin another thing is to try using a classic skin just to see if the reduced loading overhead of those skins makes any difference or not (I suspect it likely won't & is something else going on).

I've been on the standard "modern" skin, the... sorta-skeuomorphic one that was already iconic to stock Winamp? Switching to the classic skin doesn't make any difference on this though, still has the exact same multi-instance issue.

Final thought for now is if you've got the local library enabled & if so roughly how many items are in it. As going to preferences -> media library & temporarily trying this out with the whole media library disabled might also be useful to rule out some ideas I've got.

I didn't check how much stuff was in it but it's set to point to my music library folder on Windows which has like... Idunno, at least a hundred-and-something GBs of music I've collected over the years.
I did try disabling the library feature entirely from the settings since I don't make much use of it, but that didn't change anything either.

2

Preview Build Discussion / Re: Issues opening multiple files?

« on: January 02, 2025, 05:23:05 PM »

What version of Windows are you using?

Windows 10 Pro, yeah. 22H2.
MORE specifically, version 19045.4412 of that, since I haven't updated in several months and usually prefer to do that manually just in case updates break something the moment they come out.
So, at least theoretically, it shouldn't be an issue caused by some incompatibility with a recent update of Windows 10.

3

Preview Build Discussion / Issues opening multiple files?

« on: January 01, 2025, 09:53:54 PM »

Heya, I've started using WACUP about a week or two ago, since I've always loved Winamp but it was kind of painfully outdated at this point.

Loving it so far, and loving all the extra skin support and modern fixes that it has. But I've been having an issue that base Winamp didn't have.

I don't really use "media library" features in players as much as other people, and more often than not I simply manually browse the organized folders of my music collection, enter album folders, and click "play all" from Windows explorer itself.
(Windows 10 by the way)
On Winamp, this always worked perfectly fine, queuing everything in that folder (and recursive subfolders if applicable) in order and playing it with no issues. Same thing if I manually highlight a specific set of files and right click>play those.

But on WACUP, I can never seem to get it working properly even after checking through settings.
If it's not open already, it just immediately opens an instance of the player for every single song, all at once, lagging the hell out of my system and peaking my audio as it plays everything at the same time.
If it IS already running, it doesn't seem to get all the songs properly, it'll either be missing some songs at the start and/or end or just have them queued in inconsistent orders, there doesn't seem to be much of a pattern to how it breaks when it's running.

I already have it set to disallow multiple instances from the settings by the way, so I take it it has to be a bug of some kind.
I'm on the latest public preview build as of this post, is this being looked into on betas? Or has there been attention brought to the issue already, at least?