No legit project could ever make use of the leaked source code even if it was from just before the end of the pre-sale AOL era so the person who did that never actually helped anyone & imho just hindered things.
I can't use it for WACUP & I don't see how any of the other players out there (clone / compatibles / just looking to hack in some features from it) could ever use it either.
There's also the whole "source available" thing they announced earlier this year still likely means it's never going to be proper open source against how media / others at the time took it to mean. Not like things couldn't be done via plug-ins but for whatever reason so many seem to forget about that & only see source code as the only way to modify things which imho is just going to make things messier if / when something does happen.
source available is not the same as open source nor have any terms been provided on what that'd actually be other than it's seemingly just about them getting a free dev team or looking to be doing some good from an investors view point.
Because they primarily wanted shoutcast (ironic since they sold that off last year & got played in the process of doing all of that) which meant taking winamp with it. It's all a mess now but most care not for that and just see that "winamp is back".
Most of the crashes tend to be due to the parts re-used from 5.666. Also it's a preview build (aka public beta) so it can & will be unstable.
As for what place it has, I'm going to still make it because I've very clearly been made unwelcome to remain as a "winamp" user plus I don't like where it's owners are taking it with all of the ntf related stuff & taking the piss out of the user base for so long. So if I want to have something that can keep my plug-ins working then I've got to make my own player which is what I'm doing.
I had been doing that much more early on along with replacing some of the plug-ins & dlls. After a point the reality dawned that I was replacing so much that I was on the road to making my own player. Also how things have gone with the owners I just don't want to be doing anything that uses their offerings
There's still some live patching / splicing needed for some of the plug-ins that are still re-used from 5.666 as part of the current beta builds along with WACUP having the ability to run minus EQ & modern skin without the winamp core exe. As there's a few things from that exe which the modern skin plug-in requires to work which I've yet to work out all of the interfaces to allow the plug-in to work. It's part of what's been holding up a new preview build as I just need to be as free from having to leverage bits from Winamp as possible.
It's a gradual reimplementation whilst using some of the pre-compiled 5.666 exe / dll (how much depends on the build being used) with the end goal for WACUP to not require the 5.666 files, be plug-in compatible & it's own thing.
It is going to end up as a clone (as per the banner text on the site) but when I started out I didn't expect the lot that owned Winamp to fuck it up so much & abandon it. Every build uses less of the pre-compiled exe/dlls that come from 5.666 & I've currently get beta builds that can now run completely without the Winamp core along with a native 64-bit build because why not.
WACUP began as a a plug-in pack but I've pivoted to it becoming it's own player but it takes time as I've been patching / replacing the 5.666 plug-ins with my own which allows me to have the best plug-in compatibility possible unlike most other clones that do a sub-set of the Winamp 2.x api vs I wanted something that would support up to 5.666.
What revenue stream? There's nothing from pro licenses now as that was stopped prior to the sale from AOL & thankfully it doesn't seem like they've been forcing in-client adverts (though they'd talked about doing it). I'd love a revenue stream that's just some of what Winamp was making prior to it's sale rather than having to scape by.
So other than what's coming any adverts on their forum (dunno if there are any), it's being propped up by other aspects of the audiovalley group (e.g. the targetspot/shoutcast advert/charges to pay for the streaming service).
That's probably why they're going to do some sort of subscription / nft / 'donate to artists but take a cut' type of affair with whatever they may end up slapping the Winamp brand on.
'classic' Winamp is officially dead from what's stated on their awful web3.0 website & that might be fine for whoever but it misses the point of why however many have kept using it in a streaming-centric world - they don't want streaming services & Winamp being turned into a Spotify wannabe as seems to be the case is sad to see).
5.666 was the last full release of 'classic' Winamp. What is currently offered is an incomplete 5.8 beta that's "not an on-going project" (which is what was stated on their website for that download for over 3 years) so take of that as you will.
From the job listings that have been seen for their new team (which also confirmed they'd done nothing for many years despite the marketing lies) imply something that is completely different with the Winamp brand slapped on it.
AIMP misses the boat on the sort of Winamp plug-ins I still want to have supported whilst not using an actual Winamp itself (as is now the aim for WACUP). Sure it's an option but a limited sub-set of Winamp 2.x era plug-ins isn't great :)
It pre-dates the 5.666 release & is of no use to any project trying to do things correctly i.e. whoever did (I have my suspicions) basically shafted a load of projects that could have made legitimate benefit.
I think it was precisely your blog post (?) which I read that detailed that it was pre 5.666!
Is the problem that now that the source is out you can no longer claim plausible deniability you never saw it or what exact complications does it cause by just being leaked?
And one other (WinAmp related question) - I still use 5.666, but it has the weird issue that it's the one program that Windows can't get to close itself when shutting down ... why would that be? Is that fixed in WACUP?
The complication is that what's been leaked just can't be used by anything trying to be legit because it was not released in any official manner & so it's license isn't at all clarified even though it's a pre-release copy from the AOL era which some would say it's abandonware. Plenty saw the publicly posted screenshots of partial headers from the source files on twitter that were being used to prove it was a real leak which I unfortunately was greeted to on opening a DM (which I wasn't happy about) otherwise everything else gleaned was taken from others observations at the time.
With the clear demise of 'classic' Winamp with the whole 'set the tone' & seemingly nft related crap the new lot are now going for, what was leaked still equates to what's gone to the new owners (which was one of my pre-sale tasks) so it's into the messy state of who has recourse against it being leaked.
As for the issue, I don't remember there being anything specific that is in place to make it intentionally block system closing unless it's taking too long &/or it's crashing. I don't have the Winamp core handling that aspect of the running process with the current preview build (& the beta builds barely let the Winamp core do anything with it being able to run without it with some missing features) so the best way to find out if it behaves would be to try it out as a portable install so it doesn't mess with your existing Winamp install.
Mh, that makes sense. And what, the new Winamp owners are into NFTs? I have no words.
It will never close (unless you click "shut down anyway"). Maybe I'll dig into that some day - after a quick google, maybe it just doesn't honor the window messages to close the program.
I use a portable install anyway, so that hopefully won't be an issue (if I ever get around to testing)!
I can't use it for WACUP & I don't see how any of the other players out there (clone / compatibles / just looking to hack in some features from it) could ever use it either.
There's also the whole "source available" thing they announced earlier this year still likely means it's never going to be proper open source against how media / others at the time took it to mean. Not like things couldn't be done via plug-ins but for whatever reason so many seem to forget about that & only see source code as the only way to modify things which imho is just going to make things messier if / when something does happen.
-dro