Home
Artists
Search Recent Random
Posts
Search DMs Popular Hash Lookup Tags Random
Importer
Import FAQ
Register
Partychan Telegram Find&Fuck Waifus ThePornDude
Home Artists Posts Import Register

WACUP Beta Builds #14132 through #14638 (5 builds) (Patreon)

Published:
2023-02-24 15:17:18
Imported:
2023-03

Content

Some might've noticed I've been mostly quiet on social media this year (just not feeling things) but I've been diligently working away at things with 5 beta builds since the start of year (1.8.15.14132 through 1.8.21.14638)

Changelogs for the builds are at https://getwacup.com/changelog/

These builds have also reduced how many supporting dlls from 5.666 are needed for them to work (see https://getwacup.com/beta_files.html#winamp).

Also the latest beta build drops idle cpu load for modern skins & by quite a lot for some (typically sat at very low power usage now for my test setup).

Obviously plans haven't been going as wanted but if the feedback is things aren't working right then it's imho better to work on trying to fix them & delaying adding in the features that are holding up doing a new preview build (coming some point before the end of the universe™)

-dro

Files

WACUP

Find out about which files are added or modified by installing WACUP.

Comments

Anonymous

Thank you and the beta-testers for the continuous effort put into the project. It's nice to see that there are still enough people invested in the classic program to keep it up and running after all those years. Can't imagine using any other player to listen to my music (besides VLC, but only on the smartphone 😛)

Anonymous

Good morning, I completely understand the fact of doing a stable version before thinking about adding other functionality. And thank you very much for this work, Winamp and a magnificent reader. I hope that one day, we can have a CMS plugin, as before to have the Winamp player on a Internet page, I know that before it was just a skin, which resembled to Winamp, but with the Evolution of the Internet, it is finally possible. In short, my dreams: 1. Winamp broadcasting the music with the cover on a page that makes it possible for the reader and where you can control the music to listen to, without no access or the possibility of downloading music the broadcast. Or you can control the volume of the sounds with reading, pause and stop 2. Winamp broadcasting the music with the pouch streaming on a page that makes the reader or you can control the volume of the sounds with reading and stop 3. Winamp broadcasting the video streaming on a page that makes the reader or you can control the volume of the sounds with reading and stop 4.Traduction in several language of the Winamp Inteface including French. _ _ If one day there was all that, the reader would be perfect. In short this is just a dream, but you never know. When the latest version of Winamp and released and they put the key under the door, it hurt my heart and I dreamed that this reader could one day be reborn from it. And miracle took place, so all and possible. In any case, a huge thank you to all that works on this project. Big big kisses to everyone and if I can help anything do not hesitate.

wacup (edited)

Comment edits

2023-04-07 03:56:42 With points 1 & 2, you already can achieve some of that using the built-in streaming server (just no artwork is provided on the web page that's offered). The intent is to have a native equivalent of the ajaxamp plug-in (which does afaict still work under WACUP). Point 3 seems to be related though video is a lower priority but that's more down to having the streaming server plug-in be able to provide access to the file(s) so the browser, etc can then do the decoding needed. With point 4, localisation support is planned but is not happening until a non-preview build is mostly ready. As that's going to involve getting tool coded up to support it along with completing all of the handling that is needed in the WACUP core & the plug-ins (I've been mostly doing that as I go but there's still gaps). Also the intent is to treat the localisation process as a dedicated development phase as it'll also allow for a review of the preferences & related options to work out what can / should be re-worded &/or changed to make things better going forward. I've no plans to give up on WACUP so hopefully sooner rather than later I'll be able to offer the things that are needed :) -dro
2023-03-31 17:40:11 With points 1 & 2, you already can achieve some of that using the built-in streaming server (just no artwork is provided on the web page that's offered). The intent is to have a native equivalent of the ajaxamp plug-in (which does afaict still work under WACUP). Point 3 seems to be related though video is a lower priority but that's more down to having the streaming server plug-in be able to provide access to the file(s) so the browser, etc can then do the decoding needed. With point 4, localisation support is planned but is not happening until a non-preview build is mostly ready. As that's going to involve getting tool coded up to support it along with completing all of the handling that is needed in the WACUP core & the plug-ins (I've been mostly doing that as I go but there's still gaps). Also the intent is to treat the localisation process as a dedicated development phase as it'll also allow for a review of the preferences & related options to work out what can / should be re-worded &/or changed to make things better going forward. I've no plans to give up on WACUP so hopefully sooner rather than later I'll be able to offer the things that are needed :) -dro
>>104071310

With points 1 & 2, you already can achieve some of that using the built-in streaming server (just no artwork is provided on the web page that's offered). The intent is to have a native equivalent of the ajaxamp plug-in (which does afaict still work under WACUP). Point 3 seems to be related though video is a lower priority but that's more down to having the streaming server plug-in be able to provide access to the file(s) so the browser, etc can then do the decoding needed. With point 4, localisation support is planned but is not happening until a non-preview build is mostly ready. As that's going to involve getting tool coded up to support it along with completing all of the handling that is needed in the WACUP core & the plug-ins (I've been mostly doing that as I go but there's still gaps). Also the intent is to treat the localisation process as a dedicated development phase as it'll also allow for a review of the preferences & related options to work out what can / should be re-worded &/or changed to make things better going forward. I've no plans to give up on WACUP so hopefully sooner rather than later I'll be able to offer the things that are needed :) -dro