Live data from Hacker News

WinAmp Community Update Project

getwacup.com

41–50 of 56 posts

Re: WinAmp Community Update Project

#41
post #17

Few weeks ago I actually installed WinAmp because I needed that nostalgia dopamine hit of Milkdrop visualizer and those sweet skins. I downloaded some mp3 files from a YouTube playlist using FFMPEG. Unfortunately none of the mp3 worked. I think it was an encoding issue. Then I remembered the last time I faced a media file encoding problem was close to a decade ago. We take granted how good VLC or MPC-HC as software a…

VLC was the reason I stopped caring about "codec packs". If I ever hit a problem along those lines, or some media format that won't play for any other reason, instead of installing codecs or whatever, I install VLC.

Due to some quirks that I've forgotten, I've switched to using smplayer as my main video player, and winamp for audio on windows.

I wish I could remember why I switched away from VLC for everything.

Re: WinAmp Community Update Project

#42

Earlier quoted context omitted.

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. -dro

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…

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.

-dro

Re: WinAmp Community Update Project

#43
post #3

For long, I wished Winamp would be open sourced. I don't understand the benefit of keeping it closed. I'm not sure I would be back to using it though. I'm used to my current player, which already does everything I would expect from Winamp, with a (arguably) worse look but much better UX. Audacious with the Winamp classic interface is also a great Winamp for those who (still) fancy this look and feel.

The benefit of keeping it closed: squeeze some money from people googling winamp. Why would you give up that revenue stream? It might also have some residual allure to attract investment capital.

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).

-dro

Re: WinAmp Community Update Project

#44

Few weeks ago I actually installed WinAmp because I needed that nostalgia dopamine hit of Milkdrop visualizer and those sweet skins. I downloaded some mp3 files from a YouTube playlist using FFMPEG. Unfortunately none of the mp3 worked. I think it was an encoding issue. Then I remembered the last time I faced a media file encoding problem was close to a decade ago. We take granted how good VLC or MPC-HC as software a…

they were probably opus files, not mp3

Re: WinAmp Community Update Project

#45
post #3

For long, I wished Winamp would be open sourced. I don't understand the benefit of keeping it closed. I'm not sure I would be back to using it though. I'm used to my current player, which already does everything I would expect from Winamp, with a (arguably) worse look but much better UX. Audacious with the Winamp classic interface is also a great Winamp for those who (still) fancy this look and feel.

You've already got an open source Winamp if you're using the likes of xmms, qmmp, Audacious or anything else that effectively loads classic style skins (not that they tend to get it spot in) so does it really matter what the state of Winamp vs it's source code is...? I'd say no. As you've clearly got something that fits your needs as do I by slowly making my own Winamp compatible player to run my old Winamp plug-ins…

I believe the above commenter was speaking more from a place of nostalgia and curiosity, rather than "usability".

Re: WinAmp Community Update Project

#46

Earlier quoted context omitted.

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…

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 lea…

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)!

Re: WinAmp Community Update Project

#47

Earlier quoted context omitted.

The benefit of keeping it closed: squeeze some money from people googling winamp. Why would you give up that revenue stream? It might also have some residual allure to attract investment capital.

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), i…

I didn't know licenses had stopped.

They still offer the latest version for download, no hints of discontinuing it, so it will likely "morph" into something else.

Re: WinAmp Community Update Project

#48

Earlier quoted context omitted.

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), i…

I didn't know licenses had stopped. They still offer the latest version for download, no hints of discontinuing it, so it will likely "morph" into something else.

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.

-dro

Re: WinAmp Community Update Project

#49

Earlier quoted context omitted.

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 lea…

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)!

It seems that there's a reasonable implication of nft's or other aspects of the web3.0 stuff based on what's been found recently -> https://www.reddit.com/r/winamp/comments/soqig1/if_youre_won...

-dro

Post reply on HN