thedoctor_o

Alas that was never a complete open sourcing & you couldn't just build it from what was provided. There was a small effort to try & fill in the gaps (it used a trac site I think to cover what was going on) but sadly it never amounted to much.

-dro

NSIS has nothing to do with the lot that own Winamp & it was a clearly defined "not part of the sale" as it has been OSS from early on around it's v1.0 iirc which was a long long time before Winamp was eventually sold.

I still think they should be using their own forum with an archive of the NSIS sub-forum to ensure that there's a clear distinction between them & the lot that now own Winamp (as there's no benefit for them to be keeping that forum running other than a trickle of ad revenue) but that's down to those that lead NSIS to decide upon.

-dro

The pure Nullsoft Winamp was from 1997 to mid-1999 with AOL having Winamp under it's ownership until 2013 (technically until mid-January 2014) when it was sold to Radionomy (who then were bought by Vivendi but then bought themselves back under the guise of Audiovalley).

So that time with AOL covers v2.5 when it became free after starting out as shareware through to v5.666 along with the maligned WinAmp3 period. So that's whole a lot of not doing much but still producing releases for almost 15yrs. Winamp (& SHOUTcast) were sold before Verizon did it's thing with AOL.

-dro

There's also re:amp which is a decent implementation of the Winamp classic skin support.

-dro

It does with WACUP

-dro

I'm also not trying to be a jerk either but when I'm constantly being told by random people that I have to be OSS when it comes to WACUP that's also not particularly helpful other than introducing more potential work for me to do when there's absolutely no guarantee of a return to that effort. So maybe I'm more terse than I should be about such things but that's also just how I am.

It might make more sense for other projects especially those starting out fresh but that's not ever been my mindset with how I've been doing Winamp plug-in related development since 2003 along with the 5yrs I worked on Winamp & if that means people will avoid WACUP then so be it as they're more likely to be sticking with the AOL provided 2.x releases anyway.

Also it goes both ways on the trust aspects & maybe when the likes of fb2k, aimp & musicbee go OSS I might eventually reconsider my dinosaur like approach to development but there has to be a tangible benefit for me to do it.

I've already asked for help over the 5yrs or so I've been trying to make WACUP but the things that need help with doing are also the things that no one really wants to do (e.g. a new good midi input plug-in).

-dro (assuming this reply ever gets posted as I've been trying for over an hour)

Is all good.

-dro

5.x is just the 2.x base continued with newer plug-ins & newer apis for those plug-ins. Unchecking things during installation (e.g. choosing the lite install) or just removing the unwanted plug-ins was always an option to make a 5.x into a comparable 2.x install.

-dro

Fairly certain that fb2k has never been FOSS or can you point to where that's not the case as that'd be far more interesting than the point of this thread.

-dro

Maybe because not everyone likes how AIMP does what it does. Same for why there's been numerous other media players over the years - one solution doesn't work for everyone or we'd all just be using iTunes or VLC or WMP. Choice is good.

-dro

Supposedly they're still going to call it Winamp v6 assuming it happens. They've lied a number of times over the past 8yrs so don't hold your breathe but the new site is somewhat indicative of their disregard about why those still using Winamp (or clones of it) do so.

-dro

Then don't use it if you only want to use 100% OSS.

I'm making something that I want to use (essentially a compatible implementation for my plug-ins to run under) & if it's of use to others then that's a bonus.

At no point has WACUP claimed to be 100% OSS nor should I be expected to do that when I'm the only one working on my Winamp reimplementation. Aspects that need to be done that way are done so accordingly.

-dro