Latest WACUP public preview for x86 & x64 is build #20202 (September 28th 2024) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #20686 (December 23rd 2024) (x86 & x64 changelogs)


NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

Recent Posts

Pages: [1] 2 3 ... 10
1
Preview Build Discussion / Re: Issues opening multiple files?
« Last post by LazyTomato 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: APE Tags causing crash
« Last post by TheDaChicken on January 07, 2025, 09:54:13 PM »
Thanks so much and letting me know about x64. I can try x64. The issue is I do use the Stereo tool Winamp plugin.

I will definitely wait for the next public build (since that's only what I have access to).

I hope the beta builds go well
3
General Discussion / Re: Winamp ML import
« Last post by dro on January 07, 2025, 04:31:25 PM »
I refreshed the metadata for all items and everything still looks fine.
That's good to know.

I remembered one thing, after I did the import legacy via WACUP the original db files in the Winamp folder was overwritten with an empty one. A backup of the files was created (I made my own anyway) but it was still a disturbing experience. ;D
That's not meant to be happening & is related to the problem I found yesterday which stems from changes I'd made for my primary db file handling a while back but I missed by not fully re-testing for legacy db imports in missing that it was converting them to the newer format when that was never the intent of that mode. It should be fully resolved when the next build is ready to go up with them treated as a read-only action to avoid modification.
4
General Discussion / Re: Winamp ML import
« Last post by DJay on January 06, 2025, 07:42:11 PM »
I'll answer here. Now everything is in the right place, thanks. I refreshed the metadata for all items and everything still looks fine. I remembered one thing, after I did the import legacy via WACUP the original db files in the Winamp folder was overwritten with an empty one. A backup of the files was created (I made my own anyway) but it was still a disturbing experience. ;D
5
General Discussion / Re: Winamp ML import
« Last post by dro on January 06, 2025, 06:57:22 PM »
Have replied to your pm with hopefully complete db files for you to work with.

For you setup the location of the files wasn't an issue but part of my testing had me trying to use a read-only folder & that was helping to show part of the problem since it prevented the conversion of the existing db files to the newer nde based format that I use before being processed for the import action. However the import shouldn't have been attempting to mess with the files & not doing that resolves the incomplete / full failures that I'd been able to replicate as part of the import plus it also makes the importing to be somewhat quicker.
6
General Discussion / Re: album art overview
« Last post by DJay on January 06, 2025, 04:52:21 PM »
I understand your approach perfectly. I'm also a dev, but in this case I'm just a long-time Winamp user accustomed to a specific view, so I'm probably not objective.  ;)
7
General Discussion / Re: Winamp ML import
« Last post by DJay on January 06, 2025, 04:46:09 PM »
This is good news. I have the files in c:\Users\Me\AppData\Roaming\Winamp\Plugins\ml\
8
General Discussion / Re: album art overview
« Last post by dro on January 06, 2025, 04:11:49 PM »
The alternating row aspect isn't implemented because as I went with a more Explorer like approach that ends up looking odder like a chequerboard since there can be multiple on a line unlike what winamp's local library plug-in was doing. What's right I still don't know & tbh it was a pain in the whatnot to get something working that didn't suck on the performance vs OS support which I was generally happy with as a first usable form. I also don't necessarily just want to mimic what winamp's offering of things did as some aspects I never liked when I was a dev / user of it but I get that from a user view point if the outer parts are all winamp-like then there's an expectation for the insides to also be the same or more similar. I'll have a think about it all for when I get back around to doing more on the local library view modes.
9
General Discussion / Re: Winamp ML import
« Last post by dro on January 06, 2025, 04:07:21 PM »
I've been able to get it to import it with what appears to be the expected total number of records (14860) along with the view specific numbers you've noted. However there's something odd going on with the import action depending on where the files are being accessed from which I'm trying to figure out at the moment which seems to be the likely explanation of why things didn't seem to import correctly.
10
General Discussion / Re: album art overview
« Last post by DJay on January 06, 2025, 03:50:47 PM »
No problem with selected item highlighting. I meant even/odd bgcolor vide Winamp look. IMHO without clear spaces and a separator, the view merges, especially when we want a smaller thumb size, but it's your call  ;)
Pages: [1] 2 3 ... 10