Live data from Hacker News

WinAmp Community Update Project

getwacup.com

51–56 of 56 posts

Re: WinAmp Community Update Project

#51
post #32
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.

Clementine.

I can indeed do most things with a few keystrokes, including queuing and finding things in the playlist (by filtering).

It's not as lightning fast, but it's fast enough. It supports several playlists and has other niceties.

Re: WinAmp Community Update Project

#52
post #51
post #32

Earlier quoted context omitted.

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.

Clementine. I can indeed do most things with a few keystrokes, including queuing and finding things in the playlist (by filtering). It's not as lightning fast, but it's fast enough. It supports several playlists and has other niceties.

Ah, very nice. Clementine is great, agreed.

Re: WinAmp Community Update Project

#53
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…

> Also source code is pointless without dev(s)

Given the number of people still interested in Winamp, I'm sure there would be people willing to work on it if it were open-sourced.

I meant no offense :-)

Re: WinAmp Community Update Project

#54
post #50

What is the point of doing this instead of writing a clone?

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.

-dro

Re: WinAmp Community Update Project

#55
post #53

Earlier quoted context omitted.

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…

> Also source code is pointless without dev(s) Given the number of people still interested in Winamp, I'm sure there would be people willing to work on it if it were open-sourced. I meant no offense :-)

No offence taken. I would just rather than waiting around for those many willing devs (most of which seem to be web devs rather than native client devs from my past 8yrs experience) to appear I've instead put my time & effort into making something as I was already doing for the decade before Winamp was eventually sold on.

So as long as I end up with WACUP being a program that fulfils my needs in allowing my plug-ins to keep working & happens to be of use to others wanting a supported native 'classic' winamp experience (due to the pivot from a plug-in pack to being a standalone player) then I'm going to keep doing it irrespective of what is / isn't happening with "winamp" (I don't view anything that now comes out as being winamp other than a brand name slapped onto some code).

-dro

Re: WinAmp Community Update Project

#56

Earlier quoted context omitted.

For the visualizations - Milkdrop is alive and well as projectM (which sometimes comes bundled with VLC, sometimes not?): https://github.com/projectM-visualizer/projectm Which has a ridiculous level of cross-platform compatibility. I can throw up 3 copies of projectM-pulseaudio on my big 3-monitor work machine and have it listen to any audio sink, I've got it installed on my Android TV and it happily responds to what…

My issue now is that there is no way to stream my music and make these visualizations come up on people’s screens I want something as simple as spotify over chromecast, that shows these visualizations on the fly The metric is: can I do this in a hotel room that happens to have a smart tv? Because it has to pass that bar, not the bar of plugging in a computer to my own tv’s hdmi port

Bit late answering this, but projectM for Android does have the chromecast feature! It streams whatever audio is playing on the device along with the visualizations. iirc it does require you leave the phone/whatever open on that though otherwise casting loses the audio, that might be different with newer android APIs though..

Then there's all the other screen casting things like miracast or whatever, depending on what the smart TV supports (if it supports any).

Smart TVs themselves are so inconsistent and jank though, I think I'd prefer to bypass all the broken bullshit and just use a HDMI cable.

Post reply on HN