Latest WACUP public preview for x86 & x64 is build #23960 (March 1st 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #23960 (March 1st 2026) (x86 & x64 changelogs)

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dro

Pages: 1 ... 111 112 [113] 114 115 ... 134
1681
General Discussion / Re: So.... Winamp 5.8 Beta was leaked
« on: October 16, 2018, 08:50:31 PM »
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

1682
General Discussion / Re: So.... Winamp 5.8 Beta was leaked
« on: October 16, 2018, 05:59:34 PM »
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

1683
Archive / Re: Which skin should be the default on new WACUP installs?
« on: October 16, 2018, 01:53:09 PM »
Thanks for all of you who've commented on this even though it's been a bit confusing when I've taken into account other comments & general views about what people expect from a Winamp based install (more so from the few hundred comments, tweets, etc that I've looked at over the last day).

So based on all of that, the best approach with new installs is going to be not pre-selecting the default install skin (unless installing over the top of an existing install or if modern skin support is not present) & go with the preview selection dialog from the first post (which also appeared in beta build #2826) & do the one-time selection by the user as there honestly doesn't seem to be a single way to appease the majority when it comes to the default skin.

The reasoning for this is that although most of the comments from our group is for the Big Bento Modern (BBM) skin (or keeping with the Bento/Big Bento modern skins in general), the wider view point about Winamp is the 2.x classic skin & about the experience being fast to load & lightweight on resources & even with modern hardware, a modern skin is still typically taking a few seconds to full load.

With the preview selection dialog the current ordering of the skins seems to make the most sense as it puts classic & BBM as the preferred classic & modern skin options by default whilst still providing Bento & Winamp Modern as there's still a lot of love for those skins out there. As based on the feedback, BBM seems to be the preferred modern skin but you have an easy way to not go with it so everyone wins :)

Finally, requiring user input maybe isn't ideal in some eyes but the preview dialog we've come up with covers the commonly expected options as well as educating the user on how to change the skin which is something that was sadly missing from the Winamp provided option & has possibly caused confusion over the years.

Hope that all makes sense & why the decision has been made & I've attached the final version of the preview selection dialog for convenience :)

-dro

1684
General Discussion / Re: So.... Winamp 5.8 Beta was leaked
« on: October 16, 2018, 01:37:57 PM »
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

1685
Skins / Re: Huge Collection Of Skins Available
« on: October 03, 2018, 10:02:56 PM »
I'm assuming that dump that's mentioned is what was later posted on the Winamp Enthusiasts group? If it is then I've just passed on that link to the Internet Archive people to process & add in what hasn't already been collected by them (if it's a dump of winamp.com then they've most likely got most of them already). Same goes for any other skin collections people may have as they're double-checked for duplicates so the main skin collection on the internet archive is just giving what's there rather than a load of duplicates as sadly a number of the skin dumps I've seen provide.

-dro

1686
Skins / Re: Huge Collection Of Skins Available
« on: October 03, 2018, 12:25:10 AM »
This has just been posted https://blog.archive.org/2018/10/02/dont-click-on-the-llama/ & is why I'd made my early suggestion to send them the files as there's the (currently classic skin only) colleciton of skins @ https://archive.org/details/winampskins that they're gone through & de-duplicated & started to tidy-up, etc.

Am hoping it won't be too long before modern skins appear in the collection (they've got them) as that'll make the in-WACUP skin browser/installer I want to add actually be useful instead of just being limited to classic skins only.

-dro

1687
Wishlist / Feature Requests / Re: Yar-matey! Playlist Copier
« on: October 01, 2018, 06:04:44 PM »
Maybe a better option would be to have a known good curated list of plug-ins and a way to obtain them in-wacup based on what is tested / suggested & confirmed to not cause issues (e.g. must be portable aware & not have odd external dependencies). That might be a better solution 🙂

-dro

1688
Unless something is preventing the process from correctly closing & being able to save it's settings, window positions should be remembered automatically.

Can I ask what was done to fix the issue or was it just doing a re-install & that fixed things?

-dro

1689
Skins / Re: Huge Collection Of Skins Available
« on: October 01, 2018, 12:15:21 AM »
I think it's the same thing tbh but I've not tried it out nor how it compares to the dump that's on the mywinamp site (which is being used as a basis for the skin collection that the internet archive have been collating & hence my recommendation to pass this to them so they can add anything they've not yet got a hold off).

-dro

1690
Wishlist / Feature Requests / Re: Yar-matey! Playlist Copier
« on: October 01, 2018, 12:12:59 AM »
It's not hard to just install it once ;) I'm not sure about adding it to be honest as it in its current state needs more work to have it to be able to work on library playlists so it's a more complete solution. So I might do some work on the plug-in later on but I'm still not keen with adding it into WACUP (hard to put into words).

-dro

1691
Going in reverse on the points raised, it's generally down to the skin (or colour theme if using a modern skin) to determine what is shown as the actively playing item text colour. So it might be that you can just change the skin values to get a better colour scheme to better identify the currently playing item.

However I can see that there's scope to allow for overriding that (like I can already do for queued & missing playlist items depending on what's been installed) so that the background as well as the text colour can be changed.

With the selection side of things, moving the selection is entering an odd territory imho (I think there's something like it in fb2k) as it can get confusing at times especially with how to handle having a multiple selection. I get why you'd want something like this & is why I've answered this bit second as it's possible that doing the first part would actually be the better option than trying to break something which I think is better left alone (plus changing the drawn output is a lot easier to get done as I've got the code already written for the features that already use it :) ).

-dro

1692
Skins / Re: Big Bento Modern - final release v1.02
« on: September 19, 2018, 04:30:00 PM »
Lets take the default skin discussion over to https://getwacup.com/community/index.php/topic,382.0.html as there's a few things that the talk this morning has made me think off but am sure there's more / better options :)

-dro

1693
As the title of the thread says, I need some input on which skin should be the default on new WACUP installs as we'll soon have 4 possible skins to choose from when making a WACUP install. I really don't know which one should be the default as there's numerous arguments depending on how we want to aim WACUP going forward or just what people's expectations are in terms of usability vs performance & resources (i.e. classic is much lligher-weight compared to a feature complete modern skin & whether a few seconds to load the skin is acceptable or not)

The skins we'll have are:
  • 2.x base skin (with WACUP tweaks)
  • Big Bento Modern (BBM)
  • Big Bento / Bento (Winamp default from 5.5 to 5.666)
  • Winamp Modern (Winamp default from 5.0 to 5.35)

There are also some other possibilities to be considered...

The first is on a clean WACUP install (which would also cover updating an existing 5.666 install) we essentially force a skin to be selected as per the attached first_run_skin_selection_mock.png image (the layout & wording is just an initial spin on the idea so don't be too harsh :) )


The second is we go with a default skin and instead have a 'pimp my skin' section on the installer skin selection page as per the attached pimp_the_skin_mock.png image which would possibly cycle through the screenshots of some of the other skins present so you can see what the others may look like.


Maybe both options make sense to implement or just the one (possibly the first option seems to be a better fit from the discord conversation that led to this thread & some comments in the BBM thread).

So over to you as I would probably go with classic & the forced skin selection on first run but my view on this will not be the final decision & it's what the majority vote or even what is a better suggestion that comes out from this that will end up being implemented :) I'd also appreciate knowing why you think whichever option is the way to go or not as that definitely helped with the update system thread to make the feature work well.

-dro

1694
Now that beta builds 2740 and newer have updating support (with 2800 hopefully resolving all issues related to it) I'm going to un-pin this thread as I think we can call it as a done feature. Thanks to all who contributed in the suggestions & testing of the the update system.

-dro

1695
General Discussion / Re: So.... Winamp 5.8 Beta was leaked
« on: September 18, 2018, 09:27:34 PM »
Am a bit surprised (but not too much) that there's still not been anything mentioned by the current owners.

-dro

Pages: 1 ... 111 112 [113] 114 115 ... 134