Latest WACUP beta release is build #9630 (December 22nd 2021) | Latest WACUP public preview is build #7236 (March 11th 2021)


NOTE: New beta testers are not currently being added as I need to re-work the beta test program

If you've not already requested to be a beta tester & would like to then please send a PM to 'dro' to be added to the beta test group.

Note: requests to be a beta tester are processed in batches when new beta builds are released so please by patient of this process.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dro

Pages: [1] 2 3 ... 86
1
I've just had a look & I could have done with a bright screen warning when first enabling that mode but I was then able to replicate the issue.

Digging into it, the magic window that's meant to be created by the OS in response to something I have to send to the main desktop window wasn't creating it & so it set the menu item to be disabled. I've since found some different message parameters that seem to work with both normal & high contrast modes so I'll need to do a bit more testing but I think that'll do it & will be included in a future build.

-dro

2
Preview Build Discussion / Re: [WACUP 1.0.21.7236 | Shortcut]
« on: January 04, 2022, 08:40:51 PM »
As I've tried to explain, it isn't a supported mode from my side so it not working properly or it doing weird things is to be expected. This is the 'fun' that comes from a public preview release (which in hindsight I should just have called it a beta & the betas be called alpha builds).

I've also re-read things & I got the order of things the wrong way around but it doesn't make much of a difference as either way using the command-line aspects with WACUP is not supported & won't be fully implemented until I'm no longer having to use bits of Winamp for WACUP to run.

-dro

3
Wishlist / Feature Requests / Re: Chromecast Support
« on: January 04, 2022, 04:04:42 PM »
No one has pointed me to a simple nicely licensed implementation that could be used to even attempt to implement this request (I'm not going to hack up VLC source code, etc especially as I think it's then at odds on code licensing). So until there's some nice way to do it from a traditional DESKTOP program it's not going to happen & I doubt Google have done anything to help either as it's all about Chrome/mobile when I last looked.

-dro

4
Wishlist / Feature Requests / Re: Update WACUP
« on: January 04, 2022, 04:02:55 PM »
People do crappy things for numerous reasons even if it's at odds with valid reasons for limiting access but it's all about FOMO or just being a c**t.

-dro

5
I'm somewhat confused how such a theme would even be getting involved with how WACUP's build of Milkdrop works vs desktop mode unless the theme (is it the built-in OS one or something 3rd party?) is somehow messing up things in a manner I've not yet experienced from testing.

The WACUP build of WACUP checks for a specific window existing & if that's not found then it'll disable the desktop mode (is the only thing I do check) which is why I'm curious about what you're using to get the high contrast theme.

-dro

6
Preview Build Discussion / Re: Wacup, Visualizations, on Windows 11
« on: January 04, 2022, 03:54:45 PM »
From a quick read of things, it honestly sounds like it's a plug-in specific issue vs Win11 rather than something that I can really affect under WACUP.

What specific version of the plug-in are you trying to use as there's a number of versions out in the world that I'd need to know that before trying to look into what you're mentioned though I'll note it's a lower priority for now as I've still not gotten around to even attempting to setup a Win11 test VM.

-dro

7
Preview Build Discussion / Re: [WACUP 1.0.21.7236 | Shortcut]
« on: January 04, 2022, 03:52:03 PM »
Other than command-line support not being an officially supported feature due to how the WACUP loader & the original Winamp program interact (it's completely broken in the betas) & because its mostly handled by the Winamp core with the noted preview build, if you run it multiple times then it'll reload & restart playback with that command-line string along with bringing Winamp to the front as that's what Winamp does.

The only thing I'd consider changing when I get around to do it is whether WACUP gets brought back to the foreground or not but if you tell it to load a file (single or playlist) then it should always honour that action imho.

-dro

8
Preview Build Discussion / Re: [WACUP 1.0.21.7236 | Freezer]
« on: January 04, 2022, 03:47:05 PM »
What skin? What OS? I really need more information about what you're using as well as the file type(s) involved as I've nothing to go on for now.

-dro

9
Wishlist / Feature Requests / Re: Update WACUP
« on: December 29, 2021, 12:24:37 AM »
beta = intentionally restricted because it will have issues (often critical)
preview = snapshot that has non-critical issues that are generally ok & released when I'm happy with it.

and because it's restricted people have FOMO & want it rather than actually helping to give feedback when there's issues (or even worse, spread the builds around when the point is they're not ready for general usage because of the issues but some people dgaf & that just wastes my time & tbqh, I'm fed up of that).

-dro

10
Wishlist / Feature Requests / Re: Update WACUP
« on: December 26, 2021, 09:05:09 PM »
It's only been 286 days (or ~41weeks or just over 9months) between the current preview build & the most recent beta build. As I've already tried to explain, previews are just beta builds that I'm happy for more people to use & that's not been something which has been the case.

I get that people want a new preview build & don't trust beta builds even though previews are betas & based on another direct email complaint I got about this few days ago that maybe I should just call the preview a beta & betas as alphas (since that is closer to the reality of things).

but there are some crashes, and every time I open wacup, the songs in the playlist repeat the previous shuffle list every time I open it That's why I have to re-add folders at every boot.
This is the first that I'm aware of you noting having such issues (unless you've used a different handle / non-forum option to convey it) so maybe it would be better for you to try out the beta...

-dro

11
Wishlist / Feature Requests / Re: Update WACUP
« on: December 24, 2021, 02:33:23 PM »
There's been plenty of updates this year with the betas but I'm not doing a new preview build as it doesn't have everything that's needed to replace the existing preview build & not cause a load of complaints that it doesn't have things that the preview did (e.g. completely broken command-line handling & no artwork within the local library views). Making my own Winamp is hard at times.

-dro

12
General Discussion / Re: Merry Christmas and Happy New Year
« on: December 24, 2021, 11:44:01 AM »
Enjoy the time however you all are going to & hopefully it'll be safe without issues.

I'm now done on WACUP for 2021 & plan on prattling around getting my old hardware sorted out over the next week or so in the non-coding time :)

-dro

13
General Discussion / Re: The Winamp INI File for Dummies
« on: December 16, 2021, 08:52:14 PM »
I'm not against it as a storage option as it's needed to ensuring portable installs. My issues with it nowadays are more when it comes to just storing loads of data in there vs the performance impact it has (somewhat why I've been trying to reduce my stuff to only save changes from their default value into it to keep the file smaller & config reading faster).

I don't have any plans at the moment to document things as I see it more of an implementation detail & as soon as it's documented it then becomes hard to change things without cluttering up the file or having to do more in the code with settings migrations, etc. If others want to make one I'm not going to stop them.

-dro

14
My current view is that their "Winamp" which assuming it even happens as noted there's been a number of false reports of new things coming & an incomplete abandoned beta is all there is to show for it is not Winamp as I'd want to it to be. To a lot that probably doesn't matter & just having the name slapped on something is all they're going to want but I strongly don't see anything that is going to come from them which has a true 'classic' Winamp-like experience.

So for me I'm still going to be doing WACUP as a 'classic' Winamp-like experience is what I want (even if others don't or think they don't based on the comments I've seen) & in my mind anything coming from RN/AV isn't imho "Winamp" as it was known. That's fine as they can do whatever they want since they own it (same for I can make WACUP as that's what fits my needs) but I strongly don't think they get why so many have stuck with the existing Winamp because it's not a generic streaming service that is just there to make them money & help push adverts.

It's also down to each user what they want to do & use. So I'm sure there'll be those that'll abandon 'classic' Winamp / WACUP for their new version (again assuming it even happens) & that's also fine as everyone has their own needs & requirements. I just don't think they necessarily realise the cost of what they're going to be going over to if it does happen which based on what's been posted along with the job listings & prior experience is at complete odds with what I'd expect from "Winamp" (along with my obvious personal bias against that whole organisation).

-dro

15
General Discussion / Re: plugin development ressources
« on: December 10, 2021, 10:10:12 PM »
The old Winamp SDKs included the very minimum basics of what different plug-in types would be like but as things are still in flux I've not provided anything towards doing wacup specific versions & tbqh it's low on my list vs doing wacup coding (probably a mistake but I just don't have the time to prepare such things as it stands).

Compiler/IDE is completely dependent on the language as various ones can technically be used though I've only used c/c++ but I know that delphi/pascal/vb/c#/some others have been used over the years to make winamp plug-ins.

As for the goals, there might have been a basic example for exporting in one of the sdks but I need to note that it's something that is going to be added into the replacement local library plug-in & it's already present in history plug-in to allow for the changing of the playcount (the played date isn't something that's currently editable & probably is something I need to think about adding).

tl;dr: dev resources is a mess, try what you want to, some things are already on the todo list.

-dro

Pages: [1] 2 3 ... 86