Latest WACUP public preview for x86 & x64 is build #23234 (November 27th 2025) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #23234 (November 27th 2025) (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 - Aminifu

Pages: [1] 2 3 ... 31
1
In the medial library window that lists all your playlists, you can select more than 1 at a time. If you want to select consecutive playlists, just select the first one then hold down the Shift key and click on the last one. If you want to select non-consecutive playlists, just select one and hold down the Ctrl key and click on all the others you want in the group.

2
General Discussion / Re: WACUP Installer issue
« on: July 22, 2025, 10:42:16 PM »
Hmm.. weird.  Haven't seen that.  Looks like the volume level is stored in the winamp.ini file with volume=##.   For me it's volume=206 which is apparently 80% (I changed it in the player and this value changed) .  Suppose you could do a comparison of that value pre and post update to see if it's changing.

I agree, it's weird and has only happened with the last few releases. I always shut down WACUP and make a copy of the contents of my WACUP's user folder before installing a new release. I'll start doing a pre and post update comparison of that value in winamp.ini.

I leave the internal volume level at 100% (255) in my ui configurations for all of the skins I use and use the volume control for my speaker system to control the final output level I hear. Therefore, I never use any of the in-app volume controls during playback. I have enabled the WACUP option to prevent the mouse wheel from altering the volume. I also have enabled the option to use output plug-in specific volume control instead of OS only control. I have the OS process volume set at 95%, so the effective volume level is 95%.

The value in the winamp.ini copy I saved before installing build #22222 (x86) is 251. No idea how that happened during the last shutdown before the update. So it wasn't the installer, the value was somehow changed in winamp.ini before the installation.

I've an app called WinDiff that has been in my tool bag for years. I use it to flag differences in text files, among other things. The only relevant difference between the winamp.ini copy and my current winamp.ini file is the volume value.

3
General Discussion / WACUP Installer issue
« on: July 22, 2025, 08:29:43 PM »
Sometimes, the WACUP installer for the last few releases has been changing the app's internal volume level. Sometimes the change was small (barely noticeable) and sometimes it was large (zero volume output). The installer for Build #22222 (x86) made a small change in my configuration's value.

4
General Discussion / Re: WACUP Modes
« on: July 19, 2025, 12:41:14 PM »
Ok, so there is no real difference. I have been launching WACUP from a wacup.exe shortcut pinned to my task bar for years.

The recent talk about interactive buttons on the OS toaster and start menu entries caused me to look in my start menu. I guess the entry for the other mode (which launches the winamp.exe file in the WACUP folder) has been there all along.

5
General Discussion / WACUP Modes
« on: July 19, 2025, 12:06:28 PM »
Hi dro,

From looking in my start menu, I see there are now 2 ways to launch WACUP. A WACUP (Winamp Compatibility Mode) (32 bit) process and a WACUP (32 bit) process. What is the difference between them? They both appear to look and work the same way on the surface.

6
Resolved Issues / Re: [CHANGES MADE] CPro MMD3 won't load
« on: July 18, 2025, 12:53:26 AM »
It'll be the 2 elements that are bright pink as part of the player control section. ...

That is fixed in build #22186 (x86). Thank you dro.

7
Skins / Re: Winamp Modern Updated for WACUP
« on: July 04, 2025, 09:46:55 PM »
Simply copy the skin's archive file (the single file that contains all the things that make up the skin) to the WACUP or Winamp skins folder.

8
Resolved Issues / Re: [CHANGES MADE] CPro MMD3 won't load
« on: July 03, 2025, 05:16:36 PM »
Hi dro,

IMO, it is mighty big of you to have your code turn those leds on/off for that 1 skin, since it is popular. Thank you!

9

Today I used wacap for the first time, the x64 version. Wow, it’s really good.


Consider keep using WACUP, since you seem to like it. How about using the Alt+L keyboard shortcut to open and close the media library window. Some of the skins I use do not have a close button on that window and I had to get used to using the keyboard shortcut (simple and quick).

10
Resolved Issues / Re: [CHANGES MADE] CPro MMD3 won't load
« on: July 03, 2025, 08:53:37 AM »
It'll be the 2 elements that are bright pink as part of the player control section. ...

Oh that. They won't be as bright when choosing a different color theme. One of our Skinner members can probably provide a better solution.

11
Resolved Issues / Re: [CHANGES MADE] CPro MMD3 won't load
« on: July 03, 2025, 08:37:14 AM »
What's wrong with it? If you want the tab labels to be spelled all the way out, make the skin a little wider. Point to the bottom right corner and when the mouse pointer turns into a double headed arrow, click and drag to the right.

I suggest you turn on a custom beat vis. Right-click on the Cpro label at the top, select the show beat vis command at top of the dialog that opens and select one of the beat vis listed. I like the dancing queens.

12
Skins / Re: Big Bento started failing -script error
« on: July 02, 2025, 12:39:19 AM »
It probably won't hurt anything at this point to delete (or move) your bento skin folders and reinstall them from the WACUP installation file. If they still fail to load without error, then something must be off elsewhere in your configuration.

13
Skins / Re: Big Bento started failing -script error
« on: July 01, 2025, 05:57:24 PM »
I'm using the x86 version of WACUP. What version are you using?

Sorry, dumb question. X64 version doesn't support modern skins.

14
Skins / Re: Big Bento started failing -script error
« on: July 01, 2025, 06:23:08 AM »
I'm not getting a script error notice when switching to the Big Bento Modern or the Big Bento Modern Windows 10 edition skins after starting WACUP with another skin. I also don't get an error when starting WACUP with either of these skins. Both of these skins are version 1.2.4. I have the same script file and see that it is used by the player-normal.xml file in my configuration. What versions of the bento skins are you using? I'm using the x86 version of WACUP. What version are you using?

15
General Discussion / Re: Winamp Info Tool updated
« on: June 27, 2025, 06:21:23 AM »
Yes, it appears not much was updated. My report only included 2 things that weren't reported by my previous version 6.3.1.6402. I think those 2 things weren't in my configuration when I ran the earlier report, but I can't remember.   :)

Pages: [1] 2 3 ... 31