Live data from Hacker News

Winamp source code leak

web.archive.org

91–100 of 338 posts

Re: Winamp source code leak

#91

Never understood why people didn't just migrate to AIMP.

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

Re: Winamp source code leak

#93
post #39

Earlier quoted context omitted.

Somewhat worrying that I can't seem to find the source code for WACUP listed anywhere, checked their website, discord, and github. I'd feel a lot better about using it if I could see the source code. Currently using Audacious with a Winamp Classic skin.

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

Yikes, okay.

I trust Justin Frankel, I don't know you, previous team or not.. The world can go on using Winamp 2.x forever and be just fine, its GRAS. If you're bringing something that isn't that, previous dev history or not, you're going to have to differentiate yourself from the folks who are also putting out winamp-alikes.

I'm not trying to be a jerk, that's just the reality.

Knowing what the code I'm running is doing is helpful in swaying me to your direction, even if that's not what you claim to be aiming for.

> should I be expected to do that when I'm the only one working on my Winamp reimplementation

Let us know when you want to change that. We're talented, and generally nice. Maybe some day you'll want some help.

Re: Winamp source code leak

#94

Interestingly enough, there has been a community project dedicated to keeping the last Winamp version alive (last version from the original creators), and it really great to use. https://getwacup.com/ It includes a skin that allows it to work on modern display resolutions. It's really interesting to see just how low-res screens were when it was in it's hey-day, given that they are nearly unusable on a 4k monitor. Edi…

hm, forgotten about that one. I get why it exists/independent/opensource whatever..... but why does it exist? Far as I can tell the 'official' v5.8 version that's been around for download on the main site and still is for a long time works great. Maybe I've just been using it for so long I don't notice any oddities (or don't need them, it's a music player for godssake), and I guess they've improved interface etc on wacup but....

Re: Winamp source code leak

#95
post #27

Winamp was still my music player of choice until a little over a year ago when I finally made the switch to MusicBee.

curious, as Winamp still my player of choice and does its job extremely well, but checked out MusicBee just now in case something I missed and saw the iTunes clone interface and closed immediately.

Re: Winamp source code leak

#96
post #67

Earlier quoted context omitted.

Wow, that's a first. Clicking the URL hung Brave, completely unresponsive for 2-3 mins, now it's loaded but shows nothing but a dark blue background. Same for every refresh, too!

Winamp ( winamp ) It really whips your browser's ass.

My brain automatically read that in that guy's voice from DEMO.MP3, complete with the bleating.

Re: Winamp source code leak

#98
post #39

Earlier quoted context omitted.

Somewhat worrying that I can't seem to find the source code for WACUP listed anywhere, checked their website, discord, and github. I'd feel a lot better about using it if I could see the source code. Currently using Audacious with a Winamp Classic skin.

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

Oh hey! Appreciate the work you've done, thanks for keeping the project alive!

Re: Winamp source code leak

#99

I listened to my first MP3 ever (Creed's "Higher") in 1999 on Winamp. It really whipped the South American camelid's posterior. Dang. I'm old.

I remember being jealous of my friend's Pentium (66? 90?) when mp3 playback slaughtered my 486.

The original Fraunhofer MP3 player, Winplay3, had settings to reduce decoding quality - which helped a lot on my 486.

https://youtu.be/vzQT4qkC-gk?t=110

Re: Winamp source code leak

#100

I nearly got a job with them back around 2001. At the time they were revamping their development group. I had written some plug-ins for Winamp so I familiar with the plug-in structure. It looks like the new lead developer wanted to rewrite everything. Using all kinds of object-oriented methodologies. The older code was all C based and very simple. I wasn’t fan of the new direction.

> the new lead developer wanted to rewrite everything. Using all kinds of object-oriented methodologies. The older code was all C based and very simple.

A tale as old as time.

Post reply on HN