WACUP
General => General Discussion => Topic started by: musicf8 on September 16, 2018, 08:58:05 PM
-
Kind of surprised it took this long to actually leak tbh
-
Me too though it makes you wonder what snapped in someone to finally do it (or is it a side-effect of the twitter account hack or is it even about testing the waters though I somewhat doubt that last idea). Not that there's many people who would have had access to that build...
-dro
-
I have a feeling it is related to the twitter hack, as there might have been a link to the beta in the DMs, if not then that's some interesting timing haha
-
The DMs aspect would only make sense if it also included login details to get the beta download site / page (but then doing that via twitter was a dumb move & I thought the preference was email / mailing lists). Though iirc how it was done changed after I was let go so I don't know if they kept a one-login for all approach (probably the case) or moved to per-user login on whatever was being used (I somehow doubt that would have been done).
Either way, the reactions have been interesting from what I've seen so far though as it's from an unknown source & not known what might have been done to the installer / files included, a cautionary approach for those wanting to try it out is the only way (though I'd rather stick with a patched 5.666 than try that thing out or as I'll instead do, just keep using my WACUP builds :) ).
-dro
-
WACUP is much better :D
-
Am a bit surprised (but not too much) that there's still not been anything mentioned by the current owners.
-dro
-
Well we've now got https://techcrunch.com/2018/10/15/winamp-returns-in-2019-to-whip-the-llamas-ass-harder-than-ever/ which my reading of it implies that the 5.8 that will be formally provided (which makes me now think more so that the leaky build was to test the waters / find any major bugs) & then that's the end of the desktop version with "Winamp 6" being their mobile / web solution (based on the war with itunes is over comment - that's just got to mean no more windows builds at least based on the 2.x/5.x base).
I'll still be here working on WACUP (though I know a lot are questioning why even before all of this) as I think it shows that more than ever we need a properly supported windows client (going 64-bit is something that needs to be considered sooner as well) & now a lip-service release that is barely changed from the leaky build which itself sat untouched for most of the last 4.5 years. Otherwise the mobile platform agnostic marketing blurb isn't surprising as I'm sure I heard it all in meetings 4 years back & I honestly don't think it's going to be what people expect *shrugs*
-dro
-
I read on a german news site that we get on 18. october a offiziell 5.8 build. Will you take this as base?
-
Nope, I'm not going to touch 5.8 in any manner as if I was to try & rebase WACUP on top of 5.8 it'd set me back a few months from having to re-apply & validate some of the specific patches as well as everything else around it.
But as I'm working towards not using the 5.666 files long term, to change to then rely upon a build from a company I despise, it doesn't make sense to me :) And if the implications in the article are correct (as well as the tone from https://www.firstpost.com/tech/news-analysis/winamp-is-returning-as-an-all-in-one-music-player-but-it-wont-be-out-till-2019-5386901.html which references WACUP), they're more than happy to ditch the old version & that leaves a gap for WACUP imho.
-dro
-
not using the 5.8 files? sounds like a different player?
-
The aim is that WACUP will become it's own thing (hence the recent changing of the 'P' from meaning 'Pack' to now be 'Project') & not rely upon using key Winamp files as it currently does. Sure it'll be possible to use the 'legacy' Winamp plug-in files if I get it right but my aim is more about having something that can be supported & developed going forward instead of as this 5.8 appears to be as the end of the line (which imho would be better to not do & just lave it as 5.666 as sod all has really been done for the amount of time passed vs what is meant to be in 5.8 based on the leaky build changelog).
I've already technically replaced or removed the need for over 50% of the 5.666 provided files (it's closer to 60% with things that are in-progress). So that's why I don't see any benefit to having to re-do a load of work to then continue with replacing files / features that I've had to become compatible with. That's one of the main reasons why I don't want to touch 5.8 as I've tried to explain a few times previously (& probably not as well as I could have).
-dro
-
Something tells me, their 5.8 won't be able to quite do what I can do with Wacup now and the odds of them listening to me to change something is pretty much 0%. With 5.8 being the last Desktop update it would seem, why bother? I don't own a smart phone (do what!?) so that is all irrelevant to me.)
-
I just saw the news about Winamp 6 on techcrunch, I think they're going to ditch the desktop client after their 5.8 update, WACUP has become a completely different player in a very good way tbh and I love it very much, so this news doesn't excite me much.
-
Well that seem to have shown their hand (re: https://getwacup.com/community/index.php/topic,410.msg2959.html#msg2959) unless it's a ploy to go "oh ok we've heard you" but I doubt it & is why I think WACUP is going to be the best option going forward (I just need to hold up to my part of getting things public ready).
MarkRH: that's sadly a fair summary of things as you're not the streaming user that they want (& need) to make them $$$. and without your requests wacup wouldn't be where it is & I'm eternally grateful for that.
Wimukthi: that's been the aim to try & channel that actual winamp feel rather than getting an incomplete build given as a 'final' release as 5.8 essentially is now.
-dro
-
https://download.nullsoft.com/winamp/client/winamp58_3660_beta_full_en-us.exe it is released
-
WACUP > <that> 🤣
-dro
-
WACUP > <that> 🤣
-dro
I'm just 'flabberguested' by the whole thing. Can't understand they took this course. Could at least have geared up, join forces or something like that. They should be happy someone like you has kept this project alive. Its because of you the true fans had something they could go on with. I hope this is some corporate shitstorm, can't imagine this had anything to do with the original Nullsoft spirit. Correct me when wrong. I'm not going for the new Winamp unless they appologize to you and the rest of the community who kept the lama alive.
Had to said it.
WACUP <3
-
When you look at how they're now dealing with the paying SHOUTcast broadcasters including deleting posts off their facebook page (I assume to remove the complaints about how piss poor a job they are doing & the never ending ones about support never responding), there's very little chance of them apologising to the community.
Even if the v6 does appear (am somewhat doubtful tbh) they'll laud it up as being the saviours of Winamp which is ironic after 5 years & a lacklustre beta that was sat on for 2 years with little done in the prior 3 years due to not wanting devs to work on it. There are going to be people who lap it up based on the types of comments I've seen online in relation to the v6 speculation but imho it's just going to be a mobile services api wrapper without any of the charm of what made Winamp be Winamp & a complete kick in the balls on what that brand meant.
Either way, I've got a preview build to sort out :)
-dro
-
Dr0 - I remember a post I made years ago about 64bit migration of the desktop client. I believe, the response was why...32bit works or something to the effect.
Silly, argument at the time... You just got me thinking by your post about it.
------
As for the new builds. How, can what they build ever compare to the multitude of high value, routinely developed, patched and versioned high-end solutions?
- Music Bee
- AIMP
- Foobar
- XMPlay
- Itunes (blech)
- Clementine
- Media Monkey
- Amarok
- Banshee
- VLC Media Player
These are from memory, and relatively they are in many cases very well supported, include many of the features that winamp had/has; and are each quite usable. Then there are the various players for streaming subscriptions that are hands down amazing products on their own rights (spotify, amazon, etc.)
I think imho that winamp itself needs the investment and drive of developers wishing to put it into the 21 Century with a feature-set that covers all of the integration, services, capabilities of these peers now that it has been sleeping on the job; or it will remain in the shadows relegated to enthusiasts only; they have a-lot to catch up to; with very few that internally doing the work required to bring it to the masses.
-
Well my views on a native 64-bit client has changed over the last year or so as it's now one of the goals to achieve for WACUP. Yes for the most part it's not going to provide any real benefit over 32-bit (the common one is that if there are memory issues then a 64-bit version is often able to keep running much longer without exhausting the memory space available) but as a lot of platforms are generally going native 64-bit, for a Windows program to completely ignore that is in hindsight a bit naive.
Winamp desktop development as far as anyone can tell is dead & most of the players you've mentioned are developed by very small groups but it's the keeping development going that is the prime aspect which Winamp doesn't have & they do. I think that's part of the reason why some which have been around for so long aren't viewed as 'dead' (unlike Winamp) because there is that perceived support & reasonably regular updates.
The biggest issue any dedicated Windows player has nowadays is that a lot of the services that people are using are locking out Windows due to DRM, etc (e.g. Spotify) & with so many using mobiles for consumption, any of them can now be viewed as niche (even if they've got potentially millions of users). The landscape has changed a long time back & I know that Winamp has massively slid down that list & if it's in some guise (native or as the wacup replacement) is going to survive as a niche player than so be it. In some ways the push to make Winamp more mainstream removed what made it Winamp.
-dro