2

Foobar2000 volume slider stopped working in Wine

Sound is good but volume cannot be changed from the player's slider anymore.

Is there a setting in Wine that might have entailed this?

I have tested [Vineyard][1] (also) and then gave it up on which occasion some setting in Wine might have been altered but cannot see which.

Edit: This affects the main installation (v.1.1.15) made in Wine, and also portable installations of the same version (as well as portable installations of v.1.1.14 and 1.1.17b that I tested) but does not affect older versions like 1.0.3.

After testing more versions, it seems that the newest version without this problem is 1.1. (That is, before the version that changed the classic white-on-black Foobar2000 icon with the new white one.)

3 Answers3

5

As we have discussed various things in the comments without success, what might work is to create a new wineprefix and then install and run foobar always from that prefix. That may allow you to continue using foobar without reinstalling wine, as the corrupted settings may be present in the original .wine folder.

Create your wine prefix with:

WINEPREFIX=$HOME/.foobar winecfg

Then you can temporarily export the location to the environment:

export WINEPREFIX=$HOME/.foobar

(see my note below re using export and env)

Then cd to your newly downloaded version of Foobar2000 and run the install:

wine foobar2000_v1.1.17.exe

I had to logout and login before I launched the program, or I experienced some odd errors and heavy disk activity. That was probably my system however.

Now if you have logged out, open terminal and run the export command again and then enter

wine "c:\\Program files\\foobar2000\\foobar2000.exe"

To alter any settings in this new prefix, you can just run

winecfg

as long as the prefix is exported to the environment as above.

Note: I have specified to export the WINEPREFIX environmental variable above; an equally valid method would be to use env, and often using env is very useful as it does not rely on the variable having already been set with export. The WINEPREFIX specified with env is used for that command-line only, whereas using export means that variable becomes the default environmental variable and thus would have to be unset if a different WINEPREFIX was needed to be used.

Some example usage of env:

env WINEPREFIX=$HOME/.special <wine commands>

You will also have to modify the foobar location in the script I recently discussed in my other answer by adding the following, modified for your system, under the shebang at the top of the script:

export WINEPREFIX=$HOME/.foobar
cd /home/mike/.foobar/drive_c/Program\ Files/foobar2000/

This is definitely one way to get fresh settings without reinstalling wine and removing your .wine folder, and it should make foobar work correctly again, and can be repeated for many different wine programs: see the Wine FAQ.

Community
  • 1
3

The problem with the volume control appeared for me, too. I changed lots of audio settings in wine and foobar2000, but nothing worked. Then I remembered, that i changed in the wine settings the windows version from Windows XP to Windows 7. Resetting it to Windows XP solved the problem for me.

user1963987
  • 31
  • 1
0

Change the windows Version in Wine configuration under the Applications tab. I had it on windows 7 and the volume slider as well as the Data output format under playback/output in Foobar2000 preferences did not work. I switched it to Windows xp and it now works again. Good deal because it was killing the Sound quality of my Bowers & Wilkins MM-1 speakers. I know they say that I should put the Data output format on 16 Bit however the sound quality was lacking depth. 24 or 32 bit sound waaaaaaaaaaay better. There is far more depth and detail at 24 or 32 bit. It was so dull sounding that I stopped listening to my music for months until I finally figured it out.

A Hardcore Audiophile

A Hardcore Audiophile
  • 1