Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WinAmp Community Update Project

getwacup.com

Post reply on HN
Print view View original

31–40 of 56 posts

Re: WinAmp Community Update Project

#31

Post by thedoctor_o »

jraph wrote: 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 (which were always closed source nor am I for or against OSS but it needs to be the dev that decides not external pressure) because I don't trust nor like what's happened with those that now own the brand.

Also source code is pointless without dev(s) & unless we're looking for AI to do all of the coding, whether the code is open or closed, the fleshy meat bag bashing the keyboard is still needed for the time being :)

Use what makes you happy & I'll keep making & using what makes me happy too :)

-dro

Re: WinAmp Community Update Project

#32

Post by stavros »

jraph wrote: 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.

What player do you have that has better UX? Winamp was lightning fast, could do anything in a few keystrokes (especially that "jump to" dialog was magical) and got out of the way. It was perfect.

Re: WinAmp Community Update Project

#33

Post by thedoctor_o »

alternatetwo wrote: post #29
jraph wrote: 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 source code leaked a while ago, but IIRC not the final version. And it's not like one could really use it.

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

Re: WinAmp Community Update Project

#34

Post by thedoctor_o »

poisonborz wrote: post #16

If you look for a more modern Winamp-like audio player - down to supporting a lot of Winamp plugins - I really recommend AIMP.

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

-dro

Re: WinAmp Community Update Project

#35

Post by silisili »

captbaritone wrote: post #22
ahmed_ds wrote: post #11

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…

For anyone wanting to dip back into the nostalgia of Winamp and Milkdrop without installing any software, I made https://webamp.org for that exact purpose. It can render real Milkdrop presets and real classic winamp skins directly in the browser. Also, it’s open source: https://github.com/captbaritone/webamp

Cool site!

One note: On Brave mobile, the seek slider doesn't actually work. It moves and says 'seek to:' but doesn't.

Re: WinAmp Community Update Project

#37

Post by [deleted] »

captbaritone wrote: post #22
ahmed_ds wrote: post #11

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…

For anyone wanting to dip back into the nostalgia of Winamp and Milkdrop without installing any software, I made https://webamp.org for that exact purpose. It can render real Milkdrop presets and real classic winamp skins directly in the browser. Also, it’s open source: https://github.com/captbaritone/webamp

[deleted]

Re: WinAmp Community Update Project

#38

Post by justsomehnguy »

alamortsubite wrote: post #20
ahmed_ds wrote: post #11

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…

I don't know about the visualizer, but Audacious lets you install Winamp skins. Source: rocking Bento Classified uninterrupted since 1999.

>rocking Bento Classified

https://archive.org/details/winampskin_Bento_Classified

Re: WinAmp Community Update Project

#40

Post by alternatetwo »

thedoctor_o wrote: post #33
alternatetwo wrote: post #29

Earlier quoted context omitted.

The source code leaked a while ago, but IIRC not the final version. And it's not like one could really use it.

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 when shutting down ... why would that be? Is that fixed in WACUP?

Post reply on HN