Latest restricted WACUP beta release is build #19100 (May 10th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #19100 (May 10th 2024) (x86 only)


NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

Recent Posts

Pages: [1] 2 3 ... 10
1
Wishlist / Feature Requests / Re: Toaster plugin
« Last post by dro on Today at 02:07:54 PM »
The old toaster plug-in not working from what I remember isn't necessarily a WACUP issue & is mostly due to the age of that plug-in as it wasn't working under Winamp properly for a long time due to how it was trying to use the OS gdiplus implementation from what I remember. I thought there was a patched version of it though I don't see the site for it is up & can't remember where that might've been posted.

I don't know if I'm going to make my own version of it or not at any time soon since there's many other things I still need to do for the core WACUP implementation.



The lyricsplugin should be working under WACUP as I know a lot of people still use it & I've even got some specific handling in place to detect it over my for now local lyrics only plug-in & disable my plug-in so the two don't conflict. It might just require moving the plug-in dll over into the WACUP\Plugins folder as other changes to avoid program installation conflicts means it likely won't auto-detect the install location.

Trying to offer a form of online lyrics look-up is on my todo list, it's just how / where to do that when I don't have the means to pay for a service that is the main problem doing it from when I last looked (trying to use the lyricsplugin online db is afaict not an option).

-dro
2
Preview Build Discussion / Re: Slight wording confusion
« Last post by dro on Today at 01:58:01 PM »
The installer checks if there's already a running process running & offers to close if which is what the initial prompt was trying to convey. As I didn't think a force close when manually running the installer is the best of ideas - it does however do that if updating from within wacup due to there being other ui aspects to convey it's happening.

The re-showing of that same prompt is because how the installer has been scripted it can't tell at the moment if the attempt to close the found instance is either just being slow to complete or if it's hit a hang on close problem & so will keep re-trying until hopefully that instance does close.

Typically the message would just be seen the once but if it doesn't close then it's not idea & I've now made a note to try to better convey the first attempt didn't work & to either wait a bit more or to attempt to force kill the process at the expense of any potential data loss.

-dro
3
No one's reported it so I wasn't aware its broken. Are you doing this in the main playlist or the library playlist views ?

-dro
4
Preview Build Discussion / Re: Can't Play aac or wma Files
« Last post by dro on Today at 01:43:39 PM »
When saying aac files, are they mp4+aac or raw aac files or aac in some other container? As I know that mp4+aac when they're for example yt rips within the dash format do not currently work (if it's a pure aac frame in an mp4 container then that should be playing).

WMA is noted above though iirc it should on new installs try to use the re-used directshow plug-in unless that couldn't be obtained during install &/or wasn't selected.

-dro
5
General Discussion / Re: Winamp source code to be released
« Last post by dro on Today at 01:05:28 PM »
I've merged the 2 threads that were made about this. For now this is really all I can say especially now I've had a chance to look at the press release...

Currently it doesn't seem to make any difference for WACUP as there's no developer specific details on what is supposedly going to be provided in ~4 months time nor the licensing terms of that or what the sign-up form stuff is all about (which isn't something I've ever seen related to such a process).

From the press release the Winamp will remain the owner of the software and will decide on the innovations made in the official version part seems to imply it not being super open nor permissive for other solutions. So I don't see how it really helps based on the lack of developer-centric details vs people already being able to make plug-ins &/or compatible clones.

The only things that'd be helpful to save me time would be the modern skin engine plug-in + related aspects & possibly the equaliser to get the correct sound, otherwise I've already got certain remaining aspects being worked on so the last few remaining pre-compiled plug-ins from the 5.666 installer no longer need to be re-used.

I'm just going to keep plodding along in finishing off what is my attempt at a winamp-like re-make & focus on that.

-dro
6
Preview Build Discussion / Re: Can't Play aac or wma Files
« Last post by Eris Lund on Today at 11:35:15 AM »
Can you provide some info on what the AAC file contains (codec and the like)?
As for WMA, you'll have to manually enter the WMA file extension into the DirectShow plugin, since there's no longer a dedicated plugin that handles WMA/WMV.
7
Preview Build Discussion / Can't Play aac or wma Files
« Last post by arealhuman on Today at 11:01:57 AM »
Hi - thanks for accepting me onto the forum  :)

I'm running the latest build of WACUP - Public preview v1.99.13.19100 (May 10th 2024) - on an up-to-date install of Windows 11.  I can't get WACUP to play aac or wma files.  The files load in WACUP but don't play.  It may well have been like this in previous builds, I certainly had some files that didn't play, can't recall if these were any of these.

Can anyone offer any help please?

On a different note, I'm so grateful someone is building on Winamp, WACUP is destined to be truly great.  Thank you.
8
General Discussion / Re: Winamp source code to be released
« Last post by Glamrlama on Today at 05:05:12 AM »
I think this is the key piece:

Winamp will remain the owner of the software and will decide on the innovations made in the official version," explains Alexandre Saboundjian, CEO of Winamp.

If that is the case I don't think that it's Open Source.
9
General Discussion / Re: Winamp source code to be released
« Last post by Eris Lund on Yesterday at 03:23:01 PM »
And if you read carefully, no mention of Open Source anywhere :-)

There's also a PDF of a press release that, more or less says the same.

https://www.llama-group.com/wp-content/uploads/2024/05/2024-05-16-open-source-en.pdf

It can be argued that their wording implies it'll be open source, though it's not mentioned under what license it'll operate (is it GPL? BSD? MIT? WTFPL? No one knows!) or that it'll be found in a git repository either on Github or some hosted instance.

If there's anything any one of us should've learned from previous announcements, they'll either not hold their own deadline, or they do follow through and it's behind closed doors with you being required to sign up. It's noteworthy that they fired most of the people working for them, so they might as well get people to do the work for free.

TL;DR: Don't get your hopes up.
Pages: [1] 2 3 ... 10