WACUP
General => General Discussion => Topic started by: Aminifu 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.
-
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.
-
The installer shouldn't be touching the volume of the installed process in any manner plus I'm not sure how it'd be able to do that when none of the code that could do it would even be run & those changes would be against the installer process which shouldn't have any audio active.
More likely it's being changed by a plug-in / skin / other random process interaction prior to installing. Not that it should happen if pre closing wacup before updating or from within the installer telling it to close. So far I've not seen this happen & I'm not going to hold up doing a new beta / preview tomorrow for this as long as 22222 isn't crashing.
-
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.