Latest restricted WACUP beta release is build #19320 (June 5th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #19320 (June 5th 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.

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.

Topics - bobdobbs

Pages: [1]
General Discussion / Otachan in_mpg123 - includes source code.
« on: April 01, 2022, 12:00:00 PM »!mpg123.html

Was having a bit of a look in the internet archive and grabbed the link to Otachans in_mpg123.

It's nice in that the archive contains source code as well.

The license is LGPL.

I've attached it here.   It looks like there is also Shibatch mpg123, which is a patched version of this, I don't have this to hand right now.

General Discussion / Linux download/install script for WACUP in Wine
« on: March 18, 2022, 03:13:54 PM »
Here's a very basic script using the installer options to install WACUP in wine.

Code: [Select]

set -ex

# Options passed to installer:
# /IAGREE   -   Agree to installation [skips the welcome, license & changelog page (if applicable)]
# /PORTABLE  -  Select the portable install mode (settings stored in the install folder) by default instead of a normal install (which stores the settings on a per-user basis)
# /S   -        Run the installer silently, assumes a default full install
# /D=<path>   - Sets the default installation directory and this must be the last parameter used in the command-line and must not contain any quotes, even if the path contains spaces. Only absolute paths are supported.

# Only use wine32 bit for now, with a prefix in ~/.wine32

# FILENAME=WACUP_Preview_Portable_v1_0_21_7236.exe


DOWNLOAD_DIR=/tmp/$(basename ${FILENAME} .exe)

mkdir -p ${DOWNLOAD_DIR}
cd ${DOWNLOAD_DIR} && curl -s -L -C - -O $URL


Normally I'd put something like this as a public github gist, though I guess that could attract more testers, which I'm not sure are needed right now.

This sort of thing is handy as the basis for automated testing, if I tweak this further I'll update this thread.

For now this is a little my-compute centric, it installs using Wine to a 32 bit prefix in .wine32.

Since I only get bits and pieces of time I like to automate things so I don't need to think too much when I come back.

I'd like to install WACUP headlessly, are there commandline options I can pass to the installer to do this ?

I'm writing a little script to download and install in Wine.

Since it's not in Windows, the only thing I change is to set Portable mode and install to C:\WACUP

General Discussion / Winamp SDK and control by python
« on: November 05, 2018, 12:14:47 AM »
I was having a look at some automation of winamp, with the aim of grabbing screenshots of the GUI, to compare how it looks natively and under Wine (and be able to easily regenerate them each time a new version arrives)

This (ancient) python winamp control library amazingly still works

> Uses the winamp api
> and windows messaging to control winamp.

On the other hand it's incomplete and uses magic numbers from the SDK.
Where can I find an up to date version of the SDK, and is this even a sane approach ?

I had a look into autoit, but that looked like a bit of a pain (though it does have python bindings which is something).

Skins / Process for porting winamp2 style skin to modern ?
« on: February 01, 2018, 11:45:02 PM »
ArcticAmp is one of my favourites, but not being modern the other bits of the UI are a bit lacking.

What sort of process would I have to go through to attempt a remake as a modern skin ?

Are there any tools that can help, and if not, whats the manual process like ?

Pages: [1]